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

RE: d3dx: A few last questions...
by tony.wasserka＠freenet.de Jan. 29, 2008

Jan. 29, 2008

> The function D3DXCheckVersion must not be forwarded from each d3dx9_xx file to the 36 because D3DX_SDK_VERSION changes for each file. Thanks for your comment, though I don't know if this is needed: Comment from the d3dx9core.h of the DX SDK: > /////////////////////////////////////////////////////////////////////////// > // D3DX_SDK_VERSION: > // ----------------- > // This identifier is passed to D3DXCheckVersion in order to ensure that an > // application was built against the correct header files and lib files. > // This number is incremented whenever a header (or other) change would > // require applications to be rebuilt. If the version doesn't match, > // D3DXCheckVersion will return FALSE. (The number itself has no meaning.) > /////////////////////////////////////////////////////////////////////////// So this function is only needed to ensure that no header file changed between the last build of an application. As this won't be the case in our wine implementation we can let all dlls use the same function. Also, the D3DX_SDK_VERSION is declared in d3dx9core.h, which means we can only have one definition of it at a time which even prevents us from caring about this function. By the way, I think this function is just a leftover from the times, when microsoft released updates of their D3DX library without renaming the dlls, were using a more actual dll could really lead to conflicts. Unbegrenzter Speicher, Top-Spamschutz, 120 SMS und eigene E-MailDomain inkl. http://office.freenet.de/dienste/emailoffice/produktuebersicht/power/mail/i…

1 0

shell32:shlfileop - interactive dialogs on Windows Vista
by Reece Dunn Jan. 29, 2008

Jan. 29, 2008

Hi, One of the new features of Windows Vista is to bring up dialogs whenever you are copying files, moving files, etc. to ask the user what behaviour they want (e.g. move and replace; don't move; move, but keep both files). This makes it more user friendly, but for the Wine tests, it means that: - on XP the shlfileop tests run and pass eithout any user interaction; - on Vista, the shlfileop tests bring up several of those dialog prompts. I haven't yet looked at the tests to see what they are doing, or at the MSDN documentation to see if this would break things (i.e. if the program selected copy & replace, but the user said don't copy). Does anyone have any ideas how to get these working without user interaction (or if that is at all possible)? - Reece

1 1

Wine Wiki spam users
by Vitaliy Margolen Jan. 29, 2008

Jan. 29, 2008

Does anyone have a power to block / remove those users that spam Wine wiki? It seems just 2-3 users keep creating more and more spam. Can't we just remove them and permanently block an IP range? Vitaliy.

2 1

user32: understanding the HiliteMenuItem failures (all platforms)... call for help
by Reece Dunn Jan. 29, 2008

Jan. 29, 2008

Hi, I am currently looking at the user32: menu (HiliteMenuItem) test failures: menu.c:1884: Test failed: HiliteMenuItem: Item 1 is not hilited menu.c:1891: Test failed: HiliteMenuItem: Item 3 is not hilited 1. These are failing consistently on all platforms (see http://test.winehq.org/data/200801161000 - you may need to search for HiliteMenuItem to find the failures!). 2. It appears (backed up with tests in the attached patch) that the API fails when the HWND parameter is NULL. 3. The tests are not comprehensive enough. The patch I have attached here is still a work in progress: 1. I have not tested it on Wine - it is likely that this will require todo_wine markers to make it run successfully. 2. The tests are still failing on Windows (both XP and Vista). Here is where I get stuck. According to the MDSN documentation (which is likely to be wrong) this appears to be correct. Does anyone know how to get HiliteMenuItem to work?! - Reece

1 1

Mail flood from the uncoordinated bugzilla cleanup
by Detlef Riekenberg Jan. 29, 2008

Jan. 29, 2008

Grrr. Please remember, that some Free Mail accounts have a limit in the numbers of Mails. The flood was to fast to stop Mail-delivery in wine-bugs. After i stopped Mail-delivery in wine-bugs, the sending queue was still so full, that my Mailbox got flood again and the bounce rate reached the limit and mailman disabled Mail-delivery for all wine groups. Not nice. -- By by ... Detlef

2 1

RE: [Patch for Bug 8551] MoveFileWithProgressW unconditional fails fordirectories with flag MOVEFILE_REPLACE_EXISTING
by Rolf Kalbermatter Jan. 29, 2008

Jan. 29, 2008

Jens Nestler wrote: > [Patch for Bug 8551] MoveFileWithProgressW > unconditional fails fordirectories with flag MOVEFILE_REPLACE_EXISTING > > http://bugs.winehq.org/show_bug.cgi?id=8551 > > Hello, > > please find attached the patch for the bug mentioned above. Hi Jens, Please diff your patches from the top level wine directory itself, as it is it's not helpful since the patch utility couldn't even know which of the many path.c files in the source tree needs to be patched, and the maintainer has a lot more things to do than to search where a patch could apply to. Rolf Kalbermatter

3 2

Wine BOF at Scale 6X in Los Angeles, Feb 8th
by Dan Kegel Jan. 29, 2008

Jan. 29, 2008

Anyone going to Scale in Los Angeles? I've scheduled a Wine BOF at 7pm on Friday, Feb 8th; see http://www.socallinuxexpo.org/scale6x/conference-info/social-events/birds-o… For those who don't know, SCALE is the brightest spot in Los Angeles' open source / free software scene. They've been going for eight years now. It's where I first saw a Samba developer running Windows in a VM and immediately going from Ethereal traces to implementing new code :-) See you there, I hope! (The BOF is a combined BOF with Zumastor, but don't worry, that just means I'll be talking with two people instead of one :-) - Dan

1 0

Re: [Patch for Bug 8551] MoveFileWithProgressW unconditional fails for directories with flag MOVEFILE_REPLACE_EXISTING
by James Hawkins Jan. 28, 2008

Jan. 28, 2008

On Jan 28, 2008 4:05 PM, Jens Nestler <nessi(a)nessi-online.de> wrote: > http://bugs.winehq.org/show_bug.cgi?id=8551 > > Hello, > > please find attached the patch for the bug mentioned above. > Please submit a test case for this change as well. -- James Hawkins

1 0

Re: [PATCH 1/1] winecoreaudio: Make sure Port_SendToMessageThread is non-NULL in CoreAudio_WaveRelease.
by Ken Thomases Jan. 28, 2008

Jan. 28, 2008

On Jan 28, 2008, at 8:06 AM, Misha Koshelev wrote: > I have started playing with wine on MacOS in VMWare. > wineprefixcreate page faults on my > MacOS "system" and I tracked it to Port_SendToMessageThread staying > NULL because of: > err:wave:CoreAudio_WaveInit AudioHardwareGetProperty: > CoreAudio_DefaultDevice.outputDeviceID == kAudioDeviceUnknown > Clearly wineprefixcreate shouldn't be page faulting under any > condition. It seems to me that the driver ought to just fail to load in this case. If you back out your patch and apply the attached patch, does that fix the page fault? -Ken

1 0

Re: start.exe: Handle the process title argument
by Detlef Riekenberg Jan. 28, 2008

Jan. 28, 2008

On So, 2008-01-27 at 21:18 +0100, Alexander Nicolaysen Sørnes wrote: > SHELLEXECUTEINFOW sei; > + OSVERSIONINFOW vi; > WCHAR *args = NULL; > - int i; > + int i = 1; > The idention show a mismatch between SPACE and TAB -- By by ... Detlef

1 0