On 21 Feb 2002, Rick Romero wrote: > Hi all, > > I need some assistance.. I'm trying to trace a problem. The quick > description is when I run the Visual FoxPro 5 development environment, > and I click in a 'edit' window (like when you bring your program up, to > edit it) the screen freezes. > > when I ran wine --debugmsg +win vfp.exe, my last line of trace is: > trace:win:EVENT_Capture (0x20021) > > Where the heck is the code that calls setcapture for Foxpro? I didn't > think I needed to, but do I have to get into those spec files also? > > Is there somewhere, other than what grep returns, that would call that > function? I'm definately not an expert here, but I *think* I should be > able to trace a function on my own :) Err, yes. The app, or a native dll used by the app can call SetCapture itself, unless I misread the .spec files. > > My wine is cvs build 2/20/2002, using fake_windows. > > Any suggestions would be appreciated. (Should I send this to > wine-devel?) > You might try if you get any joy out of --debugmsg +snoop Or try winedbg and set a breakpoint. Lawson ---oof--- _______________________________________________ wine-users mailing list wine-users@winehq.com http://www.winehq.com/mailman/listinfo/wine-users
