Vitaliy Margolen wrote:
On 06/30/2010 09:22 AM, Max TenEyck Woodbury wrote:
1) Would including the URL of the MSDN article be useful/a good idea?
No. Microsoft in all these years haven't figured out how to create permanent
links. All, and I really mean it _ALL_ URLS on MSDN had changed
Dmitry Timoshkov wrote:
Max TenEyck Woodbury wrote:
I created the top page as a table and populated it with all the
directory entries in the 'dll' directory. Somebody immediately deleted
it. WTF?
Creating a MSDN clone does not belong to the Wine project.
Dmitry:
I think you com
On Fri, Jul 2, 2010 at 7:35 AM, Octavian Voicu wrote:
>
> PS: there are other resources except MSDN; for example, osronline.com
> has very good documentation for windows driver developers, including
> some undocumented APIs.
>
I don't know if this is worth mentioning or not,
Geoff Chappell maint
I've found the following warning the the file comdlg32:
/*
* WARNING: DO NOT CHANGE THE SIZE OF THE STANDARD DIALOG TEMPLATES.
*/
Does that mean that I can't correct the size of the buttons or strings
that are wrong in the Portuguese template file? Or is that only a
warning for the English file
On Thu, Jul 1, 2010 at 8:06 PM, Erich Hoover wrote:
> 3) Provide unchanging URLs that can legitimately be used in the source
> code without fear of them changing every week (or being lost forever
> in the case of some older functions)
> 4) Document the ever-growing list of unexpected behaviors tha
Am 01.07.2010 21:55, schrieb Alexandre Julliard:
> None of that, of course. The resources are built at compile time, at run
> time you create a PE header and copy the needed resource data. You may
> even be able to use UpdateResource to make things easier.
Do we have existing tests creating PE hea
W dniu 1 lipca 2010 21:55 użytkownik Alexandre Julliard
napisał:
> Mariusz Pluciński writes:
>
>> W dniu 1 lipca 2010 21:27 użytkownik Alexandre Julliard
>> napisał:
>>> You can't do that in the Makefile, you need to generate the files at run
>>> time.
>>
>> Huh, so while executing the test, I n
Mariusz Pluciński writes:
> W dniu 1 lipca 2010 21:27 użytkownik Alexandre Julliard
> napisał:
>> You can't do that in the Makefile, you need to generate the files at run
>> time.
>
> Huh, so while executing the test, I need to run at least resources
> compiler and linker, right? It looks really
W dniu 1 lipca 2010 21:27 użytkownik Alexandre Julliard
napisał:
> You can't do that in the Makefile, you need to generate the files at run
> time.
Huh, so while executing the test, I need to run at least resources
compiler and linker, right? It looks really more complicated way, and
I admit that
Mariusz Pluciński writes:
> That's true on Wine, but I also want to make my tests runnable
> under Windows, so in this case I need to create native PE modules.
>
> And as I said, my main problem is that I don't know how to
> write rules in Makefile.in to build what I need.
You can't do that in
Tuomo Mattila wrote:
Why not just do the check and then pass it as a Wide to the 'W' function?
Simpler and less code to maintain/update?
>+
>+
>+FIXME("(%s, %p, %d, %p), stub!\n", debugstr_a(volumename),
>volumepathname, buflen, returnlen);
If this is not a full implementation, you nee
> Do they really need to be separate binaries?
Unfortunately yes. To the function I pass only the path to binary,
and it unpacks data internally, so I cannot select actual resource.
One binary can contain multiple GDFs only if they are translations
of the same file in few languages. And I don't k
> strncmp(arg, str, sizeof(str)-1) looks ugly.
Am I expected to accept that as an axiom? IMO, your strstr wrapper is
much uglier, in addition to being needlessly complex.
--Juan
> What's wrong with strncmp?
strncmp(arg, str, sizeof(str)-1) looks ugly.
Peter
> Wine doc says relay supports user32, ntdll, etc, but not gdi32.
> However when I run wine, some gdi32 calls are caught, e.g, CreateBitmap()
> But some aren't caught, e.g, CreateBitmapIndirect()
IIRC, calls across dlls are caught by +relay, but calls within the
same dll are not.
--Juan
Hi, all
I found that WINEDEBUG=+relay works by dlls/ntdll/relay.c
and I'm trying to catch function call of dlls.
Wine doc says relay supports user32, ntdll, etc, but not gdi32.
However when I run wine, some gdi32 calls are caught, e.g, CreateBitmap()
But some aren't caught, e.g, CreateBitmapIndir
On Thursday 01 July 2010 17:19:42 Stefan Dösinger wrote:
> Am Donnerstag 01 Juli 2010 16:54:08 schrieb Fabian Bieler:
> > -glTexImage2D(GL_TEXTURE_2D, 0, GL_LUMINANCE, 1, 1, 0,
> > GL_LUMINANCE,
>
> GL_UNSIGNED_BYTE, &white);
>
> > +glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA8, 1, 1, 0,
> Are you objecting to function or the implementation? It is a simple
> function that clarifies the code by making it self documenting,
> implemented fairly efficiently in a performance wise undemanding
> program.
What's wrong with strncmp?
--Juan
> Hi,
> sorry, but your patch is a bit ugly...
> please look at the code below /* determine if tihs switch is followed by a
> separate argument */ in winegcc.c and understand what it does.
> specially with next_is_arg, is_linker_arg,
I could set option_arg for semantic correctness.
> Also t
Using "quick and dirty" in the subject while code freeze is most likely not to
be commited :)
--
Best Regards, André Hentschel
Hi,
sorry, but your patch is a bit ugly...
please look at the code below /* determine if tihs switch is followed by a
separate argument */ in winegcc.c and understand what it does.
specially with next_is_arg, is_linker_arg,
Also the following is senseless:
+int strstartswith(const char * str,
Am 01.07.2010 19:26, schrieb Peter Davies:
>> My primary concern here is
>> participation
I think http://wiki.jswindle.com would also be a good place if he would
cooperate...
BTW: we should slowly come to an end with that discussion on wine-devel IMO
--
Best Regards, André Hentschel
On 07/01/2010 04:34 AM, Dmitry Timoshkov wrote:
Max TenEyck Woodbury wrote:
I created the top page as a table and populated it with all the
directory entries in the 'dll' directory. Somebody immediately deleted
it. WTF?
Creating a MSDN clone does not belong to the Wine project.
> My primary concern here is
> participation
Count me in! I think it would be a great way to learn the wine/windows
internals.
Peter
Erich Hoover writes:
> Obviously this is a big task and it's not something that is going to
> happen overnight, but I think that such a wiki could provide a useful
> service to the Wine community. My primary concern here is
> participation, since if there's little or no participation it will
> n
On Thu, Jul 1, 2010 at 7:56 AM, Alexandre Julliard wrote:
>
> Max TenEyck Woodbury writes:
>
> > So, would it be OK with you to extract the current documentation and
> > put it in the wiki where it can be more easily maintained? Wikis are
> > supposed to be good for exactly that kind of thing.
>
Am Donnerstag 01 Juli 2010 16:54:08 schrieb Fabian Bieler:
> -glTexImage2D(GL_TEXTURE_2D, 0, GL_LUMINANCE, 1, 1, 0, GL_LUMINANCE,
GL_UNSIGNED_BYTE, &white);
> +glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA8, 1, 1, 0, GL_RGBA,
GL_UNSIGNED_INT_8_8_8_8_REV, &black);
This will only work if t
> Wine can load and parse resources just from
> winelib (dll.so/exe.so) binaries.
I assume that dll.so/exe.so are for all practical purposes identical
to .dll/.exe except they can't be run on windows.
Peter
> Howdy,
>
> I was looking at http://bugs.winehq.org/show_bug.cgi?id=23421, and
> wanted to add a stub for it. Using winedump on a Windows 7 shlwapi.dll
> gives different exports than Windows XP SP3 shlwapi.dll. Which dll
> should the spec file be updated to match? I'm assuming the latest and
> gre
On 06/30/2010 09:52 AM, Mariusz Pluciński wrote:
> Checking results of routines execution is not problem for me. But thing I
> test is parser, so I need to pass various GDF files to routine. And, as GDFs
> are stored in binaries, I will need to create many binaries. They should be
> created in comp
Max TenEyck Woodbury writes:
> So, would it be OK with you to extract the current documentation and
> put it in the wiki where it can be more easily maintained? Wikis are
> supposed to be good for exactly that kind of thing.
>
> Once the wiki is populated with the initial information from the sou
On 06/30/2010 09:22 AM, Max TenEyck Woodbury wrote:
> 1) Would including the URL of the MSDN article be useful/a good idea?
No. Microsoft in all these years haven't figured out how to create permanent
links. All, and I really mean it _ALL_ URLS on MSDN had changed at least
once a year.
> 2) Would
On 06/30/2010 03:13 PM, Alexandre Julliard wrote:
Erich Hoover writes:
Alright, well then I won't do it. Is the existing documentation going
to be stripped at some point? It seems to me like we would benefit
from more-detailed function descriptions in the auto-generated API
documentation. I
33 matches
Mail list logo
