[GRASS-dev] [GRASS GIS] #3487: vector digitizer unstable

[GRASS GIS]

#3487: vector digitizer unstable
------------------------+-------------------------------
  Reporter:  cmbarton   |      Owner:  grass-dev@…
      Type:  defect     |     Status:  new
  Priority:  critical   |  Milestone:  7.6.1
 Component:  wxGUI      |    Version:  7.2.2
Resolution:             |   Keywords:  digitizer, ctypes
       CPU:  OSX/Intel  |   Platform:  MacOSX
------------------------+-------------------------------

Comment (by cmbarton):

 Replying to [comment:17 neteler]:
 > Replying to [comment:15 cmbarton]:
 > > Unfortunately, I can't test this until we figure out why configure is
 looking for cpp and bombing when it doesn't find it now.
 >
 > I'd suggest to move this to the 7.8 milestone, with focus on Python-3.

 GRASS is compiling again. So I can test any fix.

  I disagree with kicking this can down the road even farther. Digitizing
 has been broken on the Mac since 7.2. And now we are at 7.7 in trunk. It
 is a serious problem if you can't digitize in a full-featured GIS. I am
 skeptical that it is something that Python 3 will magically solve.
 Previously, the thought was that moving from 32 bit wxPython 2.8.12 to 64
 bit wxPython 3 would fix it. We are now using wxPython 4.0.1 on the Mac
 and it still crashes.

 It has something to do with how interactive windows are being
 defined/created because the same problem affects the interactive
 supervised classification interface. But is does NOT affect other
 interactive window functions like measurement and selection. One clue to
 tracking the bug perhaps is the following. In the digitizer, it does not
 crash as soon as the digitizing functions are invoked, but only when a new
 vector layer to be digitized is defined and "OK" is pressed. For the
 supervised classification, it crashes as soon as the interface is called.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3487#comment:18>
GRASS GIS <https://grass.osgeo.org>