>> Ok, I saw that you fixed the WCHAR/byte mess. But there is still a possibility that
>> the function can copy a string longer than buffer if it already has an appended
>> null.
>
>That shouldn't happen, NtQueryValue should have signaled an overflow
>in that case. Do you have a test case showing
On Wednesday 25 February 2004 18:57, Dimitrie O. Paun wrote:
> Well, having this XML only for description is a bit useless,
> isn't it? But if you like it so much, why not use the XML
> features, and give up on the restrictive naming:
Yeah I agree.
>
> wine_someimage.png
> full/wine_som
Fabian Cenedese <[EMAIL PROTECTED]> writes:
> Ok, I saw that you fixed the WCHAR/byte mess. But there is still a possibility that
> the function can copy a string longer than buffer if it already has an appended null.
That shouldn't happen, NtQueryValue should have signaled an overflow
in that ca
Am Donnerstag, 26. Februar 2004 03:45 schrieb Hans Leidekker:
> On Wednesday 25 February 2004 15:06, Stefan Leichter wrote:
> > The problem is that your package expects mingw install in /usr/local/
> > i386-mingw32 but the Redhat one is in /usr/mingw. The error message is
> > attached.
>
> There ar
On Thu, 2004-02-26 at 08:59, Alexandre Julliard wrote:
> Robert Reif <[EMAIL PROTECTED]> writes:
>
> > I think it might be worthwhile considering restructuring the audio
> > drivers into hardware independent wave, direct sound, midi
> > and mixer sections and a hardware dependent low level
> >
Robert Reif <[EMAIL PROTECTED]> writes:
> I think it might be worthwhile considering restructuring the audio
> drivers into hardware independent wave, direct sound, midi
> and mixer sections and a hardware dependent low level
> implementation for oss, alsa, ...
Yes we should definitely do some
Mike Hearn <[EMAIL PROTECTED]> writes:
> Alexandre: I said at the time we should apply the patch I sent but disable
> it, so it doesn't get lost/forgotten about. Here's another reason we
> should do that - it'll stop people reimplementing what has already been
> done.
I'm not going to commit non-
On Wednesday 25 February 2004 15:06, Stefan Leichter wrote:
> The problem is that your package expects mingw install in /usr/local/
> i386-mingw32 but the Redhat one is in /usr/mingw. The error message is
> attached.
There are two ways out here. One is to change the install path
to /usr/mingw in
Am Dienstag, 24. Februar 2004 17:12 schrieb Hans Leidekker:
> On Monday 23 February 2004 04:16, Hans Leidekker wrote:
> > I have been working on these RPMS already and plan on putting
> > up a page somewhere shortly. Initial goal is to compile all
> > Wine tests out of the box.
>
> As promised, a s
Dan Kegel wrote:
Also, there's a way to use Visual Studio's debugger with Wine remotely,
but I can't see where that's documented. (Hey, can anyone who knows
how to do this point us to the doc?)
- Dan
Also use winedbg
- Make sure you have MyApp.pdb next to the MyApp.exe that you are
running un
Hi Ken,
I'm really sorry about this but I already implemented LockWindowUpdate
about a month or two ago. Unfortunately it is blocking on moving
invalidation handling into the wineserver, and was not applied.
So, I'm afraid that (a) the work has already been done and (b) the patch
you sent, is wro
On Wed, 25 Feb 2004, Jeremy Newman wrote:
> The xml file would look like this:
>
>
>
> hey, you can write stuff here..
>
>
Well, having this XML only for description is a bit useless,
isn't it? But if you like it so much, why not use the XML
features, and give up on the restrictive n
Jeremy,
On Wed, 25 Feb 2004 11:13:28 -0600, Jeremy Newman wrote:
> I also think the idea of having screenshot descriptions is a good idea.
> I also agree with Dimi here (say it's not so!), having a simple text
> file for each shot. I would use my simple xml parser thing to do it
> (since it alread
On Wed, 25 Feb 2004, Mike Hearn wrote:
> Another confusing debug channel allocation bites the dust...
>
> -WINE_DEFAULT_DEBUG_CHANNEL(win32);
> +WINE_DEFAULT_DEBUG_CHANNEL(time);
The win32 debug channel should just die, it's too generic to
be useful. The entire friggin' API is Win32 :) Here is
[EMAIL PROTECTED] wrote:
I am trying to run a MFC application in Red Hat Linux 8 using WINE (latest
version).
When i start the application with wine the application performs some intialization
but when the main window is about to be displayed, the application crashes giving
the following error
On Wed, 2004-02-25 at 10:46, Dimitrie O. Paun wrote:
> On Wed, 25 Feb 2004, Paul van Schayck wrote:
>
> > This is my first attemp to do something for winehq. So, are you interested
> > in descriptions for screenshots?
>
> Thank you for your contribution. I think having a description for each
> ima
On Wed, 25 Feb 2004, Paul van Schayck wrote:
> This is my first attemp to do something for winehq. So, are you interested
> in descriptions for screenshots?
Paul,
Thank you for your contribution. I think having a description for each
image is a really good idea. However, I don't think I like hav
>> Contrary to my first tests these API functions understand VB hex
>> numbers quite well. There is no problem with these calls on Win2K:
>>
>> OLECHAR test[]={'&', 'H', 'F', '0', '8', 'F', '\0'};
>> VarI4FromStr(test, LANG_NEUTRAL, NUMPRS_STD, &out);
>> VarParseNumFromStr(test, LANG_NEUTRAL, NUM
Hello Sir,
I am trying to run a MFC application in Red Hat Linux 8 using WINE (latest
version).
When i start the application with wine the application performs some intialization
but when the main window is about to be displayed, the application crashes giving
the following error.
" fixme:d
Hey,
Wouldn't it be nice to have a description of every screen at the
screenshot page of winehq.com? To know what you see, I don't know half the
programs I see on those screens.
I have made a patch for the site file. The patch needs a a description.txt
file inside /images/shots/ in this form:
[sc
Hi,
I spent some time cross compiling all of Wine with MinGW according
to this recipe:
http://winehq.com/?issue=123#Cross-compiling Wine
and I thought you might be interested in the results. I can report
a bug in Wine's makefiles right away: having those vxd's in subdirectories
that end in .v
On Wednesday 25 February 2004 04:15 am, Fabian Cenedese wrote:
> Contrary to my first tests these API functions understand VB hex
> numbers quite well. There is no problem with these calls on Win2K:
>
> OLECHAR test[]={'&', 'H', 'F', '0', '8', 'F', '\0'};
> VarI4FromStr(test, LANG_NEUTRAL, NUMPRS_
On Wednesday 25 February 2004 06:28 am, Mike Hearn wrote:
> 4) Theme all widgets with a hard link to uxtheme but have a "Win98 look"
> theme which replicates the current drawing?
This actually would end up happening in all cases, if theming is disabled the widget
is responsible for drawing
itself
On Tue, 24 Feb 2004 22:04:13 -0500, Kevin Koltzau wrote:
> I'm starting to work on theming some widgets, and I've come up with a few methods of
> doing this:
> 1) Add theming code to every widget itself, static link to uxtheme.dll
> 2) Add theming code to every widget itself, using LoadLibrary/Get
On Tuesday 24 February 2004 17:51, Uwe Bonnes wrote:
> http://www.winehq.com/site/docs/wine-devel/testing-windows
> 4.5.3. With MinGW
>
> should read:
>
> Have mingw installed. For an RPM package look e.g. at
> http://mirzam.it.vu.nl/mingw/
>
> Run "make crosstest". Run test like "wine -- msvcr
>>I'm trying (again) to run a VB app on wine. But it never shows up. Instead
>>I only see a dialog with this Type mismatch error and then it quits. I tried
>>to find the place where it goes wrong. Apparently it tries to parse a number
>>from a string in VB notation.
>>0009:trace:ole:VarParseNumFro
Hi
Can anybody comment on this?
http://www.winehq.org/hypermail/wine-patches/2004/02/0121.html
I know that it's not the best solution (or if it is it's without explanation).
I tried to find anything about this magic number but I found nothing.
Unless someone has a reason _not_ to apply it I vote
Robert Shearman wrote:
I don't know, but any C99-compatible compiler should support the LL suffix
and the ll width format specifier (in the C library). MSVC doesn't support
these and AFAIK never will.
Rob
Never say never. It does if you:
#define LL i64
#define ll i64
So what is exactly the pr
28 matches
Mail list logo
