http://bugs.winehq.com/show_bug.cgi?id=831
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-06-29 23:14 -------
I've looked at the documentation/debugger.sgml and I was wondering where to put
this. Do we want it right at the end of the WineDbg Command Reference?
http://www.winehq.org/Docs/wine-devel/dbg-commands.shtml
I guess it would be a good idea to put a blurb after the note about this right
at the begining of the debug logging section of documentation/debuging.sgml
http://www.winehq.org/Docs/wine-devel/debugging.shtml
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=831>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=395
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |832
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=395>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=455
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |829
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.
http://bugs.winehq.com/show_bug.cgi?id=831
Summary: Document the new trace-related winedbg commands
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-documentation
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: fgouget(a)codeweavers.com
(I was bout to enter a bug for this but it's been implemented already ;-)
It is now possible to enable/disable traces from the debugger interface.
-> update the documentation
See the following URL for more information:
http://www.winehq.com/hypermail/wine-devel/2002/05/0818.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=831>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=829
apa3a(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|wine-bugs(a)winehq.com |lionel.ulmer(a)free.fr
------- Additional Comments From apa3a(a)yahoo.com 2002-06-28 14:57 -------
Forwarding to Lionel.
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=829>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=829
Summary: DIB_DirectDrawSurface_Blt does not properly support
DDBLT_WAIT
Product: Wine
Version: CVS
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: tony_lambregts(a)telusplanet.net
After playing around with SimCity 3000 some more I found that
DIB_DirectDrawSurface_Blt does not properly support DDBLT_WAIT. What wine
currently does is ignore the flag completely which in most cases is ok. The
problem shows up in SimCity when you click on the top half of the playing surface.
Because DDBLT_WAIT is not supported it makes a compleate mess of the screen.
By doing some serious debuging and a little searching of MSDN I found out what
the program expects to happen. All calls with the DDBLT_WAIT flag set are
supposed to be stored untill DIB_DirectDrawSurface_Blt is called without the
flag set. From what I can tell these requests should be processed in the reverse
order that they were submitted.
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=829>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 13:33 -------
Jason, I wonder if you can reproduce the issue with even smaller test case -
when the dialog has only "Cancel" button.
BTW, <Esc> button works - it dismisses the dialog.
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=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
apa3a(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Launched window treated as |Window in modal mode does
|child window |not receive mouse and
| |keyboard input
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 13:28 -------
It looks like the problem is even bigger - the modal dialog can't be accessed
with mouse, moved, does not receive keyboard input.
This bug may affect many VB applications
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=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
------- Additional Comments From us(a)the-edmeades.demon.co.uk 2002-06-27 12:21 -------
Testcase uploaded
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=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.