February 2003 - Wine-Devel - list.winehq.org

Re: Report after porting a windows app to WINE

by Mike Hearn

> Thank-you . No debugmsg when I press F6. Any idea where I > change that in the window manager? I only know in GNOME2 it's in desktop preferences -> keyboard shortcuts. By default I don't think F6 is actually bound to anything. As I said, try it in fluxbox or something > --Mike >

Feb. 28, 2003

Re: Consoles (1/3)

by Sylvain Petreolle

--- Eric Pouech <eric.pouech(a)wanadoo.fr> a écrit : > Sylvain Petreolle wrote: > > how to continue to have a separate window with this patch applied ? > you can't with current CVS (as I wrote in a previous mail, I'll > submit > something RSN) > > > this break some functions in wcmd. > you should run wineconsole wcmd not wcmd if you want console support agreed, but this doesnt allow to use the system menu anymore, and corrupts DOS application screen with debug messages. I cant even do a mouse-copy on the text without doing a redirection. ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight Spam ! EuroCauce: http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Mike Engelhardt

Mike, > > > I put a messagebox in OnKeyUp() to tell me what nChar it's getting. > > > It enters OnKeyUp() for every function key except F6. If I hold > > > down the control key, then it also get's F6 and it get's it with the right > > > key code, 117. Could Gnome be trapping that key for something? > > > > Yes, that's possible. Like I said, use the channels Luke! > > > > wine --debugmsg +keyboard foo.exe > > > > then watch what is printed when you hit a key. If nothing appears when > > you press F6, probably the window manager is eating it before it gets to > > wine (try running it in a different setup to test that theory). Thank-you . No debugmsg when I press F6. Any idea where I change that in the window manager? --Mike

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Mike Hearn

> I put a messagebox in OnKeyUp() to tell me what nChar it's getting. > It enters OnKeyUp() for every function key except F6. If I hold > down the control key, then it also get's F6 and it get's it with the right > key code, 117. Could Gnome be trapping that key for something? Yes, that's possible. Like I said, use the channels Luke! wine --debugmsg +keyboard foo.exe then watch what is printed when you hit a key. If nothing appears when you press F6, probably the window manager is eating it before it gets to wine (try running it in a different setup to test that theory). > Other than that, I put up a new version today, 2.01c, that works > pretty well under WINE except for this F6 issue and that the > RoboHelp system does't work yet. > > --Mike >

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Mike Engelhardt

----- Original Message ----- From: "Mike Hearn" <mike(a)theoretic.com> To: "Mike Engelhardt" <pmte(a)concentric.net> Cc: <wine-devel(a)winehq.com> Sent: Friday, February 28, 2003 1:52 PM Subject: Re: Report after porting a windows app to WINE > On Fri, 2003-02-28 at 21:19, Mike Engelhardt wrote: > > Mike, > > > > > > 3. Function key F6 is not trapped. > > > > > > Can you explain this one a bit further? You mean Wine doesn't > > > forward it to the app? > > > > The function looks like this: > > > > void CecsView::OnKeyUp(UINT nChar, UINT nRepCnt, UINT nFlags) > > { > > Bear in mind quite a few people here don't know C++ :) I get the idea > though. > > > Pressing F2, F3, F4, F5, F7, F8 and F9 all go to > > the right place. Nothing happens when F6 is pressed. Why > > is that? > > No idea, but that kind of thing should be fairly easy to debug, it's > probably just a missed out or incorrect table entry. Try reading the > part about debug channels in the users guide and looking at keyboard > logs. I put a messagebox in OnKeyUp() to tell me what nChar it's getting. It enters OnKeyUp() for every function key except F6. If I hold down the control key, then it also get's F6 and it get's it with the right key code, 117. Could Gnome be trapping that key for something? Other than that, I put up a new version today, 2.01c, that works pretty well under WINE except for this F6 issue and that the RoboHelp system does't work yet. --Mike

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Mike Hearn

> I thought I had reported bugs in my first breath. Doesn't change my > requirement to have my app run under 95, 98, Me, NT, 2K, XP and any > reasonably recent release of Wine. Each OS as had it's own share of > workarounds required as is common for a really large app. Anyway, I > don't find it unreasonable to have to work around specific bugs in > specific OS's. Well yes, but Wine isn't meant to be a specific OS as such, it's meant to emulate any version of Windows required. I mean you can work around problems in Wine, but ideally we'd be altering our bugs to match those in the real Windows, that makes peoples lives easier in future (users and developers). Bear in mind that while you _have_ to work around bugs in Windows because of the slow release cycle and closed source nature, in Wine it's possible to fix the bugs directly, so you shouldn't treat them the same way. BTW to be most useful a bugreport would ideally be in bugzilla with the relevant parts of the traces, although debugging such things yourself is usually the best approach. thanks -mike

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Mike Hearn

On Fri, 2003-02-28 at 21:19, Mike Engelhardt wrote: > Mike, > > > > 3. Function key F6 is not trapped. > > > > Can you explain this one a bit further? You mean Wine doesn't > > forward it to the app? > > The function looks like this: > > void CecsView::OnKeyUp(UINT nChar, UINT nRepCnt, UINT nFlags) > { Bear in mind quite a few people here don't know C++ :) I get the idea though. > Pressing F2, F3, F4, F5, F7, F8 and F9 all go to > the right place. Nothing happens when F6 is pressed. Why > is that? No idea, but that kind of thing should be fairly easy to debug, it's probably just a missed out or incorrect table entry. Try reading the part about debug channels in the users guide and looking at keyboard logs.

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Alexandre Julliard

"Mike Engelhardt" <pmte(a)concentric.net> writes: > All this time the worker thread, having done a > SendMessage() and not a PostMessage(), is frozen waiting > for the return value of the number of points so it can > decide where to try again or continue. The scheme that > I'm using has been extensively debugged and used under > 95,98,Me,NT,2K, and XP. But under wine, the worker thread > doesn't freeze when it calls SendMessage() but keeps > executing. This definitely doesn't sound right. If you have a chance, could you please do a --debugmsg +server,+message trace showing the problem? That would help a lot in tracking this down. -- Alexandre Julliard julliard(a)winehq.com

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Mike Engelhardt

Mike, > > 3. Function key F6 is not trapped. > > Can you explain this one a bit further? You mean Wine doesn't > forward it to the app? The function looks like this: void CecsView::OnKeyUp(UINT nChar, UINT nRepCnt, UINT nFlags) { . . . if (113 == nChar) // F2, add component OnPlaceComp(); else if(114 == nChar) // F3, add wire OnDrawWires(); else if(115 == nChar) // F4, place net OnPlaceNet(); else if((116 == nChar) || (46 == nChar)) // F5(or delete key), delete stuff OnDeleteStuff(); else if(117 == nChar) // F6, duplicate stuff OnDuplicate(); else if(118 == nChar) // F7, move stuff OnMoveStuff(); else if(119 == nChar) // F8, drag stuff OnDragStuff(); else if(120 == nChar) // F9, undo HistoryUndoStep(); . . . CScrollView::OnKeyUp(nChar, nRepCnt, nFlags); } Pressing F2, F3, F4, F5, F7, F8 and F9 all go to the right place. Nothing happens when F6 is pressed. Why is that?

Feb. 28, 2003

Re: Report after porting a windows app to WINE

by Mike Engelhardt

Eric , >>>I would like to know if there is a way to determine if my app is running >>>under WINE under runtime. That way I can work around more of these >>>problems without imparing its performance under MS Windows. If you know >>>the answer, please e-mail me directly. > >the real best way is to fix the behavior in Wine, not try to get around >it. so, any good bugreport is also more than welcomed in order to have >it fixed I thought I had reported bugs in my first breath. Doesn't change my requirement to have my app run under 95, 98, Me, NT, 2K, XP and any reasonably recent release of Wine. Each OS as had it's own share of workarounds required as is common for a really large app. Anyway, I don't find it unreasonable to have to work around specific bugs in specific OS's. --Mike

Feb. 28, 2003