Between wxPython 2.8.11 and 2.9.1.1, has the toasterbox widget changed
significantly? I'm on OSX 10.6.2, and if I run the toasterbox demo
from 2.8.11, and then the same from 2.9.1.1 (and changing the active
version of wxPython appropriately), the toasterbox widget behaves
quite differently.
Originally, it scrolled up from the bottom as expected...at a
reasonable speed. Now, it just fades in (no scroll up) at a very slow
speed.
Look at a diff of the two versions of the file and read the docstrings. There were lots of changes, including a new scroll style called TB_SCR_TYPE_FADE.
On 11/10/10 5:30 AM, dhyams wrote:
Between wxPython 2.8.11 and 2.9.1.1, has the toasterbox widget changed
significantly? I'm on OSX 10.6.2, and if I run the toasterbox demo
from 2.8.11, and then the same from 2.9.1.1 (and changing the active
version of wxPython appropriately), the toasterbox widget behaves
quite differently.Originally, it scrolled up from the bottom as expected...at a
reasonable speed. Now, it just fades in (no scroll up) at a very slow
speed.
--
Robin Dunn
Software Craftsman
An update on this; I was not ever able to get toasterbox in 2.9.1.1 to
work correctly (meaning it scrolls way too slowly, and setting the
scroll speed seems to get ignored).
If I replace toasterbox.py in the wx 2.9.1.1 distribution with the
version of toasterbox.py from 2.8.11.0, everything works fine. I have
looked at diffs, but have not been able yet to figure out why the
change in behavior. The main change I could see was that a real
wx.Timer() is being used to scroll the window, instead of using
uSleep() as it was done previously. It's possible that dispatching
for wx.Timer is borked in OSX in wxWidgets 2.9.1 similarly to this
report:
http://trac.wxwidgets.org/ticket/12258
On OSX 10.6.5. I have not had a chance to test on other platforms as
of yet.
On Nov 10, 12:54 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 11/10/10 5:30 AM, dhyams wrote:
> Between wxPython 2.8.11 and 2.9.1.1, has thetoasterboxwidget changed
> significantly? I'm onOSX10.6.2, and if I run thetoasterboxdemo
> from 2.8.11, and then the same from 2.9.1.1 (and changing the active
> version of wxPython appropriately), thetoasterboxwidget behaves
> quite differently.> Originally, it scrolled up from the bottom as expected...at a
> reasonable speed. Now, it just fades in (no scroll up) at a very slow
> speed.Look at a diff of the two versions of the file and read the docstrings.
There were lots of changes, including a new scroll style called
TB_SCR_TYPE_FADE.--
Robin Dunn
Software Craftsmanhttp://wxPython.org
Yes, that is the same problem.
On 11/19/10 9:26 PM, dhyams wrote:
An update on this; I was not ever able to get toasterbox in 2.9.1.1 to
work correctly (meaning it scrolls way too slowly, and setting the
scroll speed seems to get ignored).If I replace toasterbox.py in the wx 2.9.1.1 distribution with the
version of toasterbox.py from 2.8.11.0, everything works fine. I have
looked at diffs, but have not been able yet to figure out why the
change in behavior. The main change I could see was that a real
wx.Timer() is being used to scroll the window, instead of using
uSleep() as it was done previously. It's possible that dispatching
for wx.Timer is borked in OSX in wxWidgets 2.9.1 similarly to this
report:
--
Robin Dunn
Software Craftsman
I'm not sure that it is.....it seems the same, but I did patch up my
wxwidgets distro with the fix in that trac reference above, because I
thought it would be fixed by that (along with the progress dialog),
but it was not. Even with the wxTrac has been migrated to GitHub Issues - wxWidgets
fix applied, I still needed to revert to the 2.8.11.0 version of
toasterbox.py in order for it to work correctly.
Or maybe I'm misreading what you're saying...perhaps you're saying
that it's a similar problem, but not the same as what's in that trac;
I can't tell 
On Nov 22, 1:32 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 11/19/10 9:26 PM,dhyamswrote:
> An update on this; I was not ever able to get toasterbox in 2.9.1.1 to
> work correctly (meaning it scrolls way too slowly, and setting the
> scroll speed seems to get ignored).> If I replace toasterbox.py in the wx 2.9.1.1 distribution with the
> version of toasterbox.py from 2.8.11.0, everything works fine. I have
> looked at diffs, but have not been able yet to figure out why the
> change in behavior. The main change I could see was that a real
> wx.Timer() is being used to scroll the window, instead of using
> uSleep() as it was done previously. It's possible that dispatching
> for wx.Timer is borked in OSX in wxWidgets 2.9.1 similarly to this
> report:>wxTrac has been migrated to GitHub Issues - wxWidgets
Yes, that is the same problem.
--
Robin Dunn
Software Craftsmanhttp://wxPython.org
Perhaps there have been some other changes in the trunk besides just that one that have contributed to fixing the problem you are seeing. The Toasterbox scroll speed seems fine to me in my current workspace.
On 11/24/10 9:52 PM, dhyams wrote:
I'm not sure that it is.....it seems the same, but I did patch up my
wxwidgets distro with the fix in that trac reference above, because I
thought it would be fixed by that (along with the progress dialog),
but it was not. Even with the wxTrac has been migrated to GitHub Issues - wxWidgets
fix applied, I still needed to revert to the 2.8.11.0 version of
toasterbox.py in order for it to work correctly.Or maybe I'm misreading what you're saying...perhaps you're saying
that it's a similar problem, but not the same as what's in that trac;
I can't tell
--
Robin Dunn
Software Craftsman