Editor problems with repositioning decks and stacks

[cholmcc]

@shilinski

w1. I have a wide map in a game, and I find while playing, it’s a PITA to navigate left and right. Imagine a huge map of Europe and Russia. There’s a toolbar button labeled “Moscow.” I press it, and bam, the view is centered on Moscow. I press a “Berlin” button. Bam, I’m centered on Moscow. I’d like to be able to wire toolbar buttons to single pieces. In my example, I’d make hidden, immobile “focus” pieces in those cities.

This can probably be accomplished by a Move Cameria Button with explicit pixel coordinates, or by adding an invisible piece (in a low Game Piece Layers with traits Does not stack with no movement or selection, Restricted Access to make sure no one can manipulate it, and a unique name - say MoscowLocation), and a Move Cameria Button that moves to that piece.

@shilinski

w2. The does-not-stack trait defines if a piece can be moved and/or selected. It would save me a hell of a lot of work if I could control those fields with properties. … I’ve considered coming out of retirement to do these myself.

You could implement it by Creating Custom Classes - in particular a custom BasicCommandEncoder and a custom Immobilized classes.

But, you can probably achieve the same effect by a Dynamic Property that sets the property NON_MOVABLE to true when the piece cannot be moved, and to false when it can. I haven’t tried that, but as far as I can tell, it should work. Of course, you should be careful if you mix that with the Does not stack trait.

Yours,
Christian