An application that works on wxMacPython is behaving oddly under MS Windows 2000
The current problem:
When the application opens a second frame, the second frame will not accept mouse events. It just 'dings'.
There is no problem when it opens a dialog.
Anyone know what could cause this.
I am using:
Python 2.3.3
wxPythonWIN32-2.5.1.5u-Py23
MS Windows 2000
Thanks ,
-- Brian
P. S. In case your are interested here are a couple of prior differences that I had to work around:
- The windows version will not accept an wxNullBitmap for a tool bar icon
(I used a dummy icon until my artist created the new one)
- The command webbrowser.open_new() requires the "http://" prefix to open the browser
(I changed all of the URL's to include the http prefix)
Are you sure it is a 'ding', and not a 'ping'? We just spent 1.2
million USD for a machine that goes 'ping', and we certainly
don't want a machine that merely goes 'ding', now do we?
An application that works on wxMacPython is behaving oddly under MS Windows 2000
The current problem:
When the application opens a second frame, the second frame will not accept mouse events. It just 'dings'.
There is no problem when it opens a dialog.
Anyone know what could cause this.
Not without more info. Please create a small sample app that shows the problem and send it here.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I found the problem. It appears that the xsMacPython version should not have been working. In the code that was generated by wxGlade for the second frame was the following:
self.Enable(0)
While to my naive eye this looks like a good thing, the documentation says that it is the equivalent of self.Disable. It disables the window for user input. The result is the 'ding'. Apparently I set that parameter by accident in wxGlade and didn't discover it earlier because the Mac version didn't take it seriously.
Thanks,
-- Brian
···
On Tuesday, May 18, 2004, at 04:05 PM, Brian Christensen wrote:
Robin,
Here is a stripped down example that still has the problem:
<App Test Small>
It consists of four small python files and a few of icons.
1) Main.py - opens the first Frame. It contains two buttons that both try to open the second frame
2) Report.py - defines the second frame
3) UI.py - user interface file from wxGlade
4) Menu.py - common routines for the other programs
5) icons - directory w/ icon files for toolbars
On the Mac it works fine. On MS Windows it doesn't
I'm puzzled.
Thanks,
-- Brian
On Tuesday, May 18, 2004, at 01:17 PM, Robin Dunn wrote:
Brian Christensen wrote:
An application that works on wxMacPython is behaving oddly under MS Windows 2000
The current problem:
When the application opens a second frame, the second frame will not accept mouse events. It just 'dings'.
There is no problem when it opens a dialog.
Anyone know what could cause this.
Not without more info. Please create a small sample app that shows the problem and send it here.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
---------------------------------------------------------- http://www.SimpleProjectManagement.com
(What everyone needs to know about project management.)
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
---------------------------------------------------------- http://www.SimpleProjectManagement.com
(What everyone needs to know about project management.)
Here is a stripped down example that still has the problem:
I see you've solved this so instead I'll just a comment on how you sent it:
<rant>
62k worth of attachments is not very stripped down. A .zip or .tar.gz file would have been better, but only if you could get it under 10k or so. Recreating the app without as many (or any) of the bitmaps would have been even more better. And best is creating a new app (by hand) that does nothing but show the problem.
Sending lare apps and lots of attachments to a mail list is considered bad etiquette and probably less than 1% of the hundreds of subscribers to this list would be interested in looking at it. For everybody else it is just wasted bandwidth and noise. On the other hand if you had done it as a small app that doesn't do much besides show the problem then you could have had a half dozen responses within 30 minutes (if you hadn't already solved it yourself in the process of reducing it.)
</rant>
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
