Run attachment. Notice that text shows on the keyboard buttons on Windows and Linux, but text is shown on Mac.
Details:
OSX: Maverics
wxPython: 2.9.5.0
Python: 2.7.5
Ideas?
keybutton.py (18.3 KB)
Run attachment. Notice that text shows on the keyboard buttons on Windows and Linux, but text is shown on Mac.
Details:
OSX: Maverics
wxPython: 2.9.5.0
Python: 2.7.5
Ideas?
keybutton.py (18.3 KB)
Just s you know,
I poked at this a bit, and see exactly the same symptoms.
But I didn’t do the next obvious step and try a couple simple test or two of DrawText in a really simple app all by itself – is that working?
-Chris
On Sat, Nov 9, 2013 at 6:34 AM, Edward Sitarski edward.sitarski@gmail.com wrote:
Run attachment. Notice that text shows on the keyboard buttons on Windows and Linux, but text is shown on Mac.
Details:
OSX: Maverics
wxPython: 2.9.5.0
Python: 2.7.5
Ideas?
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
One other thought:
You could try doing the really kludgy thing and using DC.DrawText instead – maybe it would be different?
-Chris
On Wed, Nov 13, 2013 at 8:36 AM, Chris Barker chris.barker@noaa.gov wrote:
Just s you know,
I poked at this a bit, and see exactly the same symptoms.
But I didn’t do the next obvious step and try a couple simple test or two of DrawText in a really simple app all by itself – is that working?
-Chris
–
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
On Sat, Nov 9, 2013 at 6:34 AM, Edward Sitarski edward.sitarski@gmail.com wrote:
Run attachment. Notice that text shows on the keyboard buttons on Windows and Linux, but text is shown on Mac.
Details:
OSX: Maverics
wxPython: 2.9.5.0
Python: 2.7.5
Ideas?
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris, I really appreciate your help.
Unfortunately, DC.DrawText does not work either in the example.
My suspicion is that there is something going wrong with fonts on the Mac and wxPython, however, there may be
I have been trying to port my app CrossMgr (source here), and anything to do with fonts or font sizes is not going well.
It is “sort of” running, but problems remain with custom buttons, layouts, printing and print preview (rather important features in race results software).
See the smaller attached example for a button-font-sizing problem (more to come). Huh?
Probably unrelated, but the executable created by pyinstaller crashes. Is that the right tool to use to make a distribution for Mac?
The Mac was a surprise based on my experience with wxPython on Windows and Linux. I expected to copy the git repo, run my app “python MainWin.py”, run pyinstaller, create the dmg and crack open a beer.
No beer yet - the problems started when I had to install the dmg manually, and I have continued to struggle with brew, PYTHONPATH and a long list of stuff that doesn’t work (I will continue to try to get simpler examples).
Did OSX Maverics destabilize wxPython, or is this normal?
gbsTest.py (851 Bytes)
On Wednesday, November 13, 2013 11:37:18 AM UTC-5, Chris Barker wrote:
One other thought:
You could try doing the really kludgy thing and using DC.DrawText instead – maybe it would be different?
-Chris
On Wed, Nov 13, 2013 at 8:36 AM, Chris Barker chris....@noaa.gov wrote:
Just s you know,
I poked at this a bit, and see exactly the same symptoms.
But I didn’t do the next obvious step and try a couple simple test or two of DrawText in a really simple app all by itself – is that working?
-Chris
On Sat, Nov 9, 2013 at 6:34 AM, Edward Sitarski edward....@gmail.com wrote:
Run attachment. Notice that text shows on the keyboard buttons on Windows and Linux, but text is shown on Mac.
Details:
OSX: Maverics
wxPython: 2.9.5.0
Python: 2.7.5
Ideas?
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
Christopher Barker, Ph.D.
OceanographerEmergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
–
Christopher Barker, Ph.D.
OceanographerEmergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 faxSeattle, WA 98115 (206) 526-6317 main reception
Chris, I really appreciate your help.
I wish I had more time to poke into it...
Unfortunately, DC.DrawText does not work either in the example.
hmm -- that isn't completely broken, It's working for a bunch of my stuff.
My suspicion is that there is something going wrong with fonts on the Mac
and wxPython,
Indeed -- I see below that you're using "Maverics " (is that 10.9? -- I
hate these non-sortable names...)? See this list, there are other issues
with fonts and wx and Maverics.
But I'm running 10.7 now, and don't see the text in that example either, so
it's not that. But that reminds me -- try changing the font (ideally
to something default, and see what you get -- it's possible you're getting
dud font in that case (I haven't looked at what you're doing though)
I have been trying to port my app CrossMgr<http://www.sites.google.com/site/crossmgrsoftware> (source
here <https://github.com/esitarski/CrossMgr>\), and anything to do with
fonts or font sizes is not going well.
It is "sort of" running, but problems remain with custom buttons, layouts,
printing and print preview (rather important features in race results
software).See the smaller attached example for a button-font-sizing problem (more to
come). Huh?
yeah -- we recently discovered a button-0sizing issue -- again, not
Maverics. I posted a suggestion on that one.
Probably unrelated, but the executable created by pyinstaller crashes. Is
that the right tool to use to make a distribution for Mac?
I've always used py2app instead, and it's getting at least a modicum
of maintenance lately, worth a try. OS-X support for pyinstaller is
relatively new, and I have no idea how well tested.
The Mac was a surprise based on my experience with wxPython on Windows and
Linux. I expected to copy the git repo, run my app "python MainWin.py",
run pyinstaller, create the dmg and crack open a beer.No beer yet - the problems started when I had to install the dmg manually,
and I have continued to struggle with brew, PYTHONPATH and a long list of
stuff that doesn't work (I will continue to try to get simpler examples).
I suspect if you want to create re-distributable binary bundles, you want
to stay away from brew and macports, and... they are really designed for
built it on your own machine....
Also, if you want to re-distribute binaries that work on older Macs, you
might want to build on an older Mac -- Apple makes it pretty hard to build
for older systems. Note: if you don't have ny other complex dependencies,
you can use the python.org python and the wxPython binaries, and be OK.
Did OSX Maverics destabilize wxPython, or is this normal?
I haven't used it, but it does seem to have caused a number of problems,
But the Mac has always been:
1) a little more "different" than the other platforms
2) Cocoa added another level of things that work different than a) other
platforms, and b) the previous wx versions.
3) It just doesn't get the same level of testing or developer suport, so
things are a bit more problematic
All that being said it's mostly worked for a number of us. You probably
need to just get over a hump here.
-Chris
On Wed, Nov 13, 2013 at 9:36 AM, Edward Sitarski <edward.sitarski@gmail.com>wrote:
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
Edward Sitarski wrote:
Run attachment. Notice that text shows on the keyboard buttons on
Windows and Linux, but text is shown on Mac.Details:
OSX: Maverics
wxPython: 2.9.5.0
Python: 2.7.5Ideas?
Debugging technique #37: Comment everything out and slowly add it back in until the error happens again. Whatever changed in that step, no matter how unlikely, must be the source of the problem.
In this case it was how you were resetting the clip region, by passing a default wx.Region(). Apparently that works unintentionally on the other platforms, but on OSX it needs to be done with ResetClip() instead.
gc.ClipRegion( wx.Region(xMiddle, 0, width, height) )
gc.FillPath( innerRoundedRect )
##gc.ClipRegion( wx.Region() )
gc.ResetClip()
--
Robin Dunn
Software Craftsman
Thanks Robin - I really appreciate it. I spent hours looking at the code - and commenting lines out. I missed that one.
On Tuesday, December 17, 2013 11:59:02 PM UTC-5, Robin Dunn wrote:
Edward Sitarski wrote:
Run attachment. Notice that text shows on the keyboard buttons on
Windows and Linux, but text is shown on Mac.
Details:
OSX: Maverics
wxPython: 2.9.5.0
Python: 2.7.5
Ideas?
Debugging technique #37: Comment everything out and slowly add it back
in until the error happens again. Whatever changed in that step, no
matter how unlikely, must be the source of the problem.In this case it was how you were resetting the clip region, by passing a
default wx.Region(). Apparently that works unintentionally on the other
platforms, but on OSX it needs to be done with ResetClip() instead.gc.ClipRegion( wx.Region(xMiddle, 0, width, height) ) gc.FillPath( innerRoundedRect ) ##gc.ClipRegion( wx.Region() ) gc.ResetClip()
–
Robin DunnSoftware Craftsman