[GRASS-dev] Re: [GRASS-user] error message from GRASS 7 on mac os

2012-03-18 Thread Michael Barton
It's good to finally find out where these start-up errors are coming from. The easiest workaround is simply not to use AdvancedSplashScreen. AFAICT, there is no point to using this at the present, since all the arguments we are using are the same for the normal wx.SplashScreen and the wx.Advance

[GRASS-dev] Re: [GRASS-user] error message from GRASS 7 on mac os

2012-03-18 Thread Michael Barton
Since wx.CallAfter does not solve this, the only sure-fire fix that I can find is to either revert to the standard wx.SplashScreen or to replace line 59 in wxgui.py with: if SC and sys.platform != 'darwin': That way, at least the Macs default to the basic splash screen without the erro

[GRASS-dev] Re: [GRASS-user] error message from GRASS 7 on mac os

2012-03-20 Thread Anna Kratochvílová
2012/3/19 Michael Barton : > Since wx.CallAfter does not solve this, the only sure-fire fix that I can > find is to either revert to the standard wx.SplashScreen or to replace line > 59 in wxgui.py with: > >        if SC and sys.platform != 'darwin': > > That way, at least the Macs default to the

[GRASS-dev] Re: [GRASS-user] error message from GRASS 7 on mac os

2012-03-20 Thread Michael Barton
OK. I'll update GRASS 7 soon. I'm uncertain of how to backport this, however. Are the versions enough in sync to do a standard backport to GRASS 6.4.3? Also, are we still maintaining GRASS 6.5? If so, how does it differ from 6.4.3? Cheers Michael On Mar 20, 2012, at 2:46 AM, Anna Kratochvílová

[GRASS-dev] Re: [GRASS-user] error message from GRASS 7 on mac os

2012-03-20 Thread Martin Landa
Hi, Dne 21. března 2012 0:46 Michael Barton napsal(a): > OK. I'll update GRASS 7 soon. I'm uncertain of how to backport this, however. > Are the versions enough in sync to do a standard backport to GRASS 6.4.3? > Also, are we still maintaining GRASS 6.5? If so, how does it differ from > 6.4.3?

[GRASS-dev] Re: [GRASS-user] error message from GRASS 7 on mac os

2012-03-21 Thread Michael Barton
OK. I've updated this in trunk and backported to 6.4 dev branch and release branch. Michael On Mar 20, 2012, at 2:46 AM, Anna Kratochvílová wrote: > 2012/3/19 Michael Barton : >> Since wx.CallAfter does not solve this, the only sure-fire fix that I can >> find is to either revert to the standa