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

Re: Authors.c Won't Compile

by Hans Leidekker

On Friday 27 February 2004 13:07, Robert Shearman wrote: > $ echo $LANG > en_GB.UTF-8 > > $ echo $LC_ALL > > $ LC_ALL=C sed -e '1,2d' -e 's/$.*$/ \"\1\",/' ../../AUTHORS | grep Ove > "Ove K\x{FFFF}ven", > > $ sed -e '1,2d' -e 's/$.*$/ \"\1\",/' ../../AUTHORS | grep Ove > "Ove K",\x{FFFF}ven Right, my orignal patch to fix this did LANG=C before the sed. Alexandre changed this to LC_ALL=C recently, probably to get C sorting order as well. When I use your settings I can't reproduce what you get (I have sed 4.0.8 on Fedora Core 2 test 1). What does it say when you do this: $ LANG=C sed -e '1,2d' -e 's/$.*$/ \"\1\",/' ../../AUTHORS | grep Ove -Hans

Feb. 27, 2004

RE: Authors.c Won't Compile

by Robert Shearman

Hans Leidekker wrote: > On Friday 27 February 2004 03:42, Robert Shearman wrote: > > > I can't compile authors.c due to some encoding issue with sed. I can > > generate the authors.c file fine on the command line, but the same > > command in the Makefile won't generate compilable code due to it > > terminating the string constant before a UTF-8 character. > > That's strange, this issue should be fixed in CVS. What does it say > when you do this: This is with latest CVS, although I hadn't updated for a week so I don't know when the issue was introduced. > [hans(a)mirzam shell32]$ file authors.c > authors.c: ISO-8859 C program text > > How are your $LANG and $LC_ALL variables set? $ file authors.c authors.c: ISO-8859 C program text $ echo $LANG en_GB.UTF-8 $ echo $LC_ALL $ LC_ALL=C sed -e '1,2d' -e 's/$.*$/ \"\1\",/' ../../AUTHORS | grep Ove "Ove K\x{FFFF}ven", $ sed -e '1,2d' -e 's/$.*$/ \"\1\",/' ../../AUTHORS | grep Ove "Ove K",\x{FFFF}ven > -Hans >

Feb. 27, 2004

Re: Help needed to get the application work for native linuxeditors

by Shachar Shemesh

saravanan wrote: >Hi, > > Can you tell me where I can get the help on X APIs. I am very new to >Linux programming. >I feel that replacing windows GetFocus API & Postmessage API with that of >Linux APIs might work. > > Saravanan > > Man, I feel old in the face of such enthusiasm. Hi Saravanan, Please, the last thing I want is to pour cold water on your enthusiasm. However, I'm afraid the project you are contemplating on doing here is in the order of magnitude of Wine itself. You see, the thing about X windows is that they don't have an HWND, for the very simple reason that they are not Windows windows (not a generic name my %$&!@). As such, you will find that in order to do what you are trying to do, you will have to create a HWND representation for windows you don't control. It gets worse - X gets events, not messages. You will have to create message loops for each window you want to create a Win32 identity for, and then figure out for each individual message how to translate it into the X API space. This is not a trivial job to do, and so far as far as I know, Wine has not handled this aspect at all. It just didn't seem important enough to anyone. Wine is currently mostly handling the Windows->X translation, not the other way around. This means that Wine is currently figuring out how to make the Win32 constructs appear inside the X world. Making the X constructs appear in the Win32 world has never came up, as far as I know. That said, you can search some of the following sites for the docs you want. http://x.org, http://xfree86.org, http://freedesktop.org. Shachar -- Shachar Shemesh Lingnu Open Systems Consulting http://www.lingnu.com/

Feb. 27, 2004

Re: Help needed to get the application work for native linuxeditors

by Mike Hearn

On Fri, 27 Feb 2004 15:29:30 +0530, saravanan wrote: > Hi, > > Can you tell me where I can get the help on X APIs. I am very new to > Linux programming. > I feel that replacing windows GetFocus API & Postmessage API with that of > Linux APIs might work. The man pages are a good start, here is the Xlib manual: http://www.tronche.com/gui/x/xlib/ thanks -mike

Feb. 27, 2004

Re: RPC Update Patch

by Mike Hearn

On Thu, 26 Feb 2004 23:16:23 -0600, Gregory M. Turner wrote: > They are actually pretty well-documented on MSDN: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rpc/rpc/rp… > > Looks like a lot of work, Robert; thanks for your efforts. Hmm, interesting. I wonder why this doesn't show up when I google for "ndr format strings". thanks -mike

Feb. 27, 2004

Re: Help needed to get the application work for native linuxeditors

by saravanan

Hi, Can you tell me where I can get the help on X APIs. I am very new to Linux programming. I feel that replacing windows GetFocus API & Postmessage API with that of Linux APIs might work. Saravanan ----- Original Message ----- From: Robert Shearman <R.J.Shearman(a)warwick.ac.uk> To: <saravananv(a)erdcitvm.org> Cc: <wine-devel(a)winehq.org> Sent: Thursday, February 26, 2004 8:23 PM Subject: Re: Help needed to get the application work for native linuxeditors > Hi, > > I can't really give you any advice on using the X API, > but I can tell you that the Win32 and X API are > completely different. If you want to support native X > apps then you will have to either completely rewrite > your Windows program in Linux or you will have to > compile the Linux editor as a Winelib app and run it > under Wine. > I suggest you find a good book on the X API and/or > contact the appropriate mailing lists to find out > which functions you should use. > > Rob > > >>> "saravanan" <saravananv(a)erdcitvm.org> 02/26/04 11:17 AM >>> > Hai friends, > > I successfully ran a script manager(keyboard Manager/driver) developed for windows (using VC++) in Linux using wine. Its working in the wordpad application called using wine.I want to make it work in Linux editors. > > The technical details about the working of the keyboard driver is as follows. > 1) The keyboard driver is a keyboard hooker program. The keyboard driver will trap all the keystrokes from the keyboard and convert the Ascii value to the appropriate native language Character code. > 2) First we have to get the handle of the window/control where the cursor is currently located, for that the GetFocus API is used. > 3) Virtual-key code of the key that generated the keystroke message is converted to appropriate another code for making the keyboard Inscript or phonetic and send using Postmessage API. > > I have some doubts. Do these APIs written for windows work in linux. In linux , How could i get the handle of the window where the cursor is currently located. What are the changes that i should make in the source code to make it work for linux editors. > Looking for your suggessions. Thanks in advance . > > Saravanan > > > > > ______________________________________ > Scanned and protected by Email scanner > > ______________________________________ Scanned and protected by Email scanner

Feb. 27, 2004

Re: Authors.c Won't Compile

by Hans Leidekker

On Friday 27 February 2004 03:42, Robert Shearman wrote: > I can't compile authors.c due to some encoding issue with sed. I can > generate the authors.c file fine on the command line, but the same > command in the Makefile won't generate compilable code due to it > terminating the string constant before a UTF-8 character. That's strange, this issue should be fixed in CVS. What does it say when you do this: [hans(a)mirzam shell32]$ file authors.c authors.c: ISO-8859 C program text How are your $LANG and $LC_ALL variables set? -Hans

Feb. 27, 2004

Re: RPC Update Patch

by Gregory M. Turner

On Thursday 26 February 2004 03:25 pm, Mike Hearn wrote: > Wow, fantastic! One thing, could you write up some basic info on > the structure of format strings? I'm just a bit concerned that one > day we'll have to rewrite the typelib marshaller to use this interpreter > and not know how, as this stuff is pretty opaque :) They are actually pretty well-documented on MSDN: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rpc/rpc/rp… Looks like a lot of work, Robert; thanks for your efforts. -- gmt "We lay it down as a fundamental, that laws, to be just, must give a reciprocation of right; that, without this, they are mere arbitrary rules of conduct, founded in force, and not in conscience." --Thomas Jefferson

Feb. 27, 2004

catching first chance exception question

by Robert Reif

I'm looking at how windows deals with invalid parameters in some of the winmm functions and it raises some questions. Sometimes they will check the parameters and return an error code and sometimes they will let a bad parameter cause a first-chance exception and catch it and return an error code. Is it ok to do a simple NULL pointer check and return an error rather than letting it cause an exception and catching it? If not, what's the best way to catch the exception and return the proper error code?

Feb. 27, 2004

Re: Reset Resolution on Crash (resend)

by Alexandre Julliard

Robert Shearman <R.J.Shearman(a)warwick.ac.uk> writes: > No comment to this patch last time it was sent. Is it better implemented > some other way? I don't think user32 should be messing with the exception filter. Maybe we could make winedbg do this? -- Alexandre Julliard julliard(a)winehq.org

Feb. 27, 2004