[CF List] problem with some diseases

[Andreas Vogl]

Scott Wedel wrote:
>
     
      > 
     
     >
     
      > "negative" damage had some special meaning [...]
     
     >
     
     
     >
     
      This type of stuff is straightforward really bad programming technique.
     
     >
     
      It is using the sign of the damage value to determine what could
     
     >
     
      be called DISEASE_DAMAGE_ADJUSTER. 
     
     
No doubt it's bad style, but unfortunately the CF object structure is
not as flexible as we'd like it to be. If unique variables and flags get
added for different object types (like the "disease-adjuster" you
proposed), that would cause a big overall increase in memory consumption.
The problem is that all objects have the same structure. Best you can
do is link-in substructures with pointers - But that's no perfect solution
either (danger of null-pointers getting accessed).

>
     
      Currently, the disease definition is needlessly obscure when
     
     >
     
      instead it should be clear so that someone could add a new
     
     >
     
      disease or modify the current ones. [...]
     
     
Try the CFJavaEditor, like for most other objects there is a good
interface for modifying diseases.

It wouldn't be too hard to rip out the attribute-interface code from
the JavaEditor and create a stand-alone "arch creation" application,
if that seems useful.


Andreas

-- 
GMX - Die Kommunikationsplattform im Internet.
     
     http://www.gmx.net