On Wed, Sep 23, 2015 at 7:37 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Fri, Sep 18, 2015 at 2:37 PM, Anna Petrášová <kratochanna@gmail.com> wrote:
On Fri, Sep 18, 2015 at 3:55 AM, Markus Neteler <neteler@osgeo.org> wrote:
> For the editing issue, look for ListCtrl_edit in the
> demo (I used 2.8 demo, so hopefully it has the same name in wpython 3
> demo).
Again, ask on mailing list. They will probably suggest you to test newer
wxpython version and then create a ticket, but maybe they have some more
insights.
FYI
I reported it to Fedora's bugzilla, they kindly took care and reported
it upstream:
I installed it and the ListCtrl_edit issue is gone! Who needs a hint
how to get it now, just contact me.
However, iIn some days it will likely be distributed through the
Fedora 22+ update channels anyway.
using the scatterplot tool (I loaded two landsat channels), I found a new issue:
Settings: unable to get value 'scatter:rasters:None'
/usr/lib64/python2.7/site-
packages/wx-3.0-gtk3/wx/lib/plot.py:377: FutureWarning:
comparison to `None` will result in an elementwise object
comparison in the future.
if coord == None:
/usr/lib64/python2.7/site-
packages/wx-3.0-gtk3/wx/lib/plot.py:1201: FutureWarning:
comparison to `None` will result in an elementwise object
comparison in the future.
if xAxis == None or yAxis == None:
It seems to produce the plot anyway but maybe worthwhile fixing.
This happened in G7.0.svn of today.
On Mon, Oct 26, 2015 at 9:53 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
using the scatterplot tool (I loaded two landsat channels), I found a new
issue:
Settings: unable to get value 'scatter:rasters:None'
/usr/lib64/python2.7/site-
packages/wx-3.0-gtk3/wx/lib/plot.py:377: FutureWarning:
comparison to `None` will result in an elementwise object
comparison in the future.
if coord == None:
/usr/lib64/python2.7/site-
packages/wx-3.0-gtk3/wx/lib/plot.py:1201: FutureWarning:
comparison to `None` will result in an elementwise object
comparison in the future.
if xAxis == None or yAxis == None:
It seems to produce the plot anyway but maybe worthwhile fixing.
This happened in G7.0.svn of today.
Yes, it is CheckListCtrlMixin which is unreadable.
I definitely like CheckBox better (also in the past) for the layer
manager. Is there a reason to use CheckListCtrlMixin?
At least I got some insights now how these checkboxes are called...
For the editing issue, look for ListCtrl_edit in the
demo (I used 2.8 demo, so hopefully it has the same name in wpython 3 demo).
Yes, the same name and yes it is broken, too bad. So that's not a GRASS issue.
--- Comment #3 from Scott Talbert <swt@XXXX> ---
Investigated. Looks to be a wxWidgets issue - the
wxRendererNative::DrawCheckBox() function doesn't seem to actually draw the
checkbox when in the checked state. Reported upstream: http://trac.wxwidgets.org/ticket/17240
and immediately fixed there.
Now I expect that it will be backported to Fedora and an update shipped.
Other affected distros may do the same, so if one of you has the same
issue, you may point them to wxWidgets bug#17240.
--- Comment #3 from Scott Talbert <swt@XXXX> ---
Investigated. Looks to be a wxWidgets issue - the
wxRendererNative::DrawCheckBox() function doesn't seem to actually draw the
checkbox when in the checked state. Reported upstream: http://trac.wxwidgets.org/ticket/17240
and immediately fixed there.
Now I expect that it will be backported to Fedora and an update shipped.
This has happened today.
Other affected distros may do the same, so if one of you has the same
issue, you may point them to wxWidgets bug#17240.
In Fedora solved in wxGTK3-3.0.2-11. Buttons look fine again.