wine-bugs

wine-bugs@winehq.org

1 participants
158906 discussions

[Bug 455] - FIXMEs
by wine-bugs＠winehq.com 19 Jul '02

19 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=455 fgouget(a)codeweavers.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From fgouget(a)codeweavers.com 2002-07-19 02:52 ------- This meta-bug has been retired. The tasklist is now being kept track of by means of the 'tasklist' keyword. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=455>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 885] - Screen Corruption in riven
by wine-bugs＠winehq.com 19 Jul '02

19 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=885 ------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-19 02:50 ------- Created an attachment (id=235) Horribly hacked solution that masks the problem (patch) DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=885>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 845] - gcc Remote debugging
by wine-bugs＠winehq.com 19 Jul '02

19 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=845 ------- Additional Comments From fgouget(a)codeweavers.com 2002-07-19 02:42 ------- Some new developments: * 2002/07/10 - Eric Pouech - [Fwd: WineDbg: adding a GDB remote proxy (part I)] http://www.winehq.com/hypermail/wine-patches/2002/07/0088.html * 2002/07/09 - Eric Pouech - WineDbg: adding a GDB remote proxy (part II) http://www.winehq.com/hypermail/wine-patches/2002/07/0081.html DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=845>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 885] - Screen Corruption in riven
by wine-bugs＠winehq.com 19 Jul '02

19 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=885 ------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-18 23:30 ------- It's a timing problem, it seems that when the source and destination are the same the screen is not updated properly before the next bitblt. I found this out by putting a FIXME in a for loop. I wanted to slow this down so I could see the problem as it progressed. What it did is clear the problem up. .... physDevDst->exposures++; wine_tsx11_unlock(); if (physDevDst == physDevSrc){ INT q; for(q=1;q<1000 q++){ FIXME("Same Source; } } return TRUE; .... DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=885>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 885] - Screen Corruption in riven
by wine-bugs＠winehq.com 19 Jul '02

19 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=885 ------- Additional Comments From dclark(a)akamail.com 2002-07-18 22:56 ------- Yep, it looks like that for me. I added a trace to check the parameters to XCopyArea, and they look ok. case SRCCOPY: /* 0xcc */ if (dcSrc->bitsPerPixel == dcDst->bitsPerPixel) { TRACE(" src_xy=%d,%d size=%d,%d dst_xy=%d,%d\n", physDevSrc->org.x + visRectSrc.left, physDevSrc->org.y + visRectSrc.top, width, height, physDevDst->org.x + visRectDst.left, physDevDst->org.y + visRectDst.top ); I think what is happening is that the first bitblt is doing the scroll on an internal image. trace:bitblt:BitBlt hdcSrc=08dc 38,0 24 bpp->hdcDest=08dc 0,0 570x392x24 rop=cc0020 ... trace:bitblt:BITBLT_InternalStretchBlt src_xy=38,0 size=570,392 dst_xy=0,0 And then the second copies the entire image to the screen trace:bitblt:StretchBlt 08dc 0,0 608x392x24 -> 0894 0,0 608x392x24 rop=cc0020 ... trace:bitmap:X11DRV_DIB_SetImageBits XPutImage(44041069,0x8079818,0x80b3ec0,0,0,0,0,608,436) ... trace:bitblt:BITBLT_InternalStretchBlt src_xy=0,0 size=608,392 dst_xy=16,22 The dst_xy on this second one is offset to accomodate the frame (I think). DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=885>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 885] - Screen Corruption in riven
by wine-bugs＠winehq.com 19 Jul '02

19 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=885 ------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-18 19:47 ------- Well I've tracked it down to this code snippet case SRCCOPY: /* 0xcc */ if (dcSrc->bitsPerPixel == dcDst->bitsPerPixel) { wine_tsx11_lock(); XSetFunction( gdi_display, physDevDst->gc, GXcopy ); XCopyArea( gdi_display, physDevSrc->drawable, physDevDst->drawable, physDevDst->gc, physDevSrc->org.x + visRectSrc.left, physDevSrc->org.y + visRectSrc.top, width, height, physDevDst->org.x + visRectDst.left, physDevDst->org.y + visRectDst.top ); physDevDst->exposures++; wine_tsx11_unlock(); return TRUE; } In each case it goes into this code. (XCopyArea is not a wine function) can you confirm? DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=885>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 502] - Convert HTASK to a void* (references: 17)
by wine-bugs＠winehq.com 18 Jul '02

18 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=502 ------- Additional Comments From mstefani(a)redhat.com 2002-07-18 18:11 ------- Patch sent to wine-patches. I would assign this bug to me, but it seems I can't do it. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=502>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 885] - Screen Corruption in riven
by wine-bugs＠winehq.com 18 Jul '02

18 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=885 ------- Additional Comments From dclark(a)akamail.com 2002-07-18 17:48 ------- Yep, that was a click on the right. And of course there is a series of quick scrolls of various sizes, corresponding to the various sized pieces left on the right side causing the screen corruption. trace:scroll:X11DRV_ScrollDC 08dc -181,0 hrgnUpdate=0000 rcUpdate = (nil) trace:scroll:X11DRV_ScrollDC 08dc -81,0 hrgnUpdate=0000 rcUpdate = (nil) trace:scroll:X11DRV_ScrollDC 08dc -81,0 hrgnUpdate=0000 rcUpdate = (nil) trace:scroll:X11DRV_ScrollDC 08dc -82,0 hrgnUpdate=0000 rcUpdate = (nil) trace:scroll:X11DRV_ScrollDC 08dc -60,0 hrgnUpdate=0000 rcUpdate = (nil) I think 24 bits is only because that is what my video card is set for, so that is what wine is using. Riven itself is only 8 bit color, as I recall. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=885>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 882] - Alpha Centauri: Text does not show in the main screen menu
by wine-bugs＠winehq.com 18 Jul '02

18 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=882 ------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-18 17:30 ------- My profuse appologies for my spelling. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=882>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 882] - Alpha Centauri: Text does not show in the main screen menu
by wine-bugs＠winehq.com 18 Jul '02

18 Jul '02

http://bugs.winehq.com/show_bug.cgi?id=882 ------- Additional Comments From andi(a)rhlx01.fht-esslingen.de 2002-07-18 16:38 ------- It's NOT pallet ! For some reason I hate it when people can't spell palette properly (and thus even mention a non-existing debugmsg at the same time). (that's quite appallETing, to be exact :-) DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=882>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs