From: Erik V. <eri...@xs...> - 2011-07-08 11:36:01
|
> -----Oorspronkelijk bericht----- > Van: Stefan Frey [mailto:ste...@we...] > To solve the issue of the location I would simply add a location field to the > SpecialRights class and initialize that from XML. OK, I have done that (and maybe overdone it by allowing multiple locations). I'm thinking if we couldn't make Rights more useful by even further generalizing it. The next new special feature that I'm considering is the 18TN Civil War, which sets in with phase 3½, and involves that each company cannot use one of its trains at the next run - so this is important for you, Stefan. (The president can choose which train, but I guess we can safely default to the smallest one). How to register such conditions? I tend to treat it as a (temporary) right. It's a negative right though - rather a liability than an asset - so should we rename Right to the more neutral Condition? Any better name? To distinguish between one-time and permanent rights/conditions/properties, we could also turn it into a class and add a boolean attribute names oneTime or such. Erik. |