Opened 11 years ago
Closed 11 years ago
#2012 closed defect (fixed)
d.vect wx module GUI forgets column names
Reported by: | hamish | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.4 |
Component: | wxGUI | Version: | svn-trunk |
Keywords: | d.vect | Cc: | |
CPU: | x86-64 | Platform: | Linux |
Description
Hi, I notice if I add a new vector layer and in the symbol tab of the d.vect pop up GUI I set the symbol size_col and rotation_col options to column names, it works ok, but then if I go back to the vector layer -> preferences and the symbol tab again the given column names are gone & forgotten. If I press apply or ok a second time the map re-renders and those settings are lost.
happens in all branches, e.g. for any points map: cat, cat, and size=1.
(trying that for a line map [m.cogo import example] without a db connection or cat number for the line ends up in a traceback error)
I also notice an error in trunk that the drop down menu for the column names is empty, but I can manually type "cat" there and it works.
? thanks, Hamish
Change History (3)
comment:1 by , 11 years ago
follow-up: 3 comment:2 by , 11 years ago
tested in trunk, now remembers size_col and rotation_column. thanks. drop down menu and no-db issues also seem to be fixed.
during testing it's still printing a traceback error to the terminal though:
(wxgui.py:3206): Pango-CRITICAL **: pango_layout_get_cursor_pos: assertion `index >= 0 && index <= layout->length' failed
Hamish
comment:3 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to hamish:
tested in trunk, now remembers size_col and rotation_column. thanks. drop down menu and no-db issues also seem to be fixed.
so I am closing this ticket as fixed
during testing it's still printing a traceback error to the terminal though:
(wxgui.py:3206): Pango-CRITICAL **: pango_layout_get_cursor_pos: assertion `index >= 0 && index <= layout->length' failed
Usually, this is harmless. It's not easy to fix this, so if you consider this as a problem open a new ticket (with minor priority).
Please test again, the column problem should be fixed. Please be more specific about the other problems, include the traceback error.