wxgui: g.region: can't reset `rows=' nor `cols='

[msieczka]

1. Run g.region from wxgui.

2. `Resolution' tab.

3. Change the `Number of rows in region'.

4. "Oops, I wanted to edit the resolution instead."

5. Edit the `Grid resolution 2D (...)' field as you intended too.

6. You can't reset `rows=' in the GUI now.

[neteler]

Indeed, no way to reset the "accidentally" hit rows= in the GUI. I fear that there is no (easy) way to avoid this.

A nice idea would be to offer here the region dialog from the Location wizard rather than the simply g.region interface.

[annakrat]

The same for v.label fontsize option. Easy way is to replace the spin control with a text field, but we probably don't want this.

[hamish]

n.b. this isn't a bug with any particular module, rather the module GUIs generated by the parser.

[annakrat]

How about changing the spinctrl to text field with integer validator (the same we did for floatspin)? In this case there is now sense in having the spinctrl anyway. We can use the text field only in cases when there is no required answer (and maybe no default answer).

[mlennert]

Replying to annakrat:

How about changing the spinctrl to text field with integer validator (the same we did for floatspin)? In this case there is now sense in having the spinctrl anyway. We can use the text field only in cases when there is no required answer (and maybe no default answer).

+1. Values can be so different that spin control does not really make sense.

Moritz