"Dmitry Timoshkov" <[EMAIL PROTECTED]> writes:
> Wine ought to be able to handle images larger than 32767x32767, that's not
> a Wine requirement, that's what applications written for win32 API expect
> to see working. There is no way to make it work without DIB engine if X11
> doesn't support it d
<[EMAIL PROTECTED]> wrote:
> http://www.x.org/pub/X11R6.8.2/patches/xorg-CAN-2005-2495.patch -
>
> +if (stuff->width > 32767 || stuff->height > 32767)
> +{
> +/* It is allowed to try and allocate a pixmap which is larger than
> + * 32767 in either dimension. However, all of the framebuffe
Thursday, November 10, 2005, 2:59:02 PM, Robert Shearman wrote:
> [EMAIL PROTECTED] wrote:
>> It seems to be that WinRAR crashes after calling:
>> ImageList_Create(16,16,ILC_COLOR32|ILC_MASK,256,2048)
>> to create the list of icons for ListView control. Wine translates
>> this ImageList_Create to
Robert Shearman schrieb:
> [EMAIL PROTECTED] wrote:
>
>> It seems to be that WinRAR crashes after calling:
>> ImageList_Create(16,16,ILC_COLOR32|ILC_MASK,256,2048)
>> to create the list of icons for ListView control. Wine translates
>> this ImageList_Create to CreateBitmapIndirect 36864x16 and the
[EMAIL PROTECTED] wrote:
It seems to be that WinRAR crashes after calling:
ImageList_Create(16,16,ILC_COLOR32|ILC_MASK,256,2048)
to create the list of icons for ListView control. Wine translates
this ImageList_Create to CreateBitmapIndirect 36864x16 and then
cannot handle 36864 parameter. If it
On Thu, 10 Nov 2005 06:02:57 +0100, Dustin Navea <[EMAIL PROTECTED]>
wrote:
x.org
Seems there are multiple issues here. First the x.org bug was big and ugly
so the rather simplistic patch was put through until what looks like some
sloppy coding in the rest of X gets cleaned up.
http:/
Yes, we are talking about the same thing, it is due to a bug in X that
was fixed. The X fix broke wine, causing that error to come up, so we
are now trying to figure out how to get around it or get X fixed without
breaking wine.
Christian Lachner wrote:
Hmm, i thought you were talking about t
On Thu, 10 Nov 2005 06:02:57 +0100, Dustin Navea <[EMAIL PROTECTED]>
wrote:
Well, I was thinking that since we really dont want to mess with Xorg
security fixes, maybe there is some sort of a workaround that could be
written into wine? I dunno, perhaps a temporary dirty hack to fix it
un
Well, I was thinking that since we really dont want to mess with Xorg
security fixes, maybe there is some sort of a workaround that could be
written into wine? I dunno, perhaps a temporary dirty hack to fix it
until Xorg fixes X again?
Unless there isnt any way to work around it of course, an
Hmm, i thought you were talking about the BadAlloc-Problem and i
noticed that audiograbber does not start because of that. Did i
misunderstand something? I'm not a dev so i don't understand your fix...
ciao chrisOn 11/9/05, Marcus Meissner <[EMAIL PROTECTED]> wrote:
On Wed, Nov 09, 2005 at 04:24:4
On Wed, Nov 09, 2005 at 04:24:43PM +0100, Christian Lachner wrote:
> Also got that Problem with Audiograbber... Other programs are surely also
> affected by this problem
>
> On 11/9/05, Dustin Navea <[EMAIL PROTECTED]> wrote:
> >
> > Can I get someone to take a look at
> > http://bugs.winehq.org/s
Also got that Problem with Audiograbber... Other programs are surely also affected by this problemOn 11/9/05, Dustin Navea <
[EMAIL PROTECTED]> wrote:Can I get someone to take a look at
http://bugs.winehq.org/show_bug.cgi?id=3573 ? This seems to affect only users of Xorg, and it seems to affect a
Can I get someone to take a look at
http://bugs.winehq.org/show_bug.cgi?id=3573 ? This seems to affect only
users of Xorg, and it seems to affect all of them, in multiple
different programs..
Dustin
13 matches
Mail list logo