November 2007 - Wine-Devel - list.winehq.org

Re: [Bug 10266] Numpad keyboard handling is strange, Del key produces two events

by Peter Åstrand

Perhaps we need to gather more input from other developers: > http://bugs.winehq.org/show_bug.cgi?id=10266 > > --- Comment #4 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2007-11-01 08:32:46 --- > > But in that case, you will find all of your X11 applications on your desktop, > > including Firefox etc, confusing as well? > > Yes, and this behaviour is very annoying and not consistent IMO. Let's break down this statement into two: 1) "Not consistent" It might be interesting to compare with CapsLock. Shift can cancel CapsLock, but also substitute it. This is true on both Windows and Linux. Additionally, on Linux, NumLock works the same, ie Shift works in both directions. On Windows, however, Shift can only cancel NumLock, not substitute it. Regardless of whether users actually finds this useful or not, I think it's hard to argue for that this is "logical" or "consistent". 2) "Annoying" Can it be that you have a Windows background and are therefore used to the Windows behaviour? I haven't actually asked any users yet, but my general opinion is that all applications on the same desktop should behave the same, if possible. We are decorating the Windows windows with the normal window manager decorations etc so I think it's reasonable that the keyboard should behave according to the native system model. Another thing to keep in mind is that most users actually never use the numpad keys in conjunction with Shift. I know this from several years of experience of keyboard hacking - there have been plenty of bugs in many softwares in this area but very few actual bug reports. > Besides, I just tested with Wine's notepad and don't see the problem you > are reporting. Which keyboard layout are you using? On my system, Wine selects the Swedish keyboard layout. Regards, --- Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.se Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00 ThinLinc User Group 2007 Höstkonferens --- 15-16 november, Linköping. Program och anmälan: http://www.thinlincusergroup.se/aktiviteter

Nov. 1, 2007

Re: setupapi: Add stub for SetupInstallServicesFromInfSectionW

by Frank Richter

On 01.11.2007 14:26, Robert Shearman wrote: > There's no need to move the entry for > SetupInstallServicesFromInfSectionW. The list was sorted alphabetically, > but now it isn't. Unless you ignore the A/W suffix. One could argue that this is more intuitive as you could locate an entry in the list by searching for the undecorated name and then look for the one with the appropriate suffix, which is at most one line away. If you sort strictly alphabetically, A/W variants may be a couple of lines away (e.g. FooA/FooExA/FooExW/FooW) which could make finding the right variant slightly counterintuitive. -f.r.

Nov. 1, 2007

Re: Bug in dlls/oleaut32/tests/vartype.c?

by Gerald Pfeifer

[ Updated patch at the end, Alexandre. ] On Mon, 29 Oct 2007, Alex Villacís Lasso wrote: > Sorry to object, but which version of exactly which compiler optimizes > away the negative sign? You're right, I misread this, sorry. My original patch wasn't wrong, but the explanation was, and there seems in fact a better patch. > Consider the following program: That's a very fair test, and I enhanced it as follows: #include <stdio.h> #include <stdlib.h> void print(const float f) { union x { float f; unsigned char b[4]; } u; u.f = f; printf("Value as float is %f\n", u.f); printf("as bytes %02x %02x %02x %02x\n\n",u.b[0],u.b[1],u.b[2],u.b[3]); } int main() { print(-1e-400); print(-0.0); } Both GCC 3.4 and GCC 4.2 snapshot give 00 00 00 80 in both cases. (All the original warning referred to actually did was to indicate that the compiler actually made this change automatically; that was added with GCC 4.3 it seems.) Gerald ChangeLog: Use -0.0 directly in test_VarBstrFromR4(). Index: vartype.c =================================================================== RCS file: /home/wine/wine/dlls/oleaut32/tests/vartype.c,v retrieving revision 1.51 diff -u -3 -p -r1.51 vartype.c --- vartype.c 20 Aug 2007 12:43:49 -0000 1.51 +++ vartype.c 1 Nov 2007 13:42:48 -0000 @@ -4747,7 +4747,7 @@ static void test_VarBstrFromR4(void) } } - f = -1e-400; /* deliberately cause underflow */ + f = -0.0; hres = pVarBstrFromR4(f, lcid, 0, &bstr); ok(hres == S_OK, "got hres 0x%08x\n", hres); if (bstr)

Nov. 1, 2007

Re: setupapi: Add stub for SetupInstallServicesFromInfSectionW

by Robert Shearman

Chris Robinson wrote: > @ stdcall SetupInstallFromInfSectionA(long long str long long str long ptr ptr long ptr) > @ stdcall SetupInstallFromInfSectionW(long long wstr long long wstr long ptr ptr long ptr) > @ stdcall SetupInstallServicesFromInfSectionA(long str long) > +@ stdcall SetupInstallServicesFromInfSectionW(long wstr long) > @ stub SetupInstallServicesFromInfSectionExA > @ stub SetupInstallServicesFromInfSectionExW > -@ stub SetupInstallServicesFromInfSectionW > @ stdcall SetupIterateCabinetA(str long ptr ptr) > @ stdcall SetupIterateCabinetW(wstr long ptr ptr) > @ stub SetupLogErrorA > There's no need to move the entry for SetupInstallServicesFromInfSectionW. The list was sorted alphabetically, but now it isn't. -- Rob Shearman

Nov. 1, 2007

Re: New DLL, Server and Service Documentation

by Stefan Dösinger

Am Donnerstag, 1. November 2007 08:00:36 schrieb Roy Shea: > Howdy All, > > This autumn I began learning both Wine and COM. A > combination of limited documentation and trouble finding the > right example code for my task at hand made this a difficult > process. In an attempt to help other new Wine and COM > developers I wrote a tutorial on COM development the Wine > way. This tutorial describes: > This should propably be linked from the wiki. Which would be the right place for that?

Nov. 1, 2007

Re: wined3d: Enable clip planes with GLSL shader backend

by Stefan Dösinger

Am Donnerstag, 1. November 2007 02:01:14 schrieb Ivan Gyurdiev: > > + if (use_vs(stateblock->wineD3DDevice) && > > stateblock->wineD3DDevice->vs_selected_mode == SHADER_ARB) > > GLSL specific logic should go in glsl_shader.c. > > Please try to get away from writing code in terms of flags and if > statements - use the OOP model. > Backend-specific logic should be removed from pixelshader and > vertexshader too... We've had this discussion over and over, but I'm not too fond of pressing everything into an OOP model by force. I agree it is useful in general, and I'm currently working on making the surface type organisation more OOPish. However, in this special case the state management collides with shader differences. Adding a shader model callback for every of those cases doesn't make the code more readable IMHO. I agree that the backend specific code in GenerateShader in vertexshader.c / pixelshader.c should be moved to arb / glsl backends. Then we'd get vertex and pixel shader specifics into arb / glsl, but we can't avoid those anyway.

Nov. 1, 2007

Re: Wine Gecko packaging

by Boaz Harrosh

----- Original Message ----- *From:* Jacek Caban <jacek(a)codeweavers.com> *To:* Dmitry Timoshkov <dmitry(a)codeweavers.com> *CC:* wine-devel(a)winehq.org *Sent:* Wed, Oct 31 2007 at 21:20 +0200 *Subject:* Wine Gecko packaging > Hi Dmitry, > > Dmitry Timoshkov wrote: > >> http://source.winehq.org/winegecko.php still points to an old Gecko >> package >> (0.0.1). Please update it. >> >> > > We can't change it due to compatibility with older Wine versions. We > encode Gecko version in URL instead, so > http://source.winehq.org/winegecko.php?v=0.1.0 will do what you want. > > Jacek > Do you have a magic param to download the latest one available? something like: winegecko.php?v=latest Thanks Boaz

Nov. 1, 2007

New DLL, Server and Service Documentation

by Roy Shea

Howdy All, This autumn I began learning both Wine and COM. A combination of limited documentation and trouble finding the right example code for my task at hand made this a difficult process. In an attempt to help other new Wine and COM developers I wrote a tutorial on COM development the Wine way. This tutorial describes: - A simple DLL providing a in-process COM object - A simple server providing a local COM object - A simple service that publishes a COM object and the corresponding proxy / stub required to use the service with instructions on Wine integration and, for Windows users or testers building for Windows, basic instructions on building and running these same applications in Windows. The tutorial is available at: http://ambleramble.org/wine/ I hope other developers enjoy this documentation. If you see mistakes, either minor typos or conceptual problems, please drop me an email and I'll clean up the docs. Peace, -Roy

Nov. 1, 2007

Re: wined3d: Enable clip planes with GLSL shader backend

by Ivan Gyurdiev

> + if (use_vs(stateblock->wineD3DDevice) && stateblock->wineD3DDevice->vs_selected_mode == SHADER_ARB) GLSL specific logic should go in glsl_shader.c. Please try to get away from writing code in terms of flags and if statements - use the OOP model. Backend-specific logic should be removed from pixelshader and vertexshader too...

Nov. 1, 2007