I am just learning Python 2.0 and have downloaded
wxPython 2.2.2 to check it out for use in a future
project. I am running under Windows NT 4.0 (service
pack 4). I observed a problem with the toolbar
control
demo that gives me great concern about using the
package. Just bringing up the Control wxToolbar demo
seems to cause some trouble when going back to the
tree list of demonstrations. After visiting the
toolbar demo, the application seems to miss a portion
of the clicks to toggle the tree expansion. I also
noticed that when the tooltip for the New button in
the toolbar is displayed, the long description text in
the Status bar stays forever. Also the buttons do not
seem to respond with right click events. Is this
something that others are seeing or is something wrong
with my installation? Perhaps there is there
something wrong with the demo implementation. I would
assume that toolbars are a key part of a lot of user
interfaces and such problems would not be expected.
pack 4). I observed a problem with the toolbar
control
demo that gives me great concern about using the
package. Just bringing up the Control wxToolbar demo
seems to cause some trouble when going back to the
tree list of demonstrations. After visiting the
toolbar demo, the application seems to miss a portion
of the clicks to toggle the tree expansion.
This is a different problem that has been fixed already in CVS. There was a
missing event.Skip() in the dmeo in one of the event handlers for that tree.
It had nothing to do with the toolbar and will happen in other situations
too.
I also
noticed that when the tooltip for the New button in
the toolbar is displayed, the long description text in
the Status bar stays forever.
You can provide a handler for EVT_TOOL_ENTER that sets a timer to clear the
status bar after some number of seconds. I'll update the demo to do this.
Also the buttons do not
seem to respond with right click events. Is this
something that others are seeing or is something wrong
with my installation?
The native toolbar used on MSW doesn't send events for right clicking, so it
is being simulated in wxToolBar. The way it is done the ID of the tool
isn't known at the time so it always sends -1. You can catch it with
EVT_TOOL_RCLICKED(self, -1, self.OnToolRClick) but you can't tell what tool
was clicked... You should probably enter a record in the bug tracker about
this.
Perhaps there is there
something wrong with the demo implementation. I would
assume that toolbars are a key part of a lot of user
interfaces and such problems would not be expected.
Unfortunatly the tool bar is one area where wxWindows is still a little
rough, mainly because of big defferences in the native controls.