On Fri, Apr 13, 2012 at 09:55:51AM +0200, Edward d'Auvergne wrote:
Hi Jack,
I've now fully tested the current relax 1.3 main line against the
Python+wxGTK from fink, and everything works perfectly! The test
suite passes without issue. In the process I removed a few small bugs
affecting relax GUI users on all operating systems. The only problem
remaining for the fink release is the starting refresh problem you
see. As I cannot reproduce this, and that the relax GUI refuses to
maximise when using wxPython with the native Mac widgets (both via
Carbon and Cocoa), I will now implement some basic infrastructure for
handling different wxPython versions (Linux GTK vs. Windows native vs.
Mac GTK vs. Mac native (carbon) vs. Mac native (cocoa) as well as wx
2.8 vs. 2.9, etc.). This will allow me to skip the calls to maximise
on the Mac platforms.
Once everything works on the Mac, I will release relax 1.3.15. In the
mean time, are you able to test on the 1.3 main line? Do you have
subversion installed?
Edward,
I'll try the relax 1.3 svn over the weekend. Earlier this week I did
try to create
a wxcocoa293-py package for fink but the resulting build claims it can
only
access the screen with a framework build of python. Things get even
stranger
on MacPorts which does have a framework build of python and a set of
wxwidgets-devel/py27-wxpython-devel packages for 2.9.3.1. According to the
documentation in wxPython 2.9.3.1, you are supposed to use the
build-wxpython.py
script now (which on fink produces two dylibs (cocoa/cocoa_gl suffixed).
The
MacPorts' py27-wxpython-devel build doesn't produce these but uses
setup.py
instead. I'll have to check with upstream about this issue. If a
frameworks
build of python is really required for cocoa to access the screen, this
pretty
much nixes the option on fink as it will be a major exercise to switch all
of the -py package variants to install in a framework based fink python.
Jack
Cheers,
Edward
On 12 April 2012 14:28, Edward d'Auvergne <edward@xxxxxxxxxxxxx> wrote:
Hi,
I would prefer to have the same behaviour on all platforms of starting
maximised, but if this problem cannot be solved, then starting
non-maximised is an option. I really don't know why your set up does
not get refreshed whereas on mine I do have a refresh. Are you using
the newest wxPython 2.18.2.1 version? Could you send the output of
'relax -i' once again, just in case it has changed. As for forcing
the refresh, I have included a diff below which might fix the problem
(although I think it could be deeper). Are you able to make that
change and test it? Cheers! I am also making all changes in the main
1.3 line rather than in the tagged 1.3.14 version. I am still in the
process of stress testing the GUI using the fink versions of
Python+modules, so maybe I will still encounter a problem or two, the
solution of which may fix this refresh problem anyway.
Cheers,
Edward
P. S. The diff is:
Index: gui/relax_gui.py
===================================================================
--- gui/relax_gui.py (revision 15693)
+++ gui/relax_gui.py (working copy)
@@ -158,7 +158,11 @@
if script:
wx.CallAfter(user_functions.script.script_exec, script)
+ # Screen refresh fix for the Mac OS X fink version.
+ self.Layout()
+ self.Refresh()
+
def about_gui(self, event):
"""The about message for the relax GUI.
Re: relax 1.3.13/14 oddities