http://bugs.winehq.com/show_bug.cgi?id=641
*** shadow/641 Fri May 3 04:28:26 2002
--- shadow/641.tmp.17739 Fri May 3 04:30:58 2002
***************
*** 31,33 ****
--- 31,37 ----
Grahic-subsys is a NVidia GeForce 2 MX400, Nvidia drivers 2802, XFree 4.0.3.
Feel free to contact me for further information.
+
+ ------- Additional Comments From o.lemke(a)tu-bs.de 2002-05-03 04:30 -------
+ Created an attachment (id=79)
+ Logfile created with --debugmsg +relay,+ddraw
http://bugs.winehq.com/show_bug.cgi?id=640
*** shadow/640 Thu May 2 23:37:11 2002
--- shadow/640.tmp.5797 Thu May 2 23:38:40 2002
***************
*** 29,31 ****
--- 29,35 ----
(chris(a)luethy.net). This issue has been in Wine for a very long time, and even
Wine branches like the Crossover plugin and the Transgaming wine exhibit this
issue. But mostly, I'd like to see it fixed in the offical wine at winehq.com
+
+ ------- Additional Comments From chris(a)luethy.net 2002-05-02 23:38 -------
+ Created an attachment (id=78)
+ A picture of the graphic error
http://bugs.winehq.com/show_bug.cgi?id=640
*** shadow/640 Thu May 2 23:37:11 2002
--- shadow/640.tmp.5727 Thu May 2 23:37:11 2002
***************
*** 0 ****
--- 1,31 ----
+ +============================================================================+
+ | Major graphic glitch in x11drv |
+ +----------------------------------------------------------------------------+
+ | Bug #: 640 Product: Wine |
+ | Status: UNCONFIRMED Version: 20020411 |
+ | Resolution: Platform: |
+ | Severity: normal OS/Version: All |
+ | Priority: P1 Component: wine-gui |
+ +----------------------------------------------------------------------------+
+ | Assigned To: wine-bugs(a)winehq.com |
+ | Reported By: chris(a)luethy.net |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | Milestone: TargetMilestone: --- |
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ When dragging unresizeable windows (like the Winamp preferences dialog), the
+ outline of the old window is left behind and begins to draw white lines all over
+ the screen. Also, if you drag that window off the screen, you being to receieve
+ black lines from the upper left corner on the screen.
+
+ I've posted a screenshot online to show you what I mean (all the white lines are
+ from Wine, from dragging around the Winamp preferences dialog):
+
+ http://chris.luethy.net/wine/image.jpg
+
+ I'm willing to provide whatever additional information is required
+ (chris(a)luethy.net). This issue has been in Wine for a very long time, and even
+ Wine branches like the Crossover plugin and the Transgaming wine exhibit this
+ issue. But mostly, I'd like to see it fixed in the offical wine at winehq.com
\ No newline at end of file
http://bugs.codeweavers.com/show_bug.cgi?id=638
*** shadow/638 Thu May 2 14:29:26 2002
--- shadow/638.tmp.10913 Thu May 2 14:29:26 2002
***************
*** 0 ****
--- 1,36 ----
+ +============================================================================+
+ | Document Wine debugging channels |
+ +----------------------------------------------------------------------------+
+ | Bug #: 638 Product: Wine |
+ | Status: UNCONFIRMED Version: unspecified |
+ | Resolution: Platform: |
+ | Severity: normal OS/Version: All |
+ | Priority: P1 Component: wine-documentation |
+ +----------------------------------------------------------------------------+
+ | Assigned To: wine-bugs(a)winehq.com |
+ | Reported By: apa3a(a)yahoo.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | Milestone: TargetMilestone: --- |
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ Write description of the debugging channels to documentation/running.sgml.
+ This is pretty easy to do - search the .c files for macros
+ WINE_DEFAULT_DEBUG_CHANNEL and WINE_DECLARE_DEBUG_CHANNEL. Some files declare
+ a few channels. E.g. file loader/module.c has following declarations:
+
+ WINE_DEFAULT_DEBUG_CHANNEL(module);
+ WINE_DECLARE_DEBUG_CHANNEL(win32);
+ WINE_DECLARE_DEBUG_CHANNEL(loaddll);
+
+ Knowing modules where the channels used and looking how these channels
+ used in the modules you can get an idea what kind of debugging information
+ these channels propagate.
+ Some information from documentation/configuring.sgml can help you. As usual
+ google and msdn.microsoft.com are also your best friends in this (well, probably
+ not the latter ;-).
+
+ Please, update list of channels if you find a new one. Note, besides file
+ documentation/running.sgml the debugging channels are listed in
+ documentation/wine.man.in.
\ No newline at end of file