Re: RPC Update Patch
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/rpc_ndr_format_strings.asp 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". It does if you include the quotes... - Dan -- US citizens: if you're considering voting for Bush, look at these first: http://www.misleader.org/ http://www.cbc.ca/news/background/arar/ http://www.house.gov/reform/min/politicsandscience/
Re: implement fixme in CreateAcceleratorTable
On Sat, 2004-02-28 at 09:46, Dmitry Timoshkov wrote:
> "Pabs" <[EMAIL PROTECTED]> wrote:
>
> > ChangeLog
> >
> > Added some checks to CreateAcceleratorTableA/W (removes fixmes)
>
> IMO it's better to use
>
> if (!MapVirtualKeyW(lpaccel[i].key, 0))
> {
> WARN("Invalid VK\n");
> SetLastError(ERROR_INVALID_PARAMETER);
> return NULL;
> }
>
> for a check whether VK is a valid one.
This being the first time I have looked at the wine source code I didn't
think of that. I agree, this is a better idea. It would be interesting
to know how windows does it though.
--
Bye,
Pabs
Re: implement fixme in CreateAcceleratorTable
"Pabs" <[EMAIL PROTECTED]> wrote:
> ChangeLog
>
> Added some checks to CreateAcceleratorTableA/W (removes fixmes)
IMO it's better to use
if (!MapVirtualKeyW(lpaccel[i].key, 0))
{
WARN("Invalid VK\n");
SetLastError(ERROR_INVALID_PARAMETER);
return NULL;
}
for a check whether VK is a valid one.
--
Dmitry.
RE: Authors.c Won't Compile
Hans Leidekker wrote:
> On Friday 27 February 2004 14:21, Robert Shearman wrote:
>
> > > > $ LC_ALL=C sed -e '1,2d' -e 's/\(.*\)/ \"\1\",/' ../../AUTHORS
> > > | grep Ove
> > > > "Ove K\x{}ven",
>
> I'm lost as to where the \x{} comes from (is it grep?), but as
> such this looks like a valid C string. So it should compile if this
> is the literal source we're seeing. Or could it be that your terminal
> inserts the \x{}? Anyone else have a clue?
It comes from pasting the lines into my mail program.
> To exclude grep, are there any \x{}s when you do:
>
> $ cat authors.c
No, there are just blanks spaces where the characters should be.
Rob
Re: catching first chance exception question
Robert Reif a écrit : 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? the normal rule of thumbs is: - don't use exception unless you have to (ie, we have a clear case of an application requiring that feature) => first implementation should be only based on NULL pointer testing - if you need to go further, then setting an exception handler is the thing to do (using IsBadReadPtr or IsBadWritePtr is a not 100% safe, especially in multi-threaded environments) A+
Sibelius 2
Sibelius is an app for scoring music. Sibelius 1 runs fine with wine. Sibelius 2 crashes on startup. When it crashes there is no useful message, only "Unhandled exception". Using winedbg I have found that Sibelius appears to be following a NULL pointer. I haven't yet managed to track down where it's getting the bad pointer from... any suggestions would be appreciated. I've got some time and energy to try to make this work, but first... Has anyone else worked or is some else currently working on this? What did you find? How far did you get? -- Andrew L. Bereson [EMAIL PROTECTED] (800)307-5754
Re: build: avoid Unix file on MinGW
On Fri, Feb 27, 2004 at 09:19:08AM -0500, Dimitrie O. Paun wrote:
> BTW, why do we need the {GLU32,GLUT32,OPENGL}FILES cases?
> Should those just be listed under X files? And shouldn't
> we just build those, and dload() the Unix libs at run time?
We need these special cases as an user can have X installed but not GLU /
GLUT or OpenGL.
And as to why we cannot dload the Unix lib at run time, it would be a bit
like 'why do we not build the X11DRV library all the time and dlsym all the
X11 symbols'.
Basically, if you do not have OpenGL installed, there is no way you will be
able to get Wine's OpenGL library to run. So there is no point to offer some
special 'dlopen' magic to be able to load it on these boxes.
Lionel
--
Lionel Ulmer - http://www.bbrox.org/
Re: winemaker: use winegcc
On Fri, 27 Feb 2004, Francois Gouget wrote: > Does winegcc systematically link applications and dlls to advapi32, > comdlg32, etc? How does one do if one does not want to link with gdi32 > for instance? Yes, it does, those are the defaults for MinGW. More specifically, all apps are linked by default against these DLLs: advapi32 user32 kernel32 additionally, GUI apps are also linked against: shell32 comdlg32 gdi32 If you don't want these defaults, you specify the -nodefaultlibs on the command line. -- Dimi.
Re: Authors.c Won't Compile
On Friday 27 February 2004 14:21, Robert Shearman wrote:
> > > $ LC_ALL=C sed -e '1,2d' -e 's/\(.*\)/ \"\1\",/' ../../AUTHORS
> > | grep Ove
> > > "Ove K\x{}ven",
I'm lost as to where the \x{} comes from (is it grep?), but as
such this looks like a valid C string. So it should compile if this
is the literal source we're seeing. Or could it be that your terminal
inserts the \x{}? Anyone else have a clue?
To exclude grep, are there any \x{}s when you do:
$ cat authors.c
-Hans
Re: winemaker: use winegcc
On Fri, 27 Feb 2004, Dimitrie O. Paun wrote: [...] > @@ -801,7 +753,7 @@ > $basename=~ s/\.(dll|exe)$//i; > # This is the default link list of Visual Studio, except odbccp32 > # which we don't have in Wine. > -my @std_imports=qw(advapi32 comdlg32 gdi32 kernel32 odbc32 ole32 oleaut32 > shell32 user32 winspool); > +my @std_imports=qw(odbc32 ole32 oleaut32 winspool); > my @std_libraries=qw(uuid); Does winegcc systematically link applications and dlls to advapi32, comdlg32, etc? How does one do if one does not want to link with gdi32 for instance? -- Francois Gouget [EMAIL PROTECTED]http://fgouget.free.fr/ May your Tongue stick to the Roof of your Mouth with the Force of a Thousand Caramels.
RE: Authors.c Won't Compile
Hans Leidekker wrote:
> 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{}ven",
> >
> > $ sed -e '1,2d' -e 's/\(.*\)/ \"\1\",/' ../../AUTHORS | grep Ove
> > "Ove K",\x{}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
"Ove K\x{}ven",
Rob
>
> -Hans
>
Re: Authors.c Won't Compile
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{}ven",
>
> $ sed -e '1,2d' -e 's/\(.*\)/ \"\1\",/' ../../AUTHORS | grep Ove
> "Ove K",\x{}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
RE: Authors.c Won't Compile
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.
> [EMAIL PROTECTED] 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{}ven",
$ sed -e '1,2d' -e 's/\(.*\)/ \"\1\",/' ../../AUTHORS | grep Ove
"Ove K",\x{}ven
> -Hans
>
Re: Authors.c Won't Compile
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: [EMAIL PROTECTED] shell32]$ file authors.c authors.c: ISO-8859 C program text How are your $LANG and $LC_ALL variables set? -Hans
Re: Help needed to get the application work for native linuxeditors
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/
Re: Help needed to get the application work for native linuxeditors
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
Re: RPC Update Patch
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/rpc_ndr_format_strings.asp > > 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
Re: Help needed to get the application work for native linuxeditors
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 <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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
