http://bugs.winehq.com/show_bug.cgi?id=561
*** shadow/561 Thu May 23 14:55:08 2002
--- shadow/561.tmp.28068 Sat May 25 15:47:37 2002
***************
*** 42,44 ****
--- 42,48 ----
Could you get a relay trace as described here:
http://www.winehq.org/Docs/wine-user/bugs.shtml
Please, attach the archived relay trace to the bug report.
+
+ ------- Additional Comments From roz(a)one.net 2002-05-25 15:47 -------
+ Created an attachment (id=131)
+ 100 line relay trace
http://bugs.winehq.com/show_bug.cgi?id=616
*** shadow/616 Sat May 25 15:03:09 2002
--- shadow/616.tmp.25959 Sat May 25 15:11:02 2002
***************
*** 2,8 ****
| keyboard input not working in warcraft II |
+----------------------------------------------------------------------------+
| Bug #: 616 Product: Wine |
! | Status: UNCONFIRMED Version: 20020411 |
| Resolution: Platform: |
| Severity: normal OS/Version: All |
| Priority: P1 Component: wine-directx |
--- 2,8 ----
| keyboard input not working in warcraft II |
+----------------------------------------------------------------------------+
| Bug #: 616 Product: Wine |
! | Status: RESOLVED Version: 20020411 |
| Resolution: Platform: |
| Severity: normal OS/Version: All |
| Priority: P1 Component: wine-directx |
***************
*** 144,146 ****
--- 144,169 ----
+ if (!other) change_queue_bits( queue, 0, clr_bit );
+ break;
+ }
+
+
+ ------- Additional Comments From Speeddymon(a)yahoo.com 2002-05-25 15:11 -------
+ sigh myself, i didn't read to the bottom before making that last post! oops...
+ more than likely, it is just the fact that warcraft2 needs to be able to grab
+ the input devices via directx, since that patch. before it didn't matter
+ because the way that input messages were being handled, everything got through,
+ but now, dxgrab is needed for warcraft to recognize the keyboard.... i think
+ that your best bet would be to leave dxgrab to n in the x11drv section and
+ create an appdefaults section at the bottom like this:
+
+ [AppDefaults\\warcraft2.exe\\x11drv]
+ "DXGrab" = "N"
+
+ where the warcraft2.exe in the [] is the actual name of your warcraft2
+ executable.
+
+ thanks for the bug report though, and im glad that i was able to help you. if
+ you ever think you have found a bug, dont hesitate to post it here, we are
+ always glad to be rid of them, and if it turns out to not be one, oh well, at
+ least we got another satisfied user! ;)
+
+ -Dustin
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=616
*** shadow/616 Sat May 25 14:05:50 2002
--- shadow/616.tmp.25531 Sat May 25 15:03:09 2002
***************
*** 121,123 ****
--- 121,146 ----
*sigh* Sorry I should've check this before.
Does this imply a configuration error or a wine bug?
+
+ ------- Additional Comments From Speeddymon(a)yahoo.com 2002-05-25 15:03 -------
+ something i noticed in the patch, dont know if it has anything to do with the
+ problem, but where is the default case in this statement?! ;)
+
+ + switch(kind)
+ + {
+ + case SEND_MESSAGE:
+ + if (!queue->msg_list[kind].first) change_queue_bits( queue, 0,
+ QS_SENDMESSAGE );
+ + break;
+ + case POST_MESSAGE:
+ + if (!queue->msg_list[kind].first) change_queue_bits( queue, 0,
+ QS_POSTMESSAGE );
+ + break;
+ + case COOKED_HW_MESSAGE:
+ + case RAW_HW_MESSAGE:
+ + clr_bit = get_hardware_msg_bit( msg );
+ + for (other = queue->msg_list[kind].first; other; other = other->next)
+ + if (get_hardware_msg_bit( other ) == clr_bit) break;
+ + if (!other) change_queue_bits( queue, 0, clr_bit );
+ + break;
+ + }
http://bugs.winehq.com/show_bug.cgi?id=729
*** shadow/729 Sat May 25 12:26:13 2002
--- shadow/729.tmp.25066 Sat May 25 14:56:18 2002
***************
*** 31,33 ****
--- 31,41 ----
------- Additional Comments From dragon_sdc(a)hotmail.com 2002-05-25 12:26 -------
Created an attachment (id=130)
A snapshot of the problem - no need to email me now :-)
+
+
+ ------- Additional Comments From Speeddymon(a)yahoo.com 2002-05-25 14:56 -------
+ could it at all be the skin? try it in windows with that same skin just to
+ make sure, i have had problems like that depending on the skin i was using...
+
+ if it doesn't display the problem in windows, try it in linux with the default
+ winamp skin, and let us know what happens..
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=720
*** shadow/720 Sat May 25 09:26:01 2002
--- shadow/720.tmp.24742 Sat May 25 14:51:45 2002
***************
*** 67,69 ****
--- 67,76 ----
Regards
Massimo
+
+ ------- Additional Comments From Speeddymon(a)yahoo.com 2002-05-25 14:51 -------
+ sounds to me like it isn't getting the coordinates of the drawing correctly,
+ and therefore redrawing it incorrectly...
+
+ could you attach those same 3 screenshots except done in windows (so that the
+ error isn't there)?
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=640
*** shadow/640 Fri May 24 21:27:38 2002
--- shadow/640.tmp.24534 Sat May 25 14:48:17 2002
***************
*** 120,122 ****
--- 120,128 ----
Okay, I added the 1.log file as an attachment to this bug. Hope it helps. I just
ran Winamp like you said, opened the Perferences dialog box, dragged it around a
little, then closed Winamp.
+
+ ------- Additional Comments From Speeddymon(a)yahoo.com 2002-05-25 14:48 -------
+ thanks, that should help find the source of the problem, anyone else need any
+ debug output messages? as for my copy of the log, i didnt get a chance to make
+ it last night or today before i left my house, so it will have to wait until
+ tomorrow or monday
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=469
*** shadow/469 Fri May 24 13:45:20 2002
--- shadow/469.tmp.23990 Sat May 25 14:33:39 2002
***************
*** 140,142 ****
--- 140,235 ----
What is your OS/distribution?
Can this application be freely accessed (probably demo/trial version)? If yes,
please describe how to reproduce the issue.
+
+ ------- Additional Comments From sbuehne(a)web.de 2002-05-25 14:33 -------
+ Hi Anryi,
+ I did some tests on the CVS tree as you suggested. I builded up the complete CVS
+ tree and went back to the 31st of July. As expected the application worked with
+ this wine build. Going forward I could identify the last working wine version
+ which is from August, 20th 2001.
+
+ In the diffs for the wine build for the 21st August the follwing
+ changes are listed:
+
+ 2001-08-21 Alexandre Julliard <julliard(a)winehq.com>
+ +
+ +
+ * windows/painting.c, windows/win.c, windows/winpos.c,
+ +
+ dlls/x11drv/winpos.c, include/win.h:
+ +
+ Removed WIN_GetDesktop().
+ +
+ +
+ * win32/console.c, windows/multimon.c, windows/x11drv/clipboard.c,
+ +
+ debugger/break.c, debugger/editline.c, debugger/msc.c,
+ +
+ dlls/msacm/msacm32_main.c, dlls/ole32/ole2.c, dlls/shell32/systray.c,
+ +
+ dlls/user/dde/server.c, dlls/winmm/driver.c, dlls/winmm/mci.c,
+ +
+ dlls/winmm/mmio.c, dlls/winmm/wineoss/mmaux.c,
+ +
+ documentation/debugger.sgml, msdos/int2f.c:
+ +
+ Francois Gouget <fgouget(a)free.fr>
+ +
+ Documentation updates (mainly thru vs. through).
+ +
+ +
+ * dlls/comctl32/listview.c:
+ +
+ Gerard Patel <gerard.patel(a)nerim.net>
+ +
+ Rect returned by LISTVIEW_GetItemRect should be total size in report
+ +
+ mode.
+ +
+ +
+ * graphics/x11drv/bitmap.c:
+ +
+ Gerard Patel <gerard.patel(a)nerim.net>
+ +
+ Default bitmap is not subject to reference counting.
+ +
+ +
+ * dlls/oleaut32/olepicture.c, dlls/oleaut32/typelib.c,
+ +
+ dlls/oleaut32/variant.c, include/oleauto.h, include/wine/obj_oleaut.h:
+ +
+ Francois Gouget <fgouget(a)free.fr>
+ +
+ Add the decVal field to VARIANT.
+ +
+ Fix the VARIANT C layout, i.e. the union/struct names/nesting.
+ +
+ Encapsulate all accesses to VARIANT types with the V_VT and V_UNION
+ +
+ macros.
+ +
+ +
+ * server/serial.c:
+ +
+ Mike McCormack <mike_mccormack(a)start.com.au>
+ +
+ Unconditionally set O_NONBLOCK when opening.
+
+ I have tested to undo the change to the serial.c modul.
+ So I removed this line from the wine build of 24th of August 2001 on my machine
+ and compiled wine without this modification. But the application is still
+ failing. So the modification to the serial.c modul does not seem to be the cause
+ of the problem.
+
+ To your other questions:
+ Also the current wine version do not work. I'm still using the old stuff.
+ The application is free available, because it is a monitoring program to a SOLAR
+ equipment, which is installed on the roof. This application reads from a serial
+ port the current status of this equipment.
+
+ My OS is a SuSE Distribution 7.3. The current kernel version is 2.4.18
+
+
+ Regards
+
+ Stephan
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=151
*** shadow/151 Sat May 25 14:12:56 2002
--- shadow/151.tmp.23045 Sat May 25 14:12:56 2002
***************
*** 0 ****
--- 1,61 ----
+ +============================================================================+
+ | dialog focus handling is not correct (e.g. in installers) |
+ +----------------------------------------------------------------------------+
+ | Bug #: 151 Product: Wine |
+ | Status: NEW Version: unspecified |
+ | Resolution: Platform: |
+ | Severity: normal OS/Version: All |
+ | Priority: P1 Component: wine-user |
+ +----------------------------------------------------------------------------+
+ | Assigned To: wine-bugs(a)winehq.com |
+ | Reported By: andi(a)rhlx01.fht-esslingen.de |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | Milestone: TargetMilestone: --- |
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ Many installers seem to have problems with their initial dialog
+ (no focus, ...)
+
+ Roger Wilco's configuration wizard (property sheet imitation)
+ doesn't have a focus at all.
+ this configuration wizard has one dialog (cancel, back, next button, main area)
+ encapsulating
+ *another* dialog. This seems to get messed up somehow, and we end up with no
+ focus at all.
+ The key area to that clearly is the focus handling after WM_INITDIALOG in
+ DIALOG_CreateIndirect().
+ Note that Roger Wilco always returns FALSE for a WM_INITDIALOG, indicating its
+ own focus
+ handling (which it obviously doesn't do).
+ Thus Wine jumps in and messes it up :)
+
+ Oh well, after having spent some hours on this without a real solution (i.e. one
+ that doesn't just look
+ perfect in *this* case, but apart from that busts any other program out there),
+ I think I'll just submit
+ Roger Wilco as one "problem case".
+
+ If you get hold of some installer that has focus problems or other programs,
+ then add them here please
+ in order to have a real collection of problem cases.
+
+ ------- Additional Comments From andi(a)rhlx01.fht-esslingen.de 2001-01-04 15:22 -------
+ Created an attachment (id=15)
+ Roger Wilco (version Mark Ic, 430kb)
+
+
+ ------- Additional Comments From andi(a)rhlx01.fht-esslingen.de 2002-05-25 14:12 -------
+ Also, many installers have e.g. their "license agreement" text completely selected
+ (blue selection), which is wrong.
+ This happens because in DEFDLG_SetFocus, we select the whole edit control text
+ in case WM_GETDLGCODE returned DLGC_HASSETSEL, which is the default of any edit
+ control (see controls/edit.c/WM_GETDLGCODE; if you want to get rid of this flag,
+ you even have to explicitly subclass the edit control, according to MSDN !).
+ Thus both DLGC_HASSETSEL and DEFDLG_SetFocus aren't wrong, it seems,
+ but instead the edit control of the dialog should not have the focus in the
+ first place (instead it should probably be one of its buttons).
+ Somehow our criteria for selecting initial dialog focus seems to be wrong.
+ Experienced with the installer for WinMX 3.10, second license dialog
+ (huh, why have they got two !? :-).
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=616
*** shadow/616 Sat May 25 12:58:07 2002
--- shadow/616.tmp.22713 Sat May 25 14:05:50 2002
***************
*** 112,114 ****
--- 112,123 ----
> 1.74 +101 -196 wine/windows/queue.c
I will try the different wine options now.
+
+
+ ------- Additional Comments From sean(a)mess.org 2002-05-25 14:05 -------
+ I found that after trying some options, with the DXGrab option set to 'Y', all
+ works fine!
+
+ *sigh* Sorry I should've check this before.
+
+ Does this imply a configuration error or a wine bug?
\ No newline at end of file