neteler
1
Hi,
I found yet another wxPython3 issue 
Running the selection dialog
g.mapsets -s
I can hardly read which mapset was checked (see attached screenshot).
From the code in
gui/wxpython/modules/mapsets_picker.py
I don't understand which wx demo (/usr/share/doc/wxPython-docs/demo/
)I should try to possibly report it upstream.
Or is it a GRASS issue?
Likewise g.gui, where I have to "blindly" use the checkboxes in the
layer tree while being fine in the map selection tool (see second
screenshot).
Any hints why they behave so differently?
Markus
(attachments)
On 17/12/16 11:17, Markus Neteler wrote:
Hi,
I found yet another wxPython3 issue Running the selection dialog
g.mapsets -s
I can hardly read which mapset was checked (see attached screenshot).
From the code in
gui/wxpython/modules/mapsets_picker.py
I don't understand which wx demo (/usr/share/doc/wxPython-docs/demo/
)I should try to possibly report it upstream.
Or is it a GRASS issue?
Likewise g.gui, where I have to "blindly" use the checkboxes in the
layer tree while being fine in the map selection tool (see second
screenshot).
Any hints why they behave so differently?
I cannot confirm this here on Debian Testing with wx-python 3.0.2 and Python 2.7.12.
Moritz
You can test g.mapsets -s GUI dialog with CheckListCtrlMixin demo.
Add multiple maps dialog uses wx.CheckListBox.
Layer manager uses CustomTreeCtrl.
So they all use different widgets. Although I can't rule out the
possibility something's wrong in GRASS, I think it's a problem
upstream.
Anna
On Sat, Dec 17, 2016 at 5:17 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
I found yet another wxPython3 issue Running the selection dialog
g.mapsets -s
I can hardly read which mapset was checked (see attached screenshot).
From the code in
gui/wxpython/modules/mapsets_picker.py
I don't understand which wx demo (/usr/share/doc/wxPython-docs/demo/
)I should try to possibly report it upstream.
Or is it a GRASS issue?
Likewise g.gui, where I have to "blindly" use the checkboxes in the
layer tree while being fine in the map selection tool (see second
screenshot).
Any hints why they behave so differently?
Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
neteler
4
On Sun, Dec 18, 2016 at 10:00 PM, Anna Petrášová <kratochanna@gmail.com> wrote:
You can test g.mapsets -s GUI dialog with CheckListCtrlMixin demo.
Thanks:
python /usr/share/doc/wxPython-docs/demo/CheckListCtrlMixin.py
--> broken.
Add multiple maps dialog uses wx.CheckListBox.
python /usr/share/doc/wxPython-docs/demo/CheckListBox.py
--> ok (as we knew)
Layer manager uses CustomTreeCtrl.
This one I found with grep:
python /usr/share/doc/wxPython-docs/demo/TreeMixin.py
--> broken (it is in the CustomTreeCtrl tab)
So they all use different widgets. Although I can't rule out the
possibility something's wrong in GRASS, I think it's a problem
upstream.
Confirmed. I have now report it upstream (say, to the Fedora package
maintainer):
https://bugzilla.redhat.com/show_bug.cgi?id=1405841
Thanks for the pointers.
Markus