#1831: wxgui d.vect: layer option should show default applied (1), not -1
-------------------------+--------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: wxGUI | Version: 6.4.2
Keywords: d.vect | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
The d.vect gui in the wxgui shows -1 by default for the layer parameter.
However, the default in grass6 is 1. This creates confusion for the user.
Is there a way to have the layer option in the GUI show the actual default
value ?
This might be more generic than the specific case of d.vect and layers. I
just happened to notice it here since my students were very confused after
using v.net to connect nodes to a network to then not see those nodes,
even though the layer option showed -1 in the GUI.
#1831: wxgui d.vect: layer option should show default applied (1), not -1
-------------------------+--------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: wxGUI | Version: 6.4.2
Keywords: d.vect | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
Comment(by marisn):
Just tested with a fresh svn up && distclean && make on trunk r54265 and
the issue #1749 with GUI/executed command mismatch is still present. I
would assume it might have the same root cause as for this issue somewhere
in d.vect wxGUI layer switching magic code.
Replying to [comment:2 mlennert]:
> Replying to [comment:1 marisn]:
> > Could be related to #1749 ?
>
> Possibly, although I cannot reproduce #1749 on either 6.4.2, 64release
or trunk. Which version are you using to produce this ?
>
> Moritz
Just tested on 6.4.3RC2 on Windows. It causes a huge confusion. Sorry, as
this is a regression*, it must be fixed before new release.
* A software regression is a software bug which makes a feature stop
functioning as intended after a certain event. In this case - it was
working just fine in previous 6.4.x releases and has been introduced by
backporting from trunk.
But in grass7 -1 is default I think. The issue is different - the
attrcolumn should be bound to llayer, not to layer option. I think it
deserves a new ticket. It is quite difficult to solve this because part of
the dependencies between widgets in auto-generated modules is in gui and
in parser options and there are many exceptions to handle (like this).
Without better parameter description it is hard to solve these issues in
gui.