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

News about iPod Sync and iTunes?

by Rainer M Krug

Hi are there any news / patrches on the iPod sync with iTunes? Thanks Rainer

March 31, 2008

Re: Proposal: versioning .wine directory

by Dan Kegel

On Mon, Mar 31, 2008 at 2:44 AM, Alexandre Julliard <julliard(a)winehq.org> wrote: > I think we should > stop telling people to blow away their .wine, and have them run > wineprefixcreate instead. Then if wineprefixcreate doesn't do the > update correctly we need to figure out why and fix it. Once we are > confident that it can do the update safely we can have it run > automatically when it detects an upgrade. Roger.

March 31, 2008

Re: Proposal: versioning .wine directory

by Alexandre Julliard

"James Hawkins" <truiken(a)gmail.com> writes: > If we have a stable wine prefix in 1.0, I don't see what could > possibly be added in 1.2 that would break that. The idea is that, > even if you add a new dll that needs to be registered in, say, 1.0.5, > you still don't need to remove your wine prefix or reinstall any apps. That should already be the case, there's nothing magical about 1.0 that would suddenly cause that to happen. And if there are cases where it doesn't work we have to fix them before 1.0 is out. I think we should stop telling people to blow away their .wine, and have them run wineprefixcreate instead. Then if wineprefixcreate doesn't do the update correctly we need to figure out why and fix it. Once we are confident that it can do the update safely we can have it run automatically when it detects an upgrade. -- Alexandre Julliard julliard(a)winehq.org

March 31, 2008

iPod sync news?

by Rainer M Krug

Hi are there any news on the iPod Touch sync front? Any patches available? Thanks Rainer

March 31, 2008

Re: user32: Implement BroadcastSystemMessage, try 5.1

by Alexandre Julliard

Vitaliy Margolen <wine-devel(a)kievinfo.com> writes: > I remember sending the patch for this exact thing a while back, which you of > course refused under the same pretense - showing a real life app that > depends on it. So if tests are not a real life app that shows a difference > between Wine and windows - then why do we bother with Wine at all? At least > should change the moto to "might run some apps with loads of problems and > never be 100% compatible". > > One for sure will find an app that in one way or another depends on > undocumented windows behavior. So if a test can be written to show a > difference between Wine and windows. Then this difference should be fixed in > Wine. It all comes down to where we want to spend our efforts. It's very easy to write a million last error tests, and then we'd have to spend months fixing Wine by adding save/restore of last error all over the place, for no benefit at all. Our time is much better spent fixing things that actually matter, and not making the code uglier for things that don't. -- Alexandre Julliard julliard(a)winehq.org

March 31, 2008

Re: midl question

by Alistair Leslie-Hughes

Hi Rob, What work would need to be done to get widl to support __stdcall? Best Regards Alistair Leslie-Hughes

March 31, 2008

Re: Direct3D shader compiler infrastructure

by H. Verbeet

On 31/03/2008, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote: > With WineD3D working on the same language, we have to share the language > definition between the shader library and WineD3D, or put the shader compiler > into WineD3D as well. I do not like the 2nd way, as it puts things together > that don't have to be in one lib, and wastes runtime memory. A 3rd way I have > to consider was a SlReadShader() function with callbacks which takes over the > current role of shader_generate_main() in WineD3D. I am not quite convinced > by this either. > Looks reasonable enough in general. I guess it would make sense to create some kind of "shader utilities" library that can be used from both wined3d and d3d9x. You could in principle even move GLSL/ARB code generation in there, although that isn't required of course.

March 31, 2008

Re: ws2_32 janitorial questions

by Juan Lang

> ws2_32/async.c has the following global declarations: > > /* protoptypes of some functions in socket.c > */ > UINT16 wsaErrno(void); > UINT16 wsaHerrno(int errnr); > > ws2_32/socket.c has the following global declarations: > > UINT wsaErrno(void); > UINT wsaHerrno(int errnr); > > Where are these functions defined? And, assuming that the above are > conflicting declarations, what type does each of these functions actually > return? socket.c: http://source.winehq.org/source/dlls/ws2_32/socket.c#L4055 They return UINTs. The return types don't conflict if compiled with a 32-bit compiler, but the one in async.c at least looks incorrect. --Juan

March 31, 2008

Re: wine based win32 printer drivers

by Marcel Partap

> A Postscript Driver has no raster renderer... > A Postscript Driver has a Postscript Engine. ... ^ ^ >> DRIVER_EVENT_INITIALIZE, 3, > "3" is wrong here. See: myAddPrinterDriverEx(DWORD level, ... It seemed suspicious to me anyway.. How do those integer shifts creep into my retyped header files again and again? mmmmhhh ... *g > Since there are much more Events, we need the DriverUI in more Places > later. I suggest a simple struct, which can be extended later > (The struct must include the Results from GetProcAddress) a struct.. that contains what? the function pointers and results? i had thought about adding a macro.. for hooking driver exports.. > The changes for winspool.drv must go in a seperate Patch. yeah it jsut was a quick and dirty preview patch ;) > WINSPOOL_CallDrvDocumentProperties is the wrong name, when you > call DrvDocumentPropertySheets. statement totally makes sense. > You should collect all API in winspool.drv, that need the driverui > (some are not implemented) and design a simple struct > with helper functions (Use monitor_t as example). I dont really grok it... like the DDI_FUNCS array in the patch i sent you or rather somethign stuct { LPWSTR name; LPWSTR driverdll; HMODULE hdriver; LPWSTR interfacedll; HMODULE hinterface, DWORD refcount; } printertriver_t; ? > Not all Drivers Export DrvDocumentPropertySheets. > You must prepare to use a Fallback to get the default devmode > (DrvConvertDevMode) ok just need to transplant my old code > See winspool.drv/monitor_load as Example: l8r :) > The current Code is a crosscall from DocumentPropertiesW to > DocumentPropertiesA. > The DDI-API is unicode and should be the prefered way. so shall i put the ddi call before that deprecated stuff? and does it need to be called from docpropsA? oh and I reodne the EnumForms patch (now less monsterous ;). Now here's only the part that provides the builtin forms, but very easy to expand, once its ready to be &/ comimtted i'll do the addforms delforms stuff.. and oh sh1t gotta write my soc application today last day heh.. this time i'm opting for drupal/php code though C/win32api is just too hellish *g n8 -- <div id="signature"> "Obstacles are those frightful things you see when you take your eyes off your goal." -- Henry Ford (1863-1947) Change the world! Vote revolution: http://hfopi.org/vote-future </div>

March 31, 2008

Re: setupapi: prevent page faults in SetupDiDeleteDeviceInterfaceRegKey

by Vitaliy Margolen

Christopher wrote: > Changelog: > Check that the handle and pointer passed to > SetupDiDeleteDeviceInterfaceRegKey are valid to read from. This patch > continues to address bug #12242 > > - if (!DeviceInterfaceData || > + if (!DeviceInterfaceData || IsBadReadPtr(DeviceInterfaceData, sizeof(SP_DEVICE_INTERFACE_DATA)) || Don't ever use IsBadReadPtr and IsBadWritePtr functions. They are bad and even MS stopped using them. You have to use TRY-EXCEPT block around an access to the memory. For example see implementation of lstrcpyA (kernel32/string.c: 359). > + ok(!ret && GetLastError() == ERROR_INVALID_HANDLE, "Expected SetupDiDeleteDeviceInterfaceRegKey to return FALSE, got %s, \ > +with error code: 6, got %d\n", ret ? "TRUE" : "FALSE", GetLastError()); This is bad way to split strings in c. Do something like this: ok(!ret && GetLastError() == ERROR_INVALID_HANDLE, "Expected SetupDiDeleteDeviceInterfaceRegKey to return FALSE, got %s, " "with error code: 6, got %d\n", ret ? "TRUE" : "FALSE", GetLastError()); Vitaliy.

March 31, 2008