Create account / Log in
Bug 13042 - NON-RECTANGULAR pieces laid over top one another can cause selection errors
NON-RECTANGULAR pieces laid over top one another can cause selection errors
Status: NEW
Product: VASSAL
Classification: Applications
Component: Editor
PC Windows
: unspecified normal
: ---
Assigned To: Bugs
Depends on:
  Show dependency treegraph
Reported: 2020-06-08 20:43 CEST by Brian Reynolds
Modified: 2020-06-22 00:12 CEST (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Brian Reynolds 2020-06-08 20:43:20 CEST
If a "small" non-rectangular piece ends up laid on top of a "big" non-rectangular piece, then the big piece may override selection of the small piece, even though the small piece is drawn in a higher priority layer than the big piece.

It isn't really necessary that the pieces be "big" and "small", but it is easier to illustrate the problem that way.

REPRO Steps:
1. Make a "big" non-rectangular piece and a "small" non-rectangular piece.
2. Put the big one in a bottom/low-priority Game Piece Layer.
3. Put the small one in a top/high-priority Game Piece Layer.
4. Make both pieces Does-Not-Stack
5. Now start the module and drag the small piece over top of the big piece so that it is "entirely within" the big piece.
6. After deselecting it, try to select the small piece by clicking

Expected: small piece selects when you click inside its non-rectangular masked area.

Actual: that selects the big piece, even though it is supposed to be "drawn lower". NOTE: The small piece can still be selected with band-select.

I can provide a module for this if desired.