Running wxPython 2.8.11...
I was getting strange behavior out of my font dialog on osx, so I just
ran the wxPython demo and popped up the wx.FontDialog from there.
First, the font color always come up green (button at the top). If
you try to change the font color, which pops a color selector dialog,
most of the time, hitting OK in the color selector dialog also closes
down the font dialog.
Does anyone else see this one?
I confirm this behaviour on my macOSx 10.6.4
works fine in windows
On Nov 7, 2:46 am, dhyams <dhy...@gmail.com> wrote:
Running wxPython 2.8.11...
I was getting strange behavior out of my font dialog on osx, so I just
ran the wxPython demo and popped up the wx.FontDialog from there.First, the font color always come up green (button at the top). If
you try to change the font color, which pops a color selector dialog,
most of the time, hitting OK in the color selector dialog also closes
down the font dialog.Does anyone else see this one?
Thanks tinauser; I am using OSX 10.6.4 as well.
I sometimes get Bus errors (application dies) when trying to set the
font color in a wx.FontDialog as well.
On Nov 8, 4:45 am, tinauser <tinau...@libero.it> wrote:
I confirm this behaviour on my macOSx 10.6.4
works fine in windowsOn Nov 7, 2:46 am, dhyams <dhy...@gmail.com> wrote:
> Running wxPython 2.8.11...
> I was getting strange behavior out of my font dialog on osx, so I just
> ran the wxPython demo and popped up the wx.FontDialog from there.> First, the font color always come up green (button at the top). If
> you try to change the font color, which pops a color selector dialog,
> most of the time, hitting OK in the color selector dialog also closes
> down the font dialog.> Does anyone else see this one?
There are already some tickets in Trac for this and similar problems, but the good news is that I wasn't able to duplicate it in my current 2.9 build so it looks like it is fixed there.
On 11/9/10 6:47 AM, dhyams wrote:
Thanks tinauser; I am using OSX 10.6.4 as well.
I sometimes get Bus errors (application dies) when trying to set the
font color in a wx.FontDialog as well.On Nov 8, 4:45 am, tinauser<tinau...@libero.it> wrote:
I confirm this behaviour on my macOSx 10.6.4
works fine in windowsOn Nov 7, 2:46 am, dhyams<dhy...@gmail.com> wrote:
Running wxPython 2.8.11...
I was getting strange behavior out of my font dialog on osx, so I just
ran the wxPython demo and popped up the wx.FontDialog from there.First, the font color always come up green (button at the top). If
you try to change the font color, which pops a color selector dialog,
most of the time, hitting OK in the color selector dialog also closes
down the font dialog.Does anyone else see this one?
--
Robin Dunn
Software Craftsman
Indeed; it does work in the 2.9 branch. Thanks Robin!
On Nov 9, 4:54 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 11/9/10 6:47 AM, dhyams wrote:
> Thanks tinauser; I am using OSX 10.6.4 as well.
> I sometimes get Bus errors (application dies) when trying to set the
> font color in a wx.FontDialog as well.> On Nov 8, 4:45 am, tinauser<tinau...@libero.it> wrote:
>> I confirm this behaviour on my macOSx 10.6.4
>> works fine in windows>> On Nov 7, 2:46 am, dhyams<dhy...@gmail.com> wrote:
>>> Running wxPython 2.8.11...
>>> I was getting strange behavior out of my font dialog on osx, so I just
>>> ran the wxPython demo and popped up the wx.FontDialog from there.>>> First, the font color always come up green (button at the top). If
>>> you try to change the font color, which pops a color selector dialog,
>>> most of the time, hitting OK in the color selector dialog also closes
>>> down the font dialog.>>> Does anyone else see this one?
There are already some tickets in Trac for this and similar problems,
but the good news is that I wasn't able to duplicate it in my current
2.9 build so it looks like it is fixed there.--
Robin Dunn
Software Craftsmanhttp://wxPython.org
Ah, yikes though. My application, which does fine in the 2.8.11
branch, behaves extremely erratically with the 2.9 version (I
installed the mac binary for Python 2.6, and my python version on the
mac is the one from python.org).
It's bizarre...I'm still trying to figure out where the slowdown is
coming from, but it's almost like run-time importing is being
affected. Dropping back to 2.8.11 gives me none of these
problems....also the virtual list ctrl's header is drawn on top of the
actual data in the list.
On Nov 9, 8:30 pm, dhyams <dhy...@gmail.com> wrote:
Indeed; it does work in the 2.9 branch. Thanks Robin!
On Nov 9, 4:54 pm, Robin Dunn <ro...@alldunn.com> wrote:
> On 11/9/10 6:47 AM, dhyams wrote:
> > Thanks tinauser; I am using OSX 10.6.4 as well.
> > I sometimes get Bus errors (application dies) when trying to set the
> > font color in a wx.FontDialog as well.> > On Nov 8, 4:45 am, tinauser<tinau...@libero.it> wrote:
> >> I confirm this behaviour on my macOSx 10.6.4
> >> works fine in windows> >> On Nov 7, 2:46 am, dhyams<dhy...@gmail.com> wrote:
> >>> Running wxPython 2.8.11...
> >>> I was getting strange behavior out of my font dialog on osx, so I just
> >>> ran the wxPython demo and popped up the wx.FontDialog from there.> >>> First, the font color always come up green (button at the top). If
> >>> you try to change the font color, which pops a color selector dialog,
> >>> most of the time, hitting OK in the color selector dialog also closes
> >>> down the font dialog.> >>> Does anyone else see this one?
> There are already some tickets in Trac for this and similar problems,
> but the good news is that I wasn't able to duplicate it in my current
> 2.9 build so it looks like it is fixed there.> --
> Robin Dunn
> Software Craftsmanhttp://wxPython.org
[[ This group prefers bottom-posting. See Top Posting and Bottom Posting and Why is Bottom-posting better than Top-posting ]]
Ah, yikes though. My application, which does fine in the 2.8.11
branch, behaves extremely erratically with the 2.9 version (I
installed the mac binary for Python 2.6, and my python version on the
mac is the one from python.org).
Which version of OSX and how powerful is your Mac's processor, etc.?
It's bizarre...I'm still trying to figure out where the slowdown is
coming from, but it's almost like run-time importing is being
affected. Dropping back to 2.8.11 gives me none of these
problems....
Does the demo have the same problems? Are you doing a lot of drawing with wx.ClientDC's? Anything else that you are doing a lot of that other applications probably don't?
also the virtual list ctrl's header is drawn on top of the
actual data in the list.
It looks okay here with both the carbon and cocoa builds.
On 11/9/10 7:01 PM, dhyams wrote:
--
Robin Dunn
Software Craftsman
[[ This group prefers bottom-posting. Seehttp://idallen.com/topposting.htmlandhttp://www.caliburn.nl/topposting.html]]
> Ah, yikes though. My application, which does fine in the 2.8.11
> branch, behaves extremely erratically with the 2.9 version (I
> installed the mac binary for Python 2.6, and my python version on the
> mac is the one from python.org).Which version of OSX and how powerful is your Mac's processor, etc.?
I'm still running 10.6.2
> It's bizarre...I'm still trying to figure out where the slowdown is
> coming from, but it's almost like run-time importing is being
> affected. Dropping back to 2.8.11 gives me none of these
> problems....Does the demo have the same problems? Are you doing a lot of drawing
with wx.ClientDC's? Anything else that you are doing a lot of that
other applications probably don't?> also the virtual list ctrl's header is drawn on top of the
> actual data in the list.It looks okay here with both the carbon and cocoa builds.
No on the drawing; the weird thing is that there's a major slowdown
during a computational part of the program where I'm showing a
wx.ProgressDialog. After working with things for quite a while last
night, the only thing that I found out was that by removing the call
to Update() for the progress dialog, things returned to normal (albiet
with no progress dlg functionality).
The other thing was that, very weirdly, clicking on things in an
ultimatetreectrl took a long time to register; also, strange dots
appeared in the checkboxes in the tree control.
As far as the misdrawn virtual list ctrl goes, it is basically a pane
within an AUI. I'm going to try putting the list ctrl on a panel, and
then putting the panel within the AUI to see if that makes a
difference. I did see that a virtual list ctrl was drawn just fine in
the wxDemo. It looks, to my untrained eye, that the list ctrl was
drawn first, and then the titlebar for the AUI pane was just drawn
over it. Resizing the AUI pane also did not resize the list ctrl
inside, but that might be a bug on my part, even though it works fine
in 2.8.11.
I'm still working to reduce the problems down to a small code; I
apologize for the extreme vagueness in the description of these
problems. The only reason that I upgraded to 2.9 was to get a fixed
wx.FontDialog, and then things kind of went haywire after that 
On Nov 10, 12:07 am, Robin Dunn <ro...@alldunn.com> wrote:
On 11/9/10 7:01 PM, dhyams wrote: