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

Re: Stub for GetRawInputDeviceList
by L. Rahyen Jan. 8, 2007

Jan. 8, 2007

Monday January 8 2007 14:35、Michał Majchrowicz さんは書きました: (from the attached file) > A modification of patch found on wine mailing list It checks whether Also, for more information you can mention my name if you wish as initial author of this patch. I know that my patch was silently rejected long time ago - I didn't asked why because I was too busy for some time and... my little patch was simply lost because of this (I wasn't very active because my patch is very small and simple). But some time ago I have received a message from unofficial wine-wiki that it "has a quote based upon your October mailing list post" (actually the patch).

1 1

Re: Stub for GetRawInputDeviceList
by Dmitry Timoshkov Jan. 8, 2007

Jan. 8, 2007

Michal Majchrowicz mmajchrowicz(a)gmail.com wrote: > Everything is in the file :) > Regards. You are using tab == 4 spaces in your editor and that messes up formatting in 2 places in your patch. Also you should leave at least 1 empty line between function implementations like it is in the existing code. -- Dmitry.

1 0

Re: [15/20] WineD3D: Clean up drawprim a bit
by Ivan Gyurdiev Jan. 7, 2007

Jan. 7, 2007

Stefan Dösinger wrote: > Now that almost everything is gone from drawPrimitiveDrawStrided we don't need > a subfunction for calling drawStridedSlow/Fast any longer > I think while we're cleaning up things, all of software shaders should be removed. There's tons of code in drawprim and *shader.c, which is disabled, doesn't work, and isn't on the right track if you ask me. None of the changes to make the shader parser 3.0 compliant are used in the disabled paths. There's even an "Emulation" value in winecfg which just confuses the user, since it doesn't work. I did have a working implementation of software shaders some time ago, which broke things up into functions, and shared the tracing and parser with hardware shaders - but in the end it was too slow, and I abandoned it as the wrong approach too. Unless we generate asm on the fly for the shader or something like that, I don't think software shaders will be made to work soon.

2 2

Re: make_makefiles: Ignore backups of edited files.
by Patrik Stridvall Jan. 7, 2007

Jan. 7, 2007

On Sunday 07 January 2007 13:16, Robert Shearman wrote: > --- > tools/make_makefiles | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) Since the "*~" files are not generated by the build process this is perhaps not the right place to do it. Rather each developer should ignore such files by editing the .git/info/exclude file. Works for me! Somebody probably should update the website to make other developers aware of this.

1 0

Re: fix a typo
by Detlef Riekenberg Jan. 6, 2007

Jan. 6, 2007

On Sa, 2007-01-06 at 15:08 +0100, Jonathan Ernst wrote: > (I think) I decided to use "options", because native Ports have: COM*: Multiple options (BaudRate, DataBits, StopBits, Parity) LPT*: A single option (TransmissionRetryTimeout) FILE: No options Wine will add Redirection, what we can set in the registry at HKCU\Software\Wine\Printing\Spooler\<portname> -- By by ... Detlef

2 1

Re: [17/20] WineD3D: Vertex buffers can use the declaration from the device
by Ivan Gyurdiev Jan. 6, 2007

Jan. 6, 2007

Stefan Dösinger wrote: > Now that the decoded vertex declaration is put into the device with > baseVertexIndex = 0, vertex buffers can just memcpy it instead of decoding it > Here's an issue I see - isn't introduced by your patch, but I am just confused. In the vertex buffer code: if(device->stateBlock->vertexShader != NULL && wined3d_settings.vs_mode != VS_NONE &&((IWineD3DVertexShaderImpl *)device->stateBlock->vertexShader)->baseShader.function != NULL && GL_SUPPORT(ARB_VERTEX_PROGRAM)) { /* Case 1: Vertex Shader: No conversion */ TRACE("Vertex Shader, no conversion needed\n"); } else if(device->stateBlock->vertexDecl || device->stateBlock->vertexShader) { 1) No code should be looking at wined3d_settings.vs_mode. This is the user spec from winecfg, which is taken into account as one of the things that determines shader mode. There are a number of other things involved - use device->shader_mode instead. 2) GL_SUPPORT(ARB_VERTEX_PROGRAM) has already been accounted for when selecting the shader mode in the device 3) This if statement looks kind of like the "useVertexShaderFunction" variable in drawprim 4) Why is the "device->stateblock->vertexShader" case included in the else statement? You cannot use this function with a vertex shader - it would not work at all, as the strided data is formatted differently (same issue as the trace function discussed earlier).

1 0

Re: French translation of localspl
by Detlef Riekenberg Jan. 6, 2007

Jan. 6, 2007

On Sa, 2007-01-06 at 15:09 +0100, Jonathan Ernst wrote: > + IDS_NOTHINGTOCONFIG "Ce port n'a pas d'option Ã configurer" This is encoded as UFT-8 -- By by ... Detlef

1 0

appdb rating inflation
by Dan Kegel Jan. 6, 2007

Jan. 6, 2007

The appdb says "Only applications which install and run flawlessly on an out-of-the-box Wine installation make it to the Platinum list" But several platinum-rated apps seem to deserve a silver or bronze rating. For instance, Call to Duty, http://appdb.winehq.org/appview.php?iVersionId=3603 has all sorts of caveats: - Punkbuster enabled Multiplayer will not work - Sound out of sync. - Runs without crashes, but only if installed as root - requires whacky third-party Loki installer; real installer fails on cd change (http://bugs.winehq.org/show_bug.cgi?id=6594) - "with alsa, the sound lags ~ 1 second behind the game.... if i choose oss i got the 166 sound files missing error" And Diablo II, http://appdb.winehq.org/appview.php?iVersionId=49, also has lots of complaints / caveats / complicated howto's. Should we impose some standards on appdb ratings? - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

19 39

Re: listview: Remove over constrained restriction on creating subitems.
by Alexandre Julliard Jan. 6, 2007

Jan. 6, 2007

Duane Clark <fpga(a)pacbell.net> writes: > Changelog: Remove over constrained restriction on creating subitems. > Subject: [PATCH] Remove over constrained restriction on creating subitems. This breaks the tests: ../../../tools/runtest -q -P wine -M comctl32.dll -T ../../.. -p comctl32_test.exe.so listview.c && touch listview.ok listview.c:305: Test failed: ret 1 make[2]: *** [listview.ok] Error 1 -- Alexandre Julliard julliard(a)winehq.org

2 1

Problem with App Data screen
by Tony Lambregts Jan. 6, 2007

Jan. 6, 2007

There is a problem with submitting/administrating screen shots. I cannot see any screenshots that were submitted recently. This is probably a problem with filtering but I cannot be sure. http://appdb.winehq.org/admin/adminAppDataQueue.php http://appdb.winehq.org/admin/adminAppDataQueue.php?iId=5572 -- Tony Lambregts

2 1