correct from address
-- Forwarded message --
From: Gert van den Berg
On Sat, Jan 30, 2010 at 15:58, Gerold Jens Wucherpfennig
wrote:
> BTW I've done some cabinet.dll stuff some years ago.
> Can anybody give me a hint to some easy-to-understand data compression
> documentation?
>
On Fri, Feb 5, 2010 at 9:54 AM, Vincent Povirk
wrote:
> It's supported 32bpp with transparency from the start. The full list
> of supported writing formats is here:
> http://source.winehq.org/source/dlls/windowscodecs/pngformat.c#L680
>
> GUID_WICPixelFormat32bppBGRA is the format you want, I thin
An idea that popped into my head when I was thinking about a Quartz (OS X)
driver that perhaps there could be separate drivers for Quartz (OS X) and X11.
Such drivers would include OpenGL and DirectX "Drivers".
The patch is a copy/paste from the file d3d9/verdeclaration.c. So this file
should be simplified too, if we simplify the d3dx9_36/mesh.c implementation.
Obviously, to compute the size of the vertex, we can use D3DXGetDeclVertexSize,
but we gain very few.
So, what do you think about this?
A+
D
Reece Dunn wrote:
> And in terms of a fix, what is the best approach for fixing the issue?
> That is, Alexandre does not like an explicit call to InvalidateRect in
> the WM_MDICREATE handler, so I assume that the repaint logic should be
> done in a more specific place or figure out why it is not
Gerold Jens Wucherpfennig wrote:
>
> Hi, I've donated some bucks to winehq by PayPal and want to spend more...
> Can I decide for which things will be spend?
> When donating money, how much of it will go to PayPal?
> Is there a better way than using PayPal (by the donate link of the
> winehq front
I wanted to experiment with these, but I'm not sure of their current
state. Do they still apply cleanly? Are they on track for eventual
inclusion? I'm willing to help provide community testing by putting
them in a special package repository.
Thanks,
Scott Ritchie
--- On Fri, 5/2/10, Aric Stewart wrote:
> Scott Ritchie wrote:
> > My notes from Wineconf remind me that I need to create
> some manual links in the registry to whatever default CJK
> fonts are on the system. Can someone tell me what
> these are supposed to look like?
> >
> > Thanks,
> > Scott
On 02/05/2010 07:38 PM, Henri Verbeet wrote:
On 5 February 2010 19:10, Michael Stefaniuc wrote:
Henri Verbeet wrote:
min and max are already defined in windef.h. Note that they're not
safe for expressions with side-effects, but for simple expressions
like the one here they're ok.
We can lift
Hin-Tak Leung wrote:
--- On Fri, 5/2/10, Aric Stewart wrote:
Scott Ritchie wrote:
My notes from Wineconf remind me that I need to create
some manual links in the registry to whatever default CJK
fonts are on the system. Can someone tell me what
these are supposed to look like?
Thanks,
Scot
On 5 February 2010 19:10, Michael Stefaniuc wrote:
> Henri Verbeet wrote:
>> min and max are already defined in windef.h. Note that they're not
>> safe for expressions with side-effects, but for simple expressions
>> like the one here they're ok.
> We can lift the side-effects and type safe min/ma
Henri Verbeet wrote:
> On 5 February 2010 18:19, Matteo Bruni wrote:
>> Sure. Better to go with something like "len = len < (desc->size -
>> desc->pos) ? len : desc->size - desc->pos" or creating a "min"
>> function?
>>
> min and max are already defined in windef.h. Note that they're not
> safe fo
Scott Ritchie wrote:
My notes from Wineconf remind me that I need to create some manual links
in the registry to whatever default CJK fonts are on the system. Can
someone tell me what these are supposed to look like?
Thanks,
Scott Ritchie
Sure! (sorry for the delay)
The important keys ar
On 5 February 2010 18:19, Matteo Bruni wrote:
> Sure. Better to go with something like "len = len < (desc->size -
> desc->pos) ? len : desc->size - desc->pos" or creating a "min"
> function?
>
min and max are already defined in windef.h. Note that they're not
safe for expressions with side-effects
Seems like I'm unable to review my code...
>
>> + if(desc->pos + len > desc->size) len = desc->size - desc->pos;
> It's usually safer to write expressions like that as "if (len >
> desc->size - desc->pos)" because "desc->pos + len" can wrap around if
> len is large, while "desc->size - desc->po
Susan Cragin writes:
> What's up with the git repository?
> I do the following:
>
> git pull
> sudo make uninstall
> ./configure --enable-win64 && make distclean
> ./configure --enable-win64 && make depend && make
>
> and I get the following:
>
> warning: System 16: missing glyph for char f8c8
>
>Susan Cragin wrote:
>> ./configure --enable-win64 && make distclean
>> ./configure --enable-win64 && make depend && make
>Huh? Are you actually trying to build the 64-bit version of Wine? Why
>would you want to do that? Especially when 64-bit Wine isn't mature yet.
>
>Did you try it without --enab
On 2010-02-02 (February, Tuesday) 15:00:01 wine-devel-requ...@winehq.org wrote:
> Your membership in the mailing list wine-devel has been disabled due
> to excessive bounces The last bounce received from you was dated
> 26-Jan-2010. You will not get any more messages from this list until
> you re-
Hi,
I have been looking at http://bugs.winehq.org/show_bug.cgi?id=14312
which shows up as the MDI client window not being repainted properly
when a new child is created given an already maximised child window
being present.
There is a related issue here that sometimes the child window frames
are
Susan Cragin wrote:
> ./configure --enable-win64 && make distclean
> ./configure --enable-win64 && make depend && make
Huh? Are you actually trying to build the 64-bit version of Wine? Why
would you want to do that? Especially when 64-bit Wine isn't mature yet.
Did you try it without --enable-win6
What's up with the git repository?
I do the following:
git pull
sudo make uninstall
./configure --enable-win64 && make distclean
./configure --enable-win64 && make depend && make
and I get the following:
warning: System 16: missing glyph for char f8c8
make[1]: *** No rule to make target `marlett
> I was looking in to the overall architectural issues but have not had
> the time to really hack on it recently. As far as I understand, the
> current png support in wine's windowscodecs does not support creation
> of a 32bpp image with transparency, unless I missed some commit
> messages or total
On 4 February 2010 19:26, Matteo Bruni wrote:
> +void wpp_write_message_var(const char *fmt, ...) PRINTF_ATTR(1,2);
> +void wpp_write_message_var(const char *fmt, ...)
You can just do the following:
+void PRINTF_ATTR(1,2) wpp_write_message_var(const char *fmt, ...)
> +desc = HeapAlloc(Get
Hello Alexandre,
Alexandre Julliard wrote:
Maarten Lankhorst writes:
---
Fix the definitions in winbase.h, and the inline assembly :)
There are still several problems with your assembly, and I don't
understand why you want to reinvent the wheel when we have a perfectly
fine interloc
On 5 February 2010 05:09, David Adam wrote:
> This patch is from Tony Wasserka. It comes from his git repertory. He
> authorized to pick up patches (see Wine-devel) to submit to Wine.
> I just cleanup it a little bit. I let Tony as the author of this patch. All
> the tests pass in a real Window
Maarten Lankhorst writes:
> ---
> Fix the definitions in winbase.h, and the inline assembly :)
There are still several problems with your assembly, and I don't
understand why you want to reinvent the wheel when we have a perfectly
fine interlocked_cmpxchg64 implementation already.
--
Alexandre
2010/2/4 Vincent Povirk
>
> > As a side note, you need to do a similar work on winemenubuilder, as it
> uses
> > libpng and fails linking without modifications. to test this images i
> > statically linked it to libpng, just to make it work, as it wasn't needed
> in
> > your test.
> > Thank you fo
2010/2/4 Vincent Povirk
>
> > * http://www.libpng.org/pub/png/PngSuite/basn4a16.png - This is a
> > grayscale png with an alpha channel. That's the situation where we use
> > the png_set_gray... function that was removed.
>
> Errr.. I may actually be thinking of
> http://www.libpng.org/pub/png/Pn
28 matches
Mail list logo
