Opened 8 years ago

Closed 7 years ago

#1616 closed defect (fixed)

WXGUI selecting to render a map and map selection bind to same event in layer manager

Reported by: marisn Owned by: grass-dev@…
Priority: normal Milestone: 6.4.3
Component: wxGUI Version: 6.4.2
Keywords: Cc:
CPU: Unspecified Platform: All

Description

When I click on the checkbox to render/disable map rendering in WXGUI layer manager, the map is selected. Clicking on the next map's checkbox will select it too.

Now when I try to get rid of this selection to have only one map selected by clicking on map name - nothing happens.

When I click outside of checkbox and outside of map name, it gets unselected, still it also triggers a rendering checkbox value change (i.e. from "not render" to "render").

The problem comes from the fact, that checkbox and the background of map layer entry both respond to same single event. Selecting a map to render or not shouldn't change it's selection and selecting/unselecting map layer shouldn't change it's rendering status. Current implementation makes really hard to select and change rendering options for multiple map layers.

Change History (4)

comment:1 in reply to:  description ; Changed 7 years ago by annakrat

There are more problems. One of them is that layer selection and changing checkbox state should be independent which was not working properly. This issue should be fixed in r52913 (grass 7). Please could you test it works also on Windows? I can then backport it.

Other issue is related more to wxPython/wxWidgets. When you click outside the layer name it triggers the change of checkbox state. This behaviour is the same like in wxPython demo. I am not sure if there is some workaround for this.

Anna

comment:2 in reply to:  1 Changed 7 years ago by annakrat

Replying to annakrat:

Other issue is related more to wxPython/wxWidgets. When you click outside the layer name it triggers the change of checkbox state. This behaviour is the same like in wxPython demo. I am not sure if there is some workaround for this.

I found a workaround (in r52933).

Anna

comment:3 Changed 7 years ago by annakrat

Platform: MSWindows VistaAll

Reported in wxTrac as a bug 14613 (Bad behaviour of CustomTreeControl? check item with TR_FULL_ROW_HIGHLIGHT style). Bug was fixed by wxPython changeset 72383.

comment:4 Changed 7 years ago by annakrat

Resolution: fixed
Status: newclosed

Nobody complains, so I backport it in r53070 and r53071 together with changes from #1717. Reopen if needed.

Note: See TracTickets for help on using tickets.