[wingide-users] Wing v2.1.4 works, v3.1.8 does not
Mark A. Schmucker
masc at rincon.com
Tue Mar 31 10:21:08 MDT 2009
> Does it not paint if you then continue from the breakpoint?
It paints only partially if I continue. It also receives only certain mouse inputs if I continue- for example I can resize my app's mainframe, but not push toolbar buttons. (I do understand that it can't possibly paint if I'm sitting on a breakpoint.)
Also note this is largely a single-threaded application. I'm breaking in the one-and-only thread.
> does obscuring and revealing the window again draw everything or just a sub-part again
Just a sub-part. It's as if certain subwindows have died or something.
Meanwhile I'm fine with using the older version of Wing, so maybe just keep it in mind in case anyone else notices similar behavior and can characterize it better than I have.
From: Wingware Support [mailto:support at wingware.com]
Sent: Tuesday, March 31, 2009 8:45 AM
To: Mark A. Schmucker
Cc: wingide-users at wingware.com
Subject: Re: [wingide-users] Wing v2.1.4 works, v3.1.8 does not
Mark A. Schmucker wrote:
> I'm developing a graphics-intensive app using wxWidgets. I have
> previously been using Wing v2.1.4 successfully to debug my app. Now
> I'm setting up my project on a new computer, and I took this
> opportunity to try v3.1.8. (Note v2.1.4 was never installed on this
> When I debug my project from Wing, it sort of works- the debugger
> starts and can hit at least some breakpoints- but my app doesn't paint
> correctly. Only part of my app's window paints itself. And my app
> doesn't get all the mouse messages, as far as I can tell.
> I uninstalled v3.1.8 and installed v2.1.4. Now everything works. So
> what's wrong with v3.1.8?
I suspect the issue is that Wing 3.x will stop all threads when one thread is stopped and your main loop is not getting time when the debugger is paused or at a breakpoint. Under Wing 2.x if you stop in a thread other than the main loop, I could see that drawing/etc might still continue because that version of Wing would only stop one debug thread and was essentially unaware of the others.
Does it not paint if you then continue from the breakpoint? In general, I would expect it to paint then without failing to paint some parts, but perhaps some of the events are being lost if they came in while the debug process is paused.
If it does fail to paint, does obscuring and revealing the window again draw everything or just a sub-part again?
Wingware | Python IDE
Advancing Software Development
More information about the wingide-users