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

Re: tests for GetPrinterDriverDirectoryA

by Francois Gouget

On Mon, 13 Jan 2003, Stefan Leichter wrote: > Am Montag 13 Januar 2003 18:42 schrieben Sie: > > On Sun, 12 Jan 2003, Stefan Leichter wrote: > > > Am Sonntag 12 Januar 2003 02:43 schrieben Sie: [...] > > > > However it fails on Wine: > > > > info.c:25: Test failed: pcbNeeded set to 18 instead of 19 > > > > info.c:30: Test failed: pcbNeeded set to 18 instead of 19 > > > > info.c:34: Test failed: expected result == 0, got 18 > > > > info.c:35: Test failed: pcbNeeded set to 18 instead of 19 > > > > info.c:48: Test failed: expected result != 0, got 0 > > > > info.c:71: Test failed: expected result != 0, got 0 > > after this patch wine will fix the errors listed above Yep, that works. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Cahn's Axiom: When all else fails, read the instructions.

Jan. 14, 2003

Re: new to wine and would like to be actively involved.

by Dimitrie O. Paun

On January 13, 2003 02:09 pm, Shravan Sadasivan wrote: > I have strong developement > skills in C and Perl.. and have worked with converting C source code in > informix. Awaiting more from your side.. Hi Shravan, There are plenty of things to do, you will find some of them on these pages: http://www.dssd.ca/wine/ Check out the Fun/Janitorial/Winelib/0.9 TODO/Contrib pages. Welcome to the team! -- Dimi. P.S. I hope you know we can not accept contributions unless they have been conceived while under the influence of at _least_ 3-5 glasses of (good) wine... :)

Jan. 13, 2003

Re: new to wine and would like to be actively involved.

by Tom Wickline

Shravan Sadasivan wrote: > Hi, > I am new to the wine developement community and would like to actively > get involved in the activities in this community. Could anyone please > educate me on how i can go about doing that?.. I have strong developement > skills in C and Perl.. and have worked with converting C source code in > informix. Awaiting more from your side.. > > TIA > > Warm Regards, > Shravan Here is a starter guide :) I'm sure there is alot of other goodies to work on as well. See : http://www.dssd.ca/wine/Wine-Contrib-0.7.html hope this helps Tom

Jan. 13, 2003

Re: Help wanted: Implementing Wine dlls that need access to X11 commands.

by Robert North

Alexandre Julliard julliard-at-winehq.com |Wine Mailing Lists| wrote: >Robert North <7ownq0k402(a)sneakemail.com> writes: > > > >> The one difference will be that wintab will create it's own X11 >>Display objects. >> It will interrogate a gdi's X11 Display object to ensure it talks >>to the same screen. >> >> The wintab code will also require multiple message queues. >> To implement this I intend to use one display object per queue. >> (Much as wine uses one display object per thread) >> >> > >Hmmm... I have a feeling you would be better off using the existing >message queues and display connections. Could you give a bit more >details on how you have to implement it, or send us pointers to the >relevant documentation? > > > That's what I thought, and I have proof of concept patch that hack the x11drv code to insert & read XInput events from wine's X11 event loop. Unfortunately this doesn't fit well with the way wintab works. So, here's an explanation, why I've made these decisions. It's far longer than I'd wish, but the issues involved in the design are complex. So here goes...... ***Quick recap of what wintab does*** The wintab dll will takes messages from a graphics tablet, and provides them to the user. But isn't that what a mouse does? A mouse provides information on the X & Y screen coords, and buttons pressed. A tablet provides all the above, plus extra axes defining the tilt of a pen, the pen's pressure, rotation of a mouse, (and possibly more). All this can be provided at resoloutions much higher than screen resoloution. ***The XInput side of the implementation *** The official way to get tablet data for an X display is to use the XInput extension. The XInput extension defines a specialised set of event classes to represent tablet data, which enter the normal X11 message queue. These messages are initially disabled. XInput provides a function to enable them for a given display and window. OK, So far it looks as if the XInput messages could be injected into the wintab messaging system. But note that this would reqire some patching to the x11drv dll to do the following 1. decode the messages. 2. enable the messages for a given window and display. But I'm assuming that changing the x11drv code could cause severe regressions to wine. I'm therefore assuming that it's good manners to avoid fiddling with x11drv code till the wintab driver implementation is known to be adequate. *** The wintab side of the implementation *** To access tablet, a "tablet context" is created that maps a window to a particular tablet device. For each tablet context the application is given a separate tablet message queue, which provides 2 ways to access the tablet message queue. a. A set of functions that get or peek, or otherwise interrogate the message queue for queue size, message at index etc. b. Posting messages into the windows(wine) message queue. To complicate matters, it appears that it's possible to use both methods in the same program. At present, I will only implement method a. as this is the one used by Painter5 and Photoshop6. Now, as it turns out, the methods to interrogate a wintab message queue are extremely similar to those to interrogate an X11 message queue. So that's +1 to giving wintab it's own X11 message queue. (Or possibly even one X11 msg queue per tablet context!). A simple X11<->wintab mapping can be implemented, and no additional queue data structs are needed in the wintab implementation. As the wintab dll implements it's own message queue, an implementation using the wine message queue would give a number of problems: 1. All wintab messages would have to be hidden from the application's windows(wine) message queue. Could be done with one specific thread, or threads for wintab. This becomes similar, but more complicated to the X11 message queue implementation. 2. Filtering methods would have to be implemented to only access the messages appropriate to the reqired tablet context. X11 provides all the filtering necessary. While windows provides enough filtering for ranges of messages. But this would mean 3 message mappings X11->windows(wine)->wintab. 3. All the queue management functions, and any necessary data structs to manage the queue will have to be implemented specifically in wintab, as the windows queue doesn't give much control over the message queue, and what's more, may need to copy data into a wintab specific message queue before the application can access it. I think after all that complexity, that's +4 or more to X11 message queue implementation, and for wintab at least, avoid the wine message queue. Well, that's the end of my whistle stop tour of the issues I've been cosidering with this part of the design. I've omitted any reference to function names, to keep this document as breif and readable as possible. If you wish, I can annotate it with the relevant function names. Please feel free to comment on anything. And finally, Some references: For the wintab spec see the following location: http://www.pointing.com/FTP.HTM For XInput see ftp://ftp.x.org/pub/R6.4/xc/doc/hardcopy/Xi/lib.PS.gz (Much of the doccumentation will probably be bundled with your xfree86 implementation too) Well, that's all for now, -Rob.

Jan. 13, 2003

[D3D status] Page update...

by Lionel Ulmer

Hi all, I updated the D3D status page (http://www.bbrox.org/d3d_status.html) with some new screenshots and some new demos. Nothing revolutionnary though :-) Thanks to Christian for the 3D Mark 2000 paragraph. Lionel -- Lionel Ulmer - http://www.bbrox.org/

Jan. 13, 2003

Re: Help with /?? stuff

by Alberto Massari

At 20.06 13/01/2003 +0200, Shachar Shemesh wrote: >Sylvain Petreolle wrote: > >>Do you know exactly _when_ it must be called ? Before or after RunOnce >>? >> >Even if noone here knows, it shouldn't be too difficult to find out. This web pages (http://www.greatis.com/regrun3startuporder.htm ) lists RunOnceEx after Run Alberto >>>In my opinion, the test should be done on the presence of the "|" >>>character; if the character is present, the file name should be >>>considered to be a DLL (regardless of the extension: e.g. >>> >>Shouldn't we check the type of the binary ? >> >Again, good points. When the time comes I'll check what the windows >version does. If someone thinks they'll have the time for it before that, >and they don't know how to test that, contact me. > > Shachar > >

Jan. 13, 2003

Re: what does __leave do?

by Greg Turner

On Monday 13 January 2003 01:07 pm, Francois Gouget wrote: > On Mon, 13 Jan 2003, Greg Turner wrote: > > Could someone run the following code under a microsoft compiler for > > me, and let me know the result? > > > > main() { > > int x = 0; > > __try { > > x = 1; > > __leave; > > x = 3; > > > } __finally { > > x = 2; > > } > > printf("x was %d\n", x); > > } > > I modified it as shown above and it prints: > x was 2 > > So '__leave' is like a 'break' but for exception blocks. cool, quick turnaround on that one. thanks. -- gmt "If everyone is thinking alike then somebody isn't thinking." --George S. Patton

Jan. 13, 2003

new to wine and would like to be actively involved.

by Shravan Sadasivan

Hi, I am new to the wine developement community and would like to actively get involved in the activities in this community. Could anyone please educate me on how i can go about doing that?.. I have strong developement skills in C and Perl.. and have worked with converting C source code in informix. Awaiting more from your side.. TIA Warm Regards, Shravan ----- Original Message ----- From: "Robert Shearman" <R.J.Shearman(a)warwick.ac.uk> To: "Jürgen Schmied" <j.schmied(a)t-online.de>; <wine-devel(a)winehq.com> Sent: Sunday, January 12, 2003 10:36 PM Subject: Bug Fix With Delay load function in Shell32 (version2) > Here is the updated patch: > > > -----Original Message----- > > From: Jürgen Schmied [mailto:j.schmied(a)t-online.de] > > Sent: 12 January 2003 13:45 > > To: Robert Shearman; wine-devel(a)winehq.com > > Subject: Re: Bug Fix With Delay load function in Shell32 > > > > ChangeLog: > > > - Set up all delay load functions in GetShellOle() function to avoid > > > GetShellOle assuming that they were all loaded when they weren't > > > This isn't the best solution since GetShellOle() initializes the > > ole subsystem by calling > > OleInitialize(). This is not nessesary for _CoCreateInstance(). > > ChangeLog: > - Seperate the HINSTANCEs used by GetShellOle() and other delay load > functions >

Jan. 13, 2003

Re: what does __leave do?

by Francois Gouget

On Mon, 13 Jan 2003, Greg Turner wrote: > > Could someone run the following code under a microsoft compiler for me, > and let me know the result? > > main() { > int x = 0; > __try { > x = 1; > __leave; x = 3; > } __finally { > x = 2; > } > printf("x was %d\n", x); > } I modified it as shown above and it prints: x was 2 So '__leave' is like a 'break' but for exception blocks. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Broadcast message : fin du monde dans cinq minutes, repentez vous !

Jan. 13, 2003

Re: Help wanted: Implementing Wine dlls that need access to X11 commands.

by Alexandre Julliard

Robert North <7ownq0k402(a)sneakemail.com> writes: > The one difference will be that wintab will create it's own X11 > Display objects. > It will interrogate a gdi's X11 Display object to ensure it talks > to the same screen. > > The wintab code will also require multiple message queues. > To implement this I intend to use one display object per queue. > (Much as wine uses one display object per thread) Hmmm... I have a feeling you would be better off using the existing message queues and display connections. Could you give a bit more details on how you have to implement it, or send us pointers to the relevant documentation? -- Alexandre Julliard julliard(a)winehq.com

Jan. 13, 2003