AFAIK, the digitizer is still broken in the Mac and there are a couple of other problems, especially one with a pull-down control that doesn't work.
Also, copy/paste is erratic and largely broken (needs correct key mappings I suppose).
All are on Trac
Michael
______________________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://csdc.asu.edu, http://shesc.asu.edu
http://www.public.asu.edu/~cmbarton
On 4/26/18, 3:59 AM, "grass-dev on behalf of grass-dev-request@lists.osgeo.org" <grass-dev-bounces@lists.osgeo.org on behalf of grass-dev-request@lists.osgeo.org> wrote:
Date: Wed, 25 Apr 2018 14:16:52 -0700 (MST)
From: Helmut Kudrnovsky <hellik@web.de>
To: grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] [release planning] 7.4.1
Message-ID: <1524691012841-0.post@n6.nabble.com>
Content-Type: text/plain; charset=us-ascii
Markus Neteler wrote
>Hi devs,
>according to our roadmap [1] it is time to prepare 7.4.1RC1:
>Time schedule:
>Proposal of release: ~14 Mar
>Soft freeze of release branch: ~23 Mar
>RC1: ~23 Apr <<-- we are here
>RC2: ~7 May
>Final release: ~14 May
>We have no blockers any more [2].
>If there are no objections, I'll prepare RC1 in the next few days.
+1
As daily winGRASS builds seems to be broken for some times now, it may be
needed to find a way to test the RCs.
Hi,
2018-04-26 18:40 GMT+02:00 Michael Barton <Michael.Barton@asu.edu>:
AFAIK, the digitizer is still broken in the Mac and there are a couple of other problems, especially one with a pull-down control that doesn't work.
Also, copy/paste is erratic and largely broken (needs correct key mappings I suppose).
I am afraid it can be hardly blocker. There must be someone who will
invest time to fix digitizer on Mac. I don't know about anyone. Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
The broken digitizer appears to be a consequence of moving Mac compiling to wxPython 3 from the old wxPython 2.8 that Linux and (I think) Windows still use (wxPython 4 is now the current version and the digitizer is broken in that version too). Note that wxPython 2.8 is 32 bit and most of the rest of GRASS is now 64 bit. Unless someone has tried new wxPython with GRASS on another platform, there is a reasonable chance that this same bug will crop up elsewhere. It also looks like it may be the same bug that crashes interactive imagery classifier interface.
Beyond that, dismissing a serious problem for an entire platform of users doesn't seem a good idea.
Michael
______________________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://csdc.asu.edu, http://shesc.asu.edu
http://www.public.asu.edu/~cmbarton
On 4/26/18, 10:15 AM, "Martin Landa" <landa.martin@gmail.com> wrote:
Hi,
2018-04-26 18:40 GMT+02:00 Michael Barton <Michael.Barton@asu.edu>:
> AFAIK, the digitizer is still broken in the Mac and there are a couple of other problems, especially one with a pull-down control that doesn't work.
>
> Also, copy/paste is erratic and largely broken (needs correct key mappings I suppose).
I am afraid it can be hardly blocker. There must be someone who will
invest time to fix digitizer on Mac. I don't know about anyone. Martin
--
Martin Landa
Ing. Martin Landa, Ph.D. – GeoWikiCZ
Martin Landa - GISMentors
On Thu, Apr 26, 2018 at 8:41 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
The broken digitizer appears to be a consequence of moving Mac compiling to wxPython 3 from the old wxPython 2.8 that Linux and (I think) Windows still use (wxPython 4 is now the current version and the digitizer is broken in that version too).
It got released earlier this year: 2018-01-31
https://wxpython.org/news/wxpython-4.0.0-release/index.html
That means it will take time yet to reach all the various distros.
Note that wxPython 2.8 is 32 bit and most of the rest of GRASS is now 64 bit.
... on Mac OS X.
Unless someone has tried new wxPython with GRASS on another platform, there is a reasonable chance that this same bug will crop up elsewhere. It also looks like it may be the same bug that crashes interactive imagery classifier interface.
Right but so far there are no(t too many) production ready distros
shipping wxPython 4 (I checked Fedora and Debian).
Beyond that, dismissing a serious problem for an entire platform of users doesn't seem a good idea.
As Martin said: we need volunteers for that and they need to have
access to Mac OS X.
Anyone able to help here?
Markus
PS: I'd rather not postpone the next release for too long.
On 30/04/18 00:03, Markus Neteler wrote:
On Thu, Apr 26, 2018 at 8:41 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
The broken digitizer appears to be a consequence of moving Mac compiling to wxPython 3 from the old wxPython 2.8 that Linux and (I think) Windows still use (wxPython 4 is now the current version and the digitizer is broken in that version too).
It got released earlier this year: 2018-01-31
https://wxpython.org/news/wxpython-4.0.0-release/index.html
That means it will take time yet to reach all the various distros.
Note that wxPython 2.8 is 32 bit and most of the rest of GRASS is now 64 bit.
... on Mac OS X.
Unless someone has tried new wxPython with GRASS on another platform, there is a reasonable chance that this same bug will crop up elsewhere. It also looks like it may be the same bug that crashes interactive imagery classifier interface.
Right but so far there are no(t too many) production ready distros
shipping wxPython 4 (I checked Fedora and Debian).
It is in Debian testing [1], so will (normally) be in next Debian stable.
But IIUC, the crash in MacOSX is not due to wxPython 4, but rather to wxPython 3 (which is already in Debian stable). Michael, do I understand this correctly ? Is there a bug report with a reproducible example somewhere ?
Moritz
[1] https://packages.debian.org/source/buster/wxpython4.0
The crash is in both wxPython 3 and 4. There is a bug report with output text and a link to a possible lead on what is wrong. You can reproduce this on any of the new Mac binaries.
Michael
_________________________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On 4/30/18, 7:09 AM, "Moritz Lennert" <mlennert@club.worldonline.be> wrote:
On 30/04/18 00:03, Markus Neteler wrote:
> On Thu, Apr 26, 2018 at 8:41 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
>> The broken digitizer appears to be a consequence of moving Mac compiling to wxPython 3 from the old wxPython 2.8 that Linux and (I think) Windows still use (wxPython 4 is now the current version and the digitizer is broken in that version too).
>
> It got released earlier this year: 2018-01-31
> wxPython 4.0.0 Released | wxPython
>
> That means it will take time yet to reach all the various distros.
>
>> Note that wxPython 2.8 is 32 bit and most of the rest of GRASS is now 64 bit.
>
> ... on Mac OS X.
>
>> Unless someone has tried new wxPython with GRASS on another platform, there is a reasonable chance that this same bug will crop up elsewhere. It also looks like it may be the same bug that crashes interactive imagery classifier interface.
>
> Right but so far there are no(t too many) production ready distros
> shipping wxPython 4 (I checked Fedora and Debian).
It is in Debian testing [1], so will (normally) be in next Debian stable.
But IIUC, the crash in MacOSX is not due to wxPython 4, but rather to
wxPython 3 (which is already in Debian stable). Michael, do I understand
this correctly ? Is there a bug report with a reproducible example
somewhere ?
Moritz
[1] Debian -- Details of source package wxpython4.0 in buster
On Mon, Apr 30, 2018 at 9:19 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
The crash is in both wxPython 3 and 4. There is a bug report with output text and a link to a possible lead on what is wrong. You can reproduce this on any of the new Mac binaries.
Is it this report?
https://trac.osgeo.org/grass/ticket/3471
Markus
No. This is the more fixable but less critical pull custom down list control. When I get back to my computer I’ll look for the trac report
Michael Barton
School of Human Evolution &Social Change
Center for Social Dynamics & Complexity
Arizona State University
...Sent from my iPad
On May 4, 2018, at 11:30 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Mon, Apr 30, 2018 at 9:19 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
The crash is in both wxPython 3 and 4. There is a bug report with output text and a link to a possible lead on what is wrong. You can reproduce this on any of the new Mac binaries.
Is it this report?
#3471 (Custom dropdown control doesn’t recognize mouse events) – GRASS GIS
Markus
Here is the relevant Trac report
https://trac.osgeo.org/grass/ticket/3487
Michael
_________________________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On 5/4/18, 12:58 PM, "Michael Barton" <Michael.Barton@asu.edu> wrote:
No. This is the more fixable but less critical pull custom down list control. When I get back to my computer I’ll look for the trac report
Michael Barton
School of Human Evolution &Social Change
Center for Social Dynamics & Complexity
Arizona State University
...Sent from my iPad
> On May 4, 2018, at 11:30 AM, Markus Neteler <neteler@osgeo.org> wrote:
>
>> On Mon, Apr 30, 2018 at 9:19 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
>> The crash is in both wxPython 3 and 4. There is a bug report with output text and a link to a possible lead on what is wrong. You can reproduce this on any of the new Mac binaries.
>
> Is it this report?
> #3471 (Custom dropdown control doesn’t recognize mouse events) – GRASS GIS
>
> Markus