wine-devel January 2003

wine-devel@winehq.org

151 participants
377 discussions

Re: Window menu
by Tony Lambregts 07 Jan '03

07 Jan '03

Duane Clark wrote: > I've been using this patch for about a year and a half now, so I might > as well just submit it. > > Changelog: > A window with a WS_EX_APPWINDOW extended style can also > get a menu. > It's about time then.<g> I have been using it since you sent it to me. Works great! -- Tony Lambregts

1 0

RDP client under Wine?
by Hetz Ben Hamo 07 Jan '03

07 Jan '03

Hi, A friend of mine needs to connect to MS Terminal server through his linux machines. There seems to be 3 options: 1. rdesktop - it runs, but only 8 bit colors and it's pretty slow (on 10MBit LAN) 2. WinConnect for Linux - costs a fortune - $79. 3. MS RDP client through wine - it runs up to the point where you actually connect, and then it dies.. Regarding option 3 - anyone managed to make it run somehow? any tips would be welcome... Thanks, Hetz

4 5

Re: console handling
by Dimitrie O. Paun 06 Jan '03

06 Jan '03

On January 4, 2003 04:32 pm, Eric Pouech wrote: > this patch fixes a couple of issues in the console handling (but > shouldn't help Lionel & Sylvain with the issues they reported on wd) Hi Eric, Do you have any plans to reorganize wineconsole a bit so that you don't need allocate a bitmap as big as the entire buffer, but rather one as big as the displayed screen only? This way we can have 3000-5000 line scroll buffers (as I have in my konsole, rxvt, xterm, etc.) -- Dimi.

2 10

Wine debugging tutorial?
by Mike Hearn 06 Jan '03

06 Jan '03

The tutorial up on winehq.org on how to use WineDbg, while pretty useful, seems a tad out of date (lots of references to 16 bit constructs etc). Does anybody know of any good tutorials on how to use low level code debuggers such as this? Coming from a delphi background, I'm more used to the integrated debugging style, and I'm finding more and more that the wine traces don't always provide useful information, so I'd like to master this tool. Oh, also, how do you use the ncurses backend (I think eric mentioned one recently). I quite like having large scrollback buffers too. thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

2 1

Re: winegcc: behave like g++ when invoked as wineg++
by Dimitrie O. Paun 06 Jan '03

06 Jan '03

On January 5, 2003 11:47 pm, Dimitrie O. Paun wrote: > ChangeLog > Create a wineg++ akin to g++. Drop support for the abused -xc++ switched. Please don't use this patch, it's broken: I don't delete the link before creating it, so only the first install works. I'll send a bigger update soon. -- Dimi.

1 0

Re: but report -- the last line tell me do this
by Marcus Meissner 06 Jan '03

06 Jan '03

On Mon, Jan 06, 2003 at 06:39:36PM +0800, yf wrote: > [yf@yf 2002]$ wine ./hexin.exe > fixme:ole:CoRegisterMessageFilter stub > fixme:shdocvw:WBPCI2_GetGUID stub: dwGuidKind = 1, pGUID = {00000000-0000-0000-0000-000000000000} > fixme:shdocvw:WBPCI2_GetGUID Wrongly returning IPropertyNotifySink interface {9bfbbc02-eff1-101a-84ed-00aa00341d07} > fixme:shdocvw:WBQA_QuickActivate stub: QACONTAINER = 0x40760874, QACONTROL = 0x407608b4 > fixme:shdocvw:WBPSI_InitNew stub > fixme:shdocvw:WBCP_Advise stub: IUnknown = 0x4183bfe4, connection cookie = 0 > fixme:shdocvw:WBOOBJ_SetExtent stub: (0x41f0a940, 1, (0 x 0)) > fixme:shdocvw:WBOOBJ_DoVerb : stub iVerb = -5 > fixme:shdocvw:WBOOBJ_DoVerb stub for OLEIVERB_INPLACEACTIVATE > fixme:shdocvw:WBOC_GetControlInfo stub: LPCONTROLINFO = 0x4183bf84 > fixme:shdocvw:WBOIPO_GetWindow stub HWND* = 0x40760980 > fixme:shdocvw:WB_Invoke stub dispIdMember = -518, IID = {00000000-0000-0000-0000-000000000000} > fixme:shdocvw:WBCP_Unadvise stub: cookie to disconnect = 1099153244 > fixme:shdocvw:WBCP_Unadvise stub: cookie to disconnect = 1099153168 > fixme:shdocvw:WBCP_Unadvise stub: cookie to disconnect = 1 > fixme:shdocvw:WBOIPO_InPlaceDeactivate stub > fixme:shdocvw:WBOOBJ_SetClientSite stub: (0x41f0a940, (nil)) > fixme:shdocvw:WBOOBJ_Close stub: () I get as far, than it fscks up its double byte names. With what 'LANG' var do you run it? > err:clipping:CLIPPING_UpdateGCRegion hVisRgn is zero. Please report this. This will do an immediate exit(1); so WINE terminates here. It probably should not. Ciao, Marcus

1 0

looking for tester on NT
by Stefan Leichter 06 Jan '03

06 Jan '03

Hello, before Christmas i did some check on an NT4 system at work that leads to the attached tests. But currently i am not at work and have no windows system available. Can someone please build and run the attached tests on a windows system (NT4 prefered) and report the results. Thanks Stefan Index: configure.ac =================================================================== RCS file: /home/wine/wine/configure.ac,v retrieving revision 1.116 diff -u -r1.116 configure.ac --- configure.ac 4 Jan 2003 02:52:05 -0000 1.116 +++ configure.ac 5 Jan 2003 16:05:33 -0000 @@ -1472,6 +1472,7 @@ dlls/winsock/Makefile dlls/winsock/tests/Makefile dlls/winspool/Makefile +dlls/winspool/tests/Makefile dlls/wintab32/Makefile dlls/wintrust/Makefile dlls/wow32/Makefile Index: dlls/winspool/Makefile.in =================================================================== RCS file: /home/wine/wine/dlls/winspool/Makefile.in,v retrieving revision 1.22 diff -u -r1.22 Makefile.in --- dlls/winspool/Makefile.in 12 Nov 2002 02:22:24 -0000 1.22 +++ dlls/winspool/Makefile.in 5 Jan 2003 16:07:17 -0000 @@ -13,6 +13,8 @@ info.c \ wspool.c +SUBDIRS = tests + @MAKE_DLL_RULES@ ### Dependencies: --- /dev/null Mon Sep 24 03:54:15 2001 +++ dlls/winspool/tests/Makefile.in Sun Jan 5 16:56:25 2003 @@ -0,0 +1,13 @@ +TOPSRCDIR = @top_srcdir@ +TOPOBJDIR = ../../.. +SRCDIR = @srcdir@ +VPATH = @srcdir@ +TESTDLL = winspool.drv +IMPORTS = winspool kernel32 ntdll + +CTESTS = \ + info.c + +@MAKE_TEST_RULES@ + +### Dependencies: --- /dev/null Mon Sep 24 03:54:15 2001 +++ dlls/winspool/tests/info.c Sun Jan 5 18:45:34 2003 @@ -0,0 +1,57 @@ +#include "wine/test.h" +#include "winbase.h" +#include "winerror.h" +#include "winspool.h" + +static void test_printer_directory(ivoid) +{ LPBYTE buffer = NULL; + DWORD cbBuf, pcbNeeded; + BOOL res; + + (void) GetPrinterDriverDirectoryA( NULL, NULL, 1, NULL, 0, &cbBuf); + + buffer = HeapAlloc( GetProcessHeap(), 0, cbBuf*2); + + res = GetPrinterDriverDirectoryA(NULL, NULL, 1, buffer, cbBuf, &pcbNeeded); + ok( res, "expected result != 0, got %d", res); + ok( cbBuf == pcbNeeded, "pcbNeeded set to %ld instead of %ld", + pcbNeeded, cbBuf); + + res = GetPrinterDriverDirectoryA(NULL, NULL, 1, buffer, cbBuf*2, &pcbNeeded); + ok( res, "expected result != 0, got %d", res); + ok( cbBuf == pcbNeeded, "pcbNeeded set to %ld instead of %ld", + pcbNeeded, cbBuf); + + res = GetPrinterDriverDirectoryA( NULL, NULL, 1, buffer, cbBuf-1, &pcbNeeded); + ok( !res , "expected result == 0, got %d", res); + ok( cbBuf == pcbNeeded, "pcbNeeded set to %ld instead of %ld", + pcbNeeded, cbBuf); + ok( ERROR_INSUFFICIENT_BUFFER == GetLastError(), + "last error set to %ld instead of ERROR_INSUFFICIENT_BUFFER", + GetLastError()); + + res = GetPrinterDriverDirectoryA( NULL, NULL, 1, NULL, cbBuf, &pcbNeeded); + ok( !res , "expected result == 0, got %d", res); + ok( ERROR_INVALID_USER_BUFFER == GetLastError(), + "last error set to %ld instead of ERROR_INVALID_USER_BUFFER", + GetLastError()); + + res = GetPrinterDriverDirectoryA( NULL, NULL, 1, buffer, cbBuf, NULL); + ok( !res , "expected result == 0, got %d", res); + ok( RPC_X_NULL_REF_POINTER == GetLastError(), + "last error set to %ld instead of RPC_X_NULL_REF_POINTER", + GetLastError()); + + res = GetPrinterDriverDirectoryA( NULL, NULL, 1, NULL, cbBuf, NULL); + ok( !res , "expected result == 0, got %d", res); + ok( RPC_X_NULL_REF_POINTER == GetLastError(), + "last error set to %ld instead of RPC_X_NULL_REF_POINTER", + GetLastError()); + + HeapFree( GetProcessHeap(), 0, buffer); +} + +START_TEST(info) +{ + test_printer_directory(); +}

2 2

Symbol stripping?
by Mike Hearn 06 Jan '03

06 Jan '03

Confused again I'm afraid. Winedbg gives me a lot of "No debugging information" messages when I load it up, which makes sense because watching the diagnostic text flow past during a build I see lots of "strip --strip-unneeded" lines. The ChangeLog refers to adding this to save disk space, but the man page says "strip everything not needed for relocation processing". Doesn't this strip out debug info though, which is sort of useful for debugging? Am I configuring Wine wrongly? What's happening here? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

2 1

Re: Workaround for Wine to produce dead-keys with Brazilian ABNT-2 keyboards
by Mauro Carvalho Chehab - BrTurbo 06 Jan '03

06 Jan '03

Hi Rikki, My patch was designed to the brazilian ABNT-2 keyboard as a workaround. On these keyboards we have two deak keys and <shift> <6> that produces accented letters when followed by a vowel. It is also used in Brazil standard US keyboards and some simbols are mapped as dead keys ("´`~^). My patch doesn´t even fix this kind of keyboard. What my patch does is to force the xkb to proccess that keys as dead keys. Does your keyboard works correclty on X sessions (using a standard window manager - please notice that KDE has its own keyboard treatment routines)? Maybe it is a question of editing the /etc/X11/XFConfig to use your keymap. I suppose that the correct solution is to implement on keyboard.c a specific dead key replacement code, and having specific dead key tables for all keyboards, but it requires a major change that must be validated by other wine users. Cheers, Mauro Carvalho Chehab ----- Original Message ----- From: "Richard Allen" <ra(a)ra.is> To: "Mauro Carvalho Chehab" <mchehab(a)brturbo.com> Sent: Friday, January 03, 2003 12:39 PM Subject: Re: Workaround for Wine to produce dead-keys with Brazilian ABNT-2 keyboards > Hola ;) > > Im trying to get the Icelandic dead (accented) keys to work. > Your workaround did not do the trick, even tho the dead key on the IS > keyboard is key 48 (2 buttons to the right from the L key). > > In vanilla wine, the dead key gave me a Z, but once your patch is > applyed it does nothing :) (A improvement) ;) > > When I press the dead key I get: > > trace:key:X11DRV_KeyEvent state = 0 > trace:key:X11DRV_KeyEvent KeyPress : keysym=FE51 (dead_acute), ascii chars=1 / B4 / '´' > trace:key:X11DRV_KeyEvent keycode 0x30 converted to vkey 0xde > trace:key:X11DRV_KeyEvent bScan = 0x28. > trace:key:queue_kbd_event wParam=00de, lParam=00280001, InputKeyState=81 > trace:key:TranslateMessage (WM_KEYDOWN, 00DE, 00280001) > trace:key:TranslateMessage Translating key VK_OEM_7 (00de), scancode 28 > trace:keyboard:X11DRV_ToUnicode AltGrMask = 0000 > trace:key:X11DRV_ToUnicode (00DE, 0028) : faked state = 0 > trace:keyboard:X11DRV_ToUnicode Found keycode 48 (0x30) > trace:key:X11DRV_ToUnicode ToUnicode about to return -1 with char 17d > trace:key:TranslateMessage -1 -> PostMessage(WM_DEADCHAR) > trace:key:TranslateMessage (WM_DEADCHAR, 008E, 00280001) > trace:key:X11DRV_KeyEvent state = 0 > trace:key:X11DRV_KeyEvent KeyRelease : keysym=FE51 (dead_acute), ascii chars=1 / B4 / '´' > trace:key:X11DRV_KeyEvent keycode 0x30 converted to vkey 0xde > trace:key:X11DRV_KeyEvent bScan = 0x28. > trace:key:queue_kbd_event wParam=00de, lParam=c0280001, InputKeyState=1 > trace:key:TranslateMessage (WM_KEYUP, 00DE, C0280001) > > > > > > and then I press the "a" key and should get an "á": > > trace:key:X11DRV_KeyEvent state = 0 > trace:key:X11DRV_KeyEvent KeyPress : keysym=61 (a), ascii chars=1 / 61 / 'a' > trace:key:X11DRV_KeyEvent keycode 0x26 converted to vkey 0x41 > trace:key:X11DRV_KeyEvent bScan = 0x1e. > trace:key:queue_kbd_event wParam=0041, lParam=001e0001, InputKeyState=81 > trace:key:TranslateMessage (WM_KEYDOWN, 0041, 001E0001) > trace:key:TranslateMessage Translating key VK_A (0041), scancode 1e > trace:keyboard:X11DRV_ToUnicode AltGrMask = 0000 > trace:key:X11DRV_ToUnicode (0041, 001E) : faked state = 0 > trace:keyboard:X11DRV_ToUnicode Found keycode 38 (0x26) > trace:key:X11DRV_ToUnicode Translating char 0x61 from code page 28605 to unicode > trace:key:X11DRV_ToUnicode ToUnicode about to return 1 with char 61 > trace:key:TranslateMessage 1 -> PostMessage(WM_CHAR) > trace:key:TranslateMessage (WM_CHAR, 0061, 001E0001) > trace:key:X11DRV_KeyEvent state = 0 > trace:key:X11DRV_KeyEvent KeyRelease : keysym=61 (a), ascii chars=1 / 61 / 'a' > trace:key:X11DRV_KeyEvent keycode 0x26 converted to vkey 0x41 > trace:key:X11DRV_KeyEvent bScan = 0x1e. > trace:key:queue_kbd_event wParam=0041, lParam=c01e0001, InputKeyState=1 > trace:key:TranslateMessage (WM_KEYUP, 0041, C01E0001) > > > > Do you see what I need to do to get this working ? > > Thanks in advance :) > > > -- > Rikki. -- RHCE, RHCX, HP-UX Certified Administrator. > -- Solaris 7 Certified Systems and Network Administrator. > Bell Labs Unix -- Reach out and grep someone. > Those who do not understand Unix are condemned to reinvent it, poorly. >

1 0

Francois's winsock.h patch
by Dimitrie O. Paun 06 Jan '03

06 Jan '03

Alexandre, Are you going to apply Francois's winsock.h patch that fixes the Winelib problems that I encountered on wxWindows? -- Dimi.

3 3

← Newer
1
...
28
29
30
31
32
33
34
...
38
Older →

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-devel January 2003