<DIV>Hello Mike,</DIV>
<DIV> </DIV>
<DIV>So as my understanding, even recompile the original windows codes using WINELIB will not work, am I correct? </DIV>
<DIV> </DIV>
<DIV>Since finding window info under cursor is only one of the functionality in this application,</DIV>
<DIV>it will be a huge work to rewrite all the codes for X window. Is there any Avenue to port such a windows application to Linux? Using Visual Mainwin or Win/U is better choices?</DIV>
<DIV>or any other comments on it?</DIV>
<DIV> </DIV>
<DIV>Thanks a lot!</DIV>
<DIV> </DIV>
<DIV>-Lechun<BR><BR><B><I>Mike Hearn <mike@theoretic.com></I></B> wrote:</DIV>
<DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid; WIDTH: 100%">Programs run under emulation are only aware of other Wine programs. If<BR>you want to write an app like that, you'd need to rewrite it for Linux.<BR><BR>BTW, you might want to talk to a guy named Bill Haneman (i think that's<BR>the spelling). He does Gnome accessibility, and i think they have an app<BR>that can read info about stuff under the mouse cursor.<BR><BR>On Thu, 2003-07-10 at 20:41, dd jj wrote:<BR>> Thank you for response. The following is my further question:<BR>> <BR>> Here is my case:<BR>> <BR>> Now I am trying to run our own developed application under wine, the<BR>> original function of this app is working as a background daemon<BR>> without GUI who is trying to figure out some window information under<BR>> the current cursor, such as the window title, class name using<BR>> GetWindowTitle, GetClassName ... WIN32 API calls. <BR>> <BR>>
When I run this under WINE, it can't "see" any other Local X<BR>> application windows such as Xterm, Xclock... which don't run under<BR>> WINE.<BR>> <BR>> <BR>> I am wondering whether I can recompile the codes to generate a lcoal X<BR>> application using winelib to solve this problem, or I must write X11<BR>> based codes?<BR>> <BR>> Thanks a lot!<BR>> <BR>> -Lechun<BR>> <BR>> Mike Hearn <MIKE@THEORETIC.COM>wrote:<BR>> > fixme:class:get_class_ptr reading from class of other<BR>> process window<BR>> > 0x2002a<BR>> > err:win:WIN_FindWndPtr window 0x2003a belongs to other<BR>> process<BR>> <BR>> Well these two are known problems. I think it's something<BR>> Alexandre will<BR>> be working on at some point, inter-process window<BR>> communication isn't<BR>> really implemented well in Wine at present.<BR>> <BR>> > Also I found other errors when I launch my window appication<BR>> under<BR>> >
wine:<BR>> > <BR>> > err:module:import_dll No implementation for<BR>> USER32.dll.GetTitleBarInfo<BR>> > imported from C:\ping\exe\ping.exe, setting to 0xdeadbeef<BR>> > err:module:import_dll No implementation for<BR>> USER32.dll.GetMenuBarInfo<BR>> > imported from C:\ping\exe\ping.exe, setting to 0xdeadbeef<BR>> > <BR>> <BR>> Unless the program actually uses them, this isn't a problem.<BR>> If it does,<BR>> the app will crash, at which point we'd need to write those<BR>> functions or<BR>> stub them out.<BR>> <BR>> thanks -mike<BR>> <BR>> <BR>> ______________________________________________________________________<BR>> Do you Yahoo!?<BR>> SBC Yahoo! DSL - Now only $29.95 per month!<BR></BLOCKQUOTE></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!