From: Erik V. <eri...@xs...> - 2010-01-13 20:24:14
|
Hmm, yes, apparently the options cannot be used on the same level where these are defined (although in fact the IfOption tags are processed first). Perhaps these should be lifted out of the Component tags entirely. If you think it's really important, I could have another look at it. Erik. -----Original Message----- From: Rick Westerman [mailto:wes...@pu...] Sent: Wednesday 13 January 2010 19:42 To: Development list for Rails: an 18xx game Subject: Re: [Rails-devel] IfOption in Map.xml Erik Vos wrote: > Yes, <IfOption> is a generic feature that should be honoured by all Rails > XML files. > I think I have found one place where it is not. But there may be a work-around. The place is in the 'GameManager' component within the 'Game.xml' file. The GameManager is, of course, where the GameOptions are defined so this may be a clue to the problem. Or as usual I might be doing something wrong. Anyway I wanted to change the PlayerShareLimit based on a GameOption. Could not do it in there. Other component sections in Game.xml do accept options. -- Rick ---------------------------------------------------------------------------- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Rails-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rails-devel |