Andreas Mohr andi@rhlx01.fht-esslingen.de writes:
On Mon, Nov 05, 2001 at 06:20:24AM -0800, Andriy Palamarchuk wrote:
Is there any way to check:
- whether Wine process is the first process started
for current Wine server?
Heh, I should really know ;-) CLIENT_IsBootThread().
No, this shouldn't be used from user32 (besides it won't really do what you want). Why do you need this at all?
--- Alexandre Julliard julliard@winehq.com wrote:
Andreas Mohr andi@rhlx01.fht-esslingen.de writes:
On Mon, Nov 05, 2001 at 06:20:24AM -0800, Andriy
Palamarchuk wrote:
Is there any way to check:
- whether Wine process is the first process
started
for current Wine server?
Heh, I should really know ;-) CLIENT_IsBootThread().
No, this shouldn't be used from user32 (besides it won't really do what you want). Why do you need this at all?
Some system parameters will be initialized from X settings. Applications can change system parameters and expect to read these changes. Chages of system parameters are not reflected on X settings.
I'm going to initialize system parameters from X settings only on the first wine process startup, so all other wine processes for the same wine server can see the changes made by the first process. Other issue is fixed with this approach - the values in registry are not changed back to X settings on startup of new Wine process.
Alexandre, the submitted patch is not affected by this issue because none of the system parameters there is initialized from X settings.
Do you have any other concerns about the patch?
Andriy Palamarchuk
__________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com