Re: [Fwd: Wine-Wiki.org]

2005-01-28 Thread Tony Lambregts
Francois Gouget wrote: On Thu, 27 Jan 2005 [EMAIL PROTECTED] wrote: Wine's release cycle is simply irrelevant to the Application Maintainer's Guide. No, it is not important to you. To me its about what is resonable to ask a maintainer to do. At some point in time we will be stable and we will n

Re: unicode "tables"

2005-01-28 Thread Andrew Bartlett
On Fri, 2005-01-28 at 23:47 +0800, Dmitry Timoshkov wrote: > "Mike McCormack" <[EMAIL PROTECTED]> wrote: > > > Jonathan Wilson wrote: > > > I remember some people talking about some kind of "unicode tables" that > > > WINE has but that dont match with the MS implementation. > > > What are the tab

Re: MSVCRT: Re-implement *printf

2005-01-28 Thread Jesse Allen
On Fri, 28 Jan 2005 12:48:12 +, Aneurin Price <[EMAIL PROTECTED]> wrote: > Changelog: > > > Re-implement all *printf functions in msvcrt.dll, according to > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_format_specification_fields_.2d_.printf_and_wprintf_fu

Re: [IWineD3d + d3d9] bogus query implemetation

2005-01-28 Thread Oliver Stieber
While we're being picky about silly details, normal > Wine code style is to > have a space between the comment markers and the > comment, ie > > /* foo */ > > not > > /*foo*/ > > thanks -mike > > opps, missed this in v3, I'll send up a incremental with cosmetics in later, and try to make s

Re: Slick build output

2005-01-28 Thread Robert Shearman
Vincent Béron wrote: Le ven 28/01/2005 à 12:22, Robert Shearman a écrit : [snip] write_msft.c:590: warning: 'ctl2_alloc_importinfo' defined but not used write_msft.c:628: warning: 'ctl2_alloc_importfile' defined but not used write_msft.c:1048: warning: 'ctl2_find_nth_reference' defined but not u

Re: Slick build output

2005-01-28 Thread Vincent Béron
Le ven 28/01/2005 à 12:22, Robert Shearman a écrit : [snip] > write_msft.c:590: warning: 'ctl2_alloc_importinfo' defined but not used > write_msft.c:628: warning: 'ctl2_alloc_importfile' defined but not used > write_msft.c:1048: warning: 'ctl2_find_nth_reference' defined but not used > > It doesn'

Re: MSVCRT: Re-implement *printf

2005-01-28 Thread Juan Lang
Hi Aneurin, > Nobody has any comments about this? Well, I held off thinking I'd give Alexandre a chance to chime in. As it's a large patch, I knew it could take a while. But since he hasn't.. My advice isn't going to be as specific as it has been in the past. You've obviously done a lot on th

Re: Slick build output

2005-01-28 Thread Steven Edwards
Hi Jason, --- Jason But <[EMAIL PROTECTED]> wrote: > This patch doesn't do the complete job, instead only produces output for the > compile (gcc) stages. In fact, (make install) will produce no output at all! > > If people think this is a good idea, simple extensions will lead to complete >

Re: v2.: [IWineD3d + d3d9] bogus query implemetation

2005-01-28 Thread Juan Lang
Hi again Oliver, > this should be better. Yeah, but this function is still borked, I think: +HRESULT WINAPI IWineD3DDeviceImpl_CreateQuery(IWineD3DDevice *iface, D3DQUERYTYPE Type, IWineD3DQuery** ppQuery){ +IWineD3DDeviceImpl *This = (IWineD3DDeviceImpl *)iface; + +if(NULL == ppQuer

Re: Can winedbg --auto backtrace all threads?

2005-01-28 Thread Mike Hearn
On Fri, 28 Jan 2005 13:09:26 -0800, Michael Ost wrote: > PS: thanks for that 'bt all' command. It's not in the winedbg man page > and will save me a lot of typing when I use winedbg in the future. Correct, it is not. That's because I suck. If you want to submit a patch for that then great. BTW yo

Re: [IWineD3d + d3d9] bogus query implemetation

2005-01-28 Thread Mike Hearn
On Fri, 28 Jan 2005 11:39:53 -0800, Juan Lang wrote: > +/*Just a check to see if we support this type of query*/ > +HRESULT hr = D3DERR_NOTAVAILABLE; While we're being picky about silly details, normal Wine code style is to have a space between the comment markers and the c

Re: Can winedbg --auto backtrace all threads?

2005-01-28 Thread Michael Ost
On Fri, 2005-01-28 at 12:58, Eric Pouech wrote: > IMO, the cleanest way would be to add an option (like the --command in gdb) > which would execute commands out of a file (almost everything is in place, > you > just need to pass the name of the file in the call to parser() in winedbg.c). > Then

Re: Can winedbg --auto backtrace all threads?

2005-01-28 Thread Eric Pouech
Michael Ost a Ãcrit : On Fri, 2005-01-28 at 12:13, Eric Pouech wrote: Michael Ost a Ãcrit : In order to help track down sporadic runtime crashes in our testing process, I have turned on winedbg --auto when wine handles exceptions via the AeDebug registry entry. don't use the --auto flag and use t

Re: Q: porting driver for USB scanner - where to start?

2005-01-28 Thread Kuba Ober
> Interfacing directly with the scanner might work using Wine's brand new > and very incomplete USB interface (I believe part of it is in setupapi) > but that would probably be more code and you would still end up writing > what is essentially a driver. Nope. On "client" side it would be just the

Re: Can winedbg --auto backtrace all threads?

2005-01-28 Thread Eric Pouech
Michael Ost a Ãcrit : On Fri, 2005-01-28 at 12:13, Eric Pouech wrote: Michael Ost a Ãcrit : In order to help track down sporadic runtime crashes in our testing process, I have turned on winedbg --auto when wine handles exceptions via the AeDebug registry entry. don't use the --auto flag and use t

Re: Can winedbg --auto backtrace all threads?

2005-01-28 Thread Michael Ost
On Fri, 2005-01-28 at 12:13, Eric Pouech wrote: > Michael Ost a Ãcrit : > > In order to help track down sporadic runtime crashes in our testing > > process, I have turned on winedbg --auto when wine handles exceptions > > via the AeDebug registry entry. > don't use the --auto flag and use the 'bt

Re: Can winedbg --auto backtrace all threads?

2005-01-28 Thread Eric Pouech
Michael Ost a écrit : Is there a way to have winedbg --auto do a backtrace of all the threads in an app at exception time? In order to help track down sporadic runtime crashes in our testing process, I have turned on winedbg --auto when wine handles exceptions via the AeDebug registry entry. This

Re: PRESS: run windows viruses with wine ...

2005-01-28 Thread Brad DeMorrow
David D. Hagood wrote: On 01/27/2005 03:03 PM, Troy Rollo wrote: Even if they don't run Outlook Express, with Linux 2.6 there is a facility to have the kernel recognise foreign executable file formats and run them by means of another executable. If used to run Wine executables (and somebody on /

Re: MSVCRT: Re-implement *printf

2005-01-28 Thread Aneurin Price
Changelog: Re-implement all *printf functions in msvcrt.dll, according to http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_format_specification_fields_.2d_.printf_and_wprintf_functions.asp and descriptions of appropriate functions. This should fix, among other thi

Re: [IWineD3d + d3d9] bogus query implemetation

2005-01-28 Thread Juan Lang
Hi Oliver, +HRESULT WINAPI IWineD3DDeviceImpl_CreateQuery(IWineD3DDevice *iface, D3DQUERYTYPE Type, IWineD3DQuery** ppQuery){ +IWineD3DDeviceImpl *This = (IWineD3DDeviceImpl *)iface; + +if(NULL == ppQuery){ +/*Just a check to see if we support this type of query*/ +

Re: Slick build output

2005-01-28 Thread Robert Shearman
Dmitry Timoshkov wrote: "Robert Shearman" <[EMAIL PROTECTED]> wrote: How many developers need to see the command line being passed to gcc? I would argue that it would be more useful if there was a short "[CC] regsvr.c" rather than the multi-line output there is now which makes warnings more d

Re: Slick build output

2005-01-28 Thread Dmitry Timoshkov
"Robert Shearman" <[EMAIL PROTECTED]> wrote: > How many developers need to see the command line being passed to gcc? I > would argue that it would be more useful if there was a short "[CC] > regsvr.c" rather than the multi-line output there is now which makes > warnings more difficult to spot.

Re: Slick build output

2005-01-28 Thread Robert Shearman
Alexandre Julliard wrote: Jason But <[EMAIL PROTECTED]> writes: Not really related to the actual wine development but more to the make/build/install environment. Remembering the most wine users will not necessarily be developers we should consider improving the output of running (./configure

Re: Slick build output

2005-01-28 Thread Alexandre Julliard
Jason But <[EMAIL PROTECTED]> writes: > Not really related to the actual wine development but more to the > make/build/install environment. > > Remembering the most wine users will not necessarily be developers we should > consider improving the output of running (./configure && make) to make i

Re: Slick build output

2005-01-28 Thread Robert Shearman
Jason But wrote: Hello all, Not really related to the actual wine development but more to the make/build/install environment. Remembering the most wine users will not necessarily be developers we should consider improving the output of running (./configure && make) to make it more user friendly

Re: unicode "tables"

2005-01-28 Thread Dmitry Timoshkov
"Mike McCormack" <[EMAIL PROTECTED]> wrote: > Jonathan Wilson wrote: > > I remember some people talking about some kind of "unicode tables" that > > WINE has but that dont match with the MS implementation. > > What are the tables for? > > And what API call(s) are involved? > > StringCompareA/W a

Re: [WINETEST] How is a visible desktop detected

2005-01-28 Thread Paul Vriens
On Fri, 2005-01-28 at 13:52, Ferenc Wagner wrote: > Paul Vriens <[EMAIL PROTECTED]> writes: > Hmm, services use an invisible desktop by default AFAIK. > It shouldn't matter how you started winrash (the service), > but how you started winetest itself. If it's started by > winrash, it runs on an inv

Re: unicode "tables"

2005-01-28 Thread Mike McCormack
Jonathan Wilson wrote: I remember some people talking about some kind of "unicode tables" that WINE has but that dont match with the MS implementation. What are the tables for? And what API call(s) are involved? StringCompareA/W and related functions won't do the exactly the same thing as Windows

unicode "tables"

2005-01-28 Thread Jonathan Wilson
I remember some people talking about some kind of "unicode tables" that WINE has but that dont match with the MS implementation. What are the tables for? And what API call(s) are involved?

Re: [WINETEST] How is a visible desktop detected

2005-01-28 Thread Ferenc Wagner
Paul Vriens <[EMAIL PROTECTED]> writes: > I have a Win98/WNT/W2K (on VMWare) and a XP Home > system. All are running the winrash service. All were > started when I was logged in but only the W98 and WNT were > considered running on a visible desktop. Hmm, services use an invisible desktop by defa

Re: X11DRV: Fix to incorrect detection and other bugs of keyboard driver in XKB presence

2005-01-28 Thread Alexandre Julliard
"Oleh R. Nykyforchyn" <[EMAIL PROTECTED]> writes: > Add alternative (alpha) code to keyboard driver in x11drv that can handle > correct detection and switching of keyboard layout both with and without > XKB extension. Add temporary --enable-xkb feature to configure script > to enable compilation

Re: msvcrt: translate name to locate program

2005-01-28 Thread Alexandre Julliard
Michael Wu <[EMAIL PROTECTED]> writes: > Would passing an empty path (eg. ".") to the function solve the problem? > SearchPath does a lot of what spawn needs to find the real filename, and I'd > like to avoid duplicating what SearchPath does. If all you need is to append ".exe" calling SearchPa

Re: Re: [winecfg] Show detected audio systems, and offer selection

2005-01-28 Thread Paul van Schayck
So in the end we will just keep it all the same for now? Or did I lost you all. Or do we want to follow Chris suggestion by offering a frontend to the driver load order list? Thanks, Paul

Re: [Fwd: Wine-Wiki.org]

2005-01-28 Thread Stefan Munz
Am Donnerstag, 27. Januar 2005 10:30 schrieb Jonathan Ernst: > > > > So these 'supported' applications are no different from any other > > application and the medals mean nothing more than the old rating system. > > They just have 4 levels instead of 6. > > I think having more than 3-4 levels is t

Re: [Fwd: Wine-Wiki.org]

2005-01-28 Thread Francois Gouget
On Thu, 27 Jan 2005 [EMAIL PROTECTED] wrote: Francois Gouget wrote: [Snip] * Test the application on a regular basis. Ideally you would test it once a week so that you can quickly notify the Wine developers of any regression. The earlier a Wine regression is noticed, the easier it will be to