From: Erik V. <eri...@xs...> - 2012-08-31 21:32:39
|
Yes, that is valid. There are two ways to do it: 1. Create a separate <IfOption> tag for each and every variant. That is how I did it originally in all situations, and how your example below does it. 2. First define a default case (without <IfOption> tags), and add <IfOption> tags per (group of) variant(s), only defining the differences, which override the default values only if specified That is how I have later started to configure game options. This way, a lot of code can be saved. Erik. > -----Original Message----- > From: Oliver Heck [mailto:oli...@gm...] > Sent: Friday, August 31, 2012 1:56 PM > To: rai...@li... > Subject: Re: [Rails-devel] 1835 Schlesien > > Erik, > > I understand your discussion about variants and options. But I am not sure, > what are the implications to how the XML-files have to be changed. > > Is this the 18xx-example still valid? > > <IfOption name="Variant" value="Basegame,Pere > Marquette,Reading,Simple"> > <Hex name="F2" tile="-903" orientation="5" value="40,70" > city="Chicago"/> > </IfOption> > <IfOption name="Variant" value="Coalfields,Coalfields&Reading"> > <Hex name="F2" tile="-903" pic="-939" orientation="5" > value="40,70" city="Chicago"> > <Access runThrough="yes"/> > </Hex> > </IfOption> > <IfOption name="Variant" value="Wabash"> > <Hex name="F2" tile="0"/> > </IfOption> > > I am waiting for your input how to move on. > > Oliver > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |