Other side effect of the new code in shdocvw.inf is that it causes the
path in Internet Explorer shortcuts to be created incorrectly and
invalidly making IE unable to launch from its link file.
I would suggest all that IE registration stuff go into our iexplore.exe
instead of shdocvw.dll.
Eith
Hi Stefan, a few minor nits:
+ * one pixel has alpha != 0x00, and the mask ignored as described in the
Do you mean, "the mask is ignored...", or "the AND mask is ignored..." ?
+ * written at 8 / 16 bpp times do not knwow about the 32 bit alpha, so
s/knwow/know/
+for (y = 0; y <
Stefan Dösinger wrote:
> Am Mittwoch, 12. Dezember 2007 18:50:39 schrieb Kris Moore:
>> Hey all!
>>
>> One of our devs noticed that on FreeBSD we don't get the process name
>> set properly, so in "ps" we get a lot of wine-pthread garbage. Here's a
>> small patch to fix this in dlls/kernel32/p
Am Mittwoch, 12. Dezember 2007 18:50:39 schrieb Kris Moore:
> Hey all!
>
> One of our devs noticed that on FreeBSD we don't get the process name
> set properly, so in "ps" we get a lot of wine-pthread garbage. Here's a
> small patch to fix this in dlls/kernel32/process.c
>
> I tried to make this as
On Dec 12, 2007 2:15 AM, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> Stefan Doesinger <[EMAIL PROTECTED]> wrote:
>
> > This obsolettes the 15 bpp bitmap and 16 bpp screen compatibility since
> > 15 bpp bitmaps do not exist.
>
> 15 bpp bitmaps do exist. According to the Feng Yuan's book that depen
At 2007-12-11 20:01, Maarten Lankhorst wrote:
>Hi Gonzalo,
>
>Stefan Dösinger schreef:
> > Ow, ah, this is a different business. I think
> we use some Linux-only feature
> > to set the name, and Alexandre told me that
> at least MacOS doesn't have it. I
> > have no idea if there is a way to chang
Hi Sam,
-DWORD total_size;
+DWORD total_size, datalen;
(snip)
+if (count) datalen = *count;
(snip)
-if (len > *count) status = STATUS_BUFFER_OVERFLOW;
+if (len > datalen) status = STATUS_BUFFER_OVERFLOW;
I mentioned when I reviewed the patch that datale
Am Mittwoch, 12. Dezember 2007 16:15:11 schrieb Dmitry Timoshkov:
> No, I don't. I'd say that even with a technically 15 bpp screen depth
> video memory organization a driver would still say "16" in the user
> visible settings to avoid a possible user confusion, but report "15"
> on the API level.
"Stefan Dösinger" <[EMAIL PROTECTED]> wrote:
> > Stefan Doesinger <[EMAIL PROTECTED]> wrote:
> > > This obsolettes the 15 bpp bitmap and 16 bpp screen compatibility since
> > > 15 bpp bitmaps do not exist.
> >
> > 15 bpp bitmaps do exist. According to the Feng Yuan's book that depends on
> > the d
On Dec 11, 2007 11:34 PM, Lei Zhang <[EMAIL PROTECTED]> wrote:
> It looks as though you're running the current test with an older
> quartz.dll.so.
I'd better add a 'make clean' to my automated script.
And for that matter, a "rm -rf ~/.wine".
- Dan
Hans Leidekker <[EMAIL PROTECTED]> writes:
> Changelog
> Do glyph translation for truetype fonts only.
This fails here:
../../../tools/runtest -q -P wine -M usp10.dll -T ../../.. -p usp10_test.exe.so
usp10.c && touch usp10.ok
usp10.c:217: Test failed: Translation to place when told not to. WCH
Am Mittwoch, 12. Dezember 2007 10:15:32 schrieb Dmitry Timoshkov:
> Stefan Doesinger <[EMAIL PROTECTED]> wrote:
> > This obsolettes the 15 bpp bitmap and 16 bpp screen compatibility since
> > 15 bpp bitmaps do not exist.
>
> 15 bpp bitmaps do exist. According to the Feng Yuan's book that depends on
On 12/12/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Just to add that msdn states that
>
> "Direct3D 10 limits the use of assembly language to that of debugging
> purposes only, therefore any hand written assembly shaders used in
> Direct3D 9 will need to be converted to HLSL."
>
> http://
Just to add that msdn states that
"Direct3D 10 limits the use of assembly language to that of debugging
purposes only, therefore any hand written assembly shaders used in
Direct3D 9 will need to be converted to HLSL."
http://msdn2.microsoft.com/en-us/library/bb205073.aspx#Porting_Shaders
I think
Stefan Doesinger <[EMAIL PROTECTED]> wrote:
> This obsolettes the 15 bpp bitmap and 16 bpp screen compatibility since
> 15 bpp bitmaps do not exist.
15 bpp bitmaps do exist. According to the Feng Yuan's book that depends on
the driver and hardware.
--
Dmitry.
15 matches
Mail list logo