'Next to use' erroneously increases cat number in wxdigitizer settings
|Reported by:||shanel||Owned by:|
|Keywords:||digitizer category||Cc:||mlennert@…, grass-user@…|
Corresponded about this on grass-users list; summary of my experiences and Moritz Lennert:
After opening up 'digitization settings' dialog when in digitize mode in wx map display. For option 'Category mode' each time user mouse-clicks on 'Next to Use', the 'category number' increases by one. This is without doing any digitising at all, just clicking on the mode option e.g. If I click on 'next to use' in the listbox ten times, the cat that will be used next goes from 320 to 330, before I have digitised anything to even give a cat to. Then when proceeding to digitise, the next cat number used will be 331 and no cats will exist for 320 to 330. So not only does repeatedly clicking on 'Next to Use' artificially increase the cat number, but what is actually used when next digitising is a cat number one higher than shown as 'next' in the dialog.
If user then sets 'Manual' number to be lower than the max cat number, e.g. I set it down to 140, then (regardless of whether I digitise something with cat 140 or not) returning to 'Next to Use' option it will increment from the manually selected number, not from what the max cat number is for the vector layer in question.
Moritz had some further experience/comments:
"At the same time, when you actually digitize in 'Next to use' mode, the counter does not increment visibly in the parameter window. You have to close that window and open it again to make this visible. (my note: or if you click on 'next to use' mode again, it will 'catch up' to whatever the next number is supposed to be.)
Generally, the fact that this parameter (i.e. choice of mode) is hidden in the parameter window, makes it much less convenient to use. In this particular point, the tcl/tk system is easier.
I don't think this is related to system specs. This seems to be within the _setCategoryNextToUse(self) function in gui/wxpython/gui_modules/wxvdigit.py (or within possible library functions used there...)."
My system settings are filed with this bug. Not sure what system settings Moritz duplicated the issue on but probably different to mine.