"Robert Shearman" <[EMAIL PROTECTED]> wrote:
this one should be added to windows.h (maybe it's not the best
place for it, but it works):
#define stricmp strcasecmp
This define is not present in the Platform SDK. It is a by-product of
using glibc instead of msvcrt as your C library. If you us
"Timm" <[EMAIL PROTECTED]> wrote:
My one win app that makes me a devotee of WINE is TablEdit
(demo at www.tabledit.com/download/tabled32.exe)
has a custom font , tef260.ttf, that has failed to display since
somewhere after ver 9.6. The program installs the font into
c:\windows\font, but can not
[I keep my source and object in different directories, and generic.ppd isn't
found during build]
That method of building is great, and is supported, but
not too many people build that way, so bugs do creep in.
You can either keep living with the workaround you found,
or submit a patch to fix t
With a recent update to Wine 0.9.31, my printing issue [1] has changed
in some way that actually generated some meaningful error messages
being printed. I don't know if this is indeed the same issue or not.
However, here are the messages that I started getting:
$ wine notepad
Couldn't find PPD fi
On 17/02/07, Duane Clark <[EMAIL PROTECTED]> wrote:
Well, no server changes are needed just to implement 32 bits per pixel.
There are rather simple changes needed in the file
dlls/winex11.drv/mouse.c in create_cursor(), and the places that need to
be changed are cleverly marked by "switch (ptr->b
On 17/02/07, Dan Kegel <[EMAIL PROTECTED]> wrote:
Could you break off some of the features and
do them first, e.g. 32 bpp cursors?
- Dan
My plan was to redo the set for local cursors only, but there's also
wined3d that needs attention :-)
Dan Kegel wrote:
http://bugs.winehq.org/show_bug.cgi?id=4273 points to a
patch set that implements 32 bit per pixel cursors
and a bunch of other cursor stuff.
Looks like the patch got dropped by the author, though,
and since it makes server changes, it's going to be hard
to get past Alexandre.
On 2/16/07, H. Verbeet wrote:
http://bugs.winehq.org/show_bug.cgi?id=4273 points to a
patch set that implements 32 bit per pixel cursors
and a bunch of other cursor stuff. [What's up with it?]
I believe the problem is not that Henri has dropped the patches.
The problem was that Alexandre didn'
Robert Shearman <[EMAIL PROTECTED]> wrote: Joris Huizer wrote:
> Hello,
>
> I was looking at the result of configuring with -ansi,
> -pedantic flags. It gives loads of warnings (not all
> relevant - also complaining about 'long long' not
> being ansi) and indicates unnamed unions, among other
> t
Joris Huizer wrote:
Hello,
I was looking at the result of configuring with -ansi,
-pedantic flags. It gives loads of warnings (not all
relevant - also complaining about 'long long' not
being ansi) and indicates unnamed unions, among other
things.
Could someone confirm my idea that unnamed unions
David Saez Padros wrote:
This line should be added to commctrl.h:
#define ListView_GetOrigin(hwndLV, ppt) \
(BOOL)SNDMSG((hwndLV), LVM_GETORIGIN, (WPARAM)0, (LPARAM)ppt)
I've submitted a patch for this.
this one should be added to windows.h (maybe it's not the best
place for it, but it w
(Please CC me, I'm not on the list)
According to:
http://undocumented.ntinternals.net/UserMode/Undocumented%20Functions/Executable%20Images/LdrGetProcedureAddress.html
The parameter order for LdrGetProcedureAddress is (Handle, Function,
Ordinal, Address)
The file dlls/ntdll/module.c has the
On Fri, 16 Feb 2007, WineHQ wrote:
> ChangeSet ID: 30931
> CVSROOT: /opt/cvs-commit
> Module name: lostwages
> Changes by: [EMAIL PROTECTED] 2007/02/16 18:13:29
Could we get rid of wineowner account? It makes it impossible to know
who's doing the changes. Each user having access to
Jeff L a écrit :
Eric Pouech wrote:
Jeff Latimer a écrit :
Establish the framework for testing NtCreateMailslotFile. Have
fixed issues with NTSTATUS return codes etc.
those tests belong to dlls/ntdll, not dlls/kernel32
also, if the test is for ntdll functions, it shouldn't use kernel32
ones.
"Jeff L" <[EMAIL PROTECTED]> wrote:
Have reread MSDN
http://msdn2.microsoft.com/en-us/library/ms648410.aspx and it seems
that NtClose has been superseded by CloseHandle. So I suppose that
CloseHandle is the one to use.
The information in MSDN is misleading in this case, CloseHandle is a
ke
Hello,
I was looking at the result of configuring with -ansi,
-pedantic flags. It gives loads of warnings (not all
relevant - also complaining about 'long long' not
being ansi) and indicates unnamed unions, among other
things.
Could someone confirm my idea that unnamed unions must
all be dealt wit
Eric Pouech wrote:
Jeff Latimer a écrit :
Establish the framework for testing NtCreateMailslotFile. Have fixed
issues with NTSTATUS return codes etc.
those tests belong to dlls/ntdll, not dlls/kernel32
also, if the test is for ntdll functions, it shouldn't use kernel32
ones... hence, NtClose
Jeff Latimer a écrit :
Establish the framework for testing NtCreateMailslotFile. Have fixed
issues with NTSTATUS return codes etc.
those tests belong to dlls/ntdll, not dlls/kernel32
also, if the test is for ntdll functions, it shouldn't use kernel32
ones... hence, NtClose should be used inste
> http://bugs.winehq.org/show_bug.cgi?id=4273 points to a
> patch set that implements 32 bit per pixel cursors
> and a bunch of other cursor stuff.
>
> Looks like the patch got dropped by the author, though,
> and since it makes server changes, it's going to be hard
> to get past Alexandre.
>
> I
Dmitry Timoshkov wrote:
"Jeff L" <[EMAIL PROTECTED]> wrote:
To close the handle returned by an NT API you have you use an NT API
as well.
What is not apparent in the explanation above?
I have no problem with what you have said though I did have a bit of
difficulty marrying to the sentence be
"Jeff L" <[EMAIL PROTECTED]> wrote:
To close the handle returned by an NT API you have you use an NT API
as well.
What is not apparent in the explanation above?
Have reread MSDN http://msdn2.microsoft.com/en-us/library/ms648410.aspx
and it seems that NtClose has been superseded by CloseHandl
Dmitry Timoshkov wrote:
"Jeff Latimer" <[EMAIL PROTECTED]> wrote:
+ok( CloseHandle(hslot), "CloseHandle failed\n");
To close the handle returned by an NT API you have you use an NT API
as well.
Have reread MSDN http://msdn2.microsoft.com/en-us/library/ms648410.aspx
and it seems that NtClos
22 matches
Mail list logo
