Hi Kevin, I think the issue is that there are actually three layers:- SideA, SideB and Default.
Whenever you define Game Piece Layers, there is an additional 'Default' layer is implicitly defined for any pieces that belong to none of the defined layers. Pieces in the Default will float on top of all other defined layers. The Rotate Layers command is rotating through this hidden layer as well as your defined layers. It sounds like the 'Skip layers with no pieces' option is not correctly recognising when there are no pieces in the Default layer. I will add a Bug Report for you. Regards, Brent. >*********** REPLY SEPARATOR *********** > >On 19/11/2006 at 7:06 PM Kevin Coombs wrote: >Hello all, > >I am creating a module that has only two sides (we'll call them SideA >and SideB). To keep the pieces of these two sides from stacking >together when one side is moving through a hex containing pieces from >the other side, I have created two Game Piece Layers, one layer for >SideA and one for SideB. SideA is the default top layer. > >Now I want to allow the players to "toggle" which side is the layer >that is "on top." This will allow the players to control which >pieces are displayed "on top" of the stack, so that, when SideA is >moving, his pieces will display on top of a stack of pieces >containing both player's pieces, then, when it is SideB's turn, the >SideB player can toggle to make SideB's pieces appear on top of mixed >stacks during his turn. Then, of course, when it is SideA's turn >again, the SideA player can just toggle back. > >To allow this toggling, I have added a Game Piece Layer Control. In >it I have selected "Rotate Layer Order Up." This does what I am >wanting (toggling between SideA and SideB to be the top pieces). >However, there appears to be a small problem. Even though there are >only two Layers in my module, the SideB player has to click the Game >Piece Layer Control (GPLC) button twice to toggle over to his side on >top. > >It appears the layer that is defaulted as the top layer (SideA) >remains the top layer with the first click, then the second click >brings up SideB as the top layer. So here is what happens: > >1) SideA is the default top layer. He takes his turn and is finished. >2) SideB player clicks the GPLC button once to cause his pieces to be >on top: SideA is still the top layer. >3) SideB player has to click the GPLC button a second time: now SideB >is the top layer. He takes his turn and is finished. >4) SideA player clicks GPLC button: now SideA is the top layer and he >takes his turn. >5) Now back to SideB player. Here we repeat the steps starting with >step 2 above. He has to click the button twice for his pieces to >become the top layer. > >So, in essence, it takes 2 clicks of the button to get SideA (the >default top layer) to stop being the top layer. You would think >that, with just two Game Piece Layers defined, it would only take one >click to toggle to allow the other pieces to be on top. > >Note that I also tried this with "Rotate Layer Order Down" and I get >the same results. I also tried this with the Skip Layers with No >Counters checkbox both checked and unchecked, and both yielded the >same results. > >So my questions are: > >1) Am I doing this whole toggle concept wrong? Is there another way >I should be toggling to change the top layer? Or should I be >selecting another Action in the GPLC dialog window other than Rotate >Layer Order Up (or Down)? > >2) Or, is there a bug with the Rotate Layer Order Up (or Down) >Actions? > >Thanks for anyone's help. > >Kevin > > > ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED]
