April 2002 - Wine-devel - list.winehq.org

MS' hidden API
by Zhang Shu 09 Jul '02

09 Jul '02

Dear wine developers, I have one question on the development of wine. Long(one or two years) ago I've heard that Microsoft got some hidden APIs in their products of various windows, and they use these APIs in their own applications. I wonder if this is still a problem on their recent product like windows XP. If it is, I guess wine will not be able to run such MS applications which uses hidden APIs. Is this right? And, is wine designed(or its goal is) to run all applications(including MS product and non-MS product) that runs on windows? Please forgive me if this problem has appeared in the past. I just joined this list a couple of days ago. Thank you. Regards, -- Zhang Shu

10 10

Re: fixme:win32:PeekNamedPipe
by Andriy Palamarchuk 17 May '02

17 May '02

I just came across bugzilla entry about this issue - bug 297: http://wine.codeweavers.com/bugs/show_bug.cgi?id=297 If anybody starts to work on the bug, please take this bug and keep it updated. Andriy Palamarchuk __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/

2 1

Re: Chinese text input into Notes R6 Mail field
by Daniel Schwarz 03 May '02

03 May '02

> Actually Aric and Ulrich helped a lot and they provided us the patch you > Codeweavers did for your clients and Aric has > gained permission to open the source. Since he needs to clean up the > code, he suggested to let him post the patch when it's > done. > > I used it to try for Chinese Input on Notes Client r6. Unfortunately, > it only works on some controls. > When I want to type Chinese/Japanese on the mail content area ( do not > know what kind of widget it is), > it doesn't show properly. I think it's a bug. Could you kindly help? > Which segment of code I should trace on? I have not used Notes R6 extensively but based on my understanding of the Notes R4 - R5 code, the mail content area is a Notes Rich Text field, which is implemented internally to Notes. It's not a Windows control therefore will not be responsive to code that hooks into Windows controls. Notes is localized for many countries,including, I think, Chinese, although the Notes R6 Beta is probably US-English only. I suggest you experiment with a copy of Notes R5 with Chinese localization. If you need technical details on how localized versions of Notes handle alternate keyboard input methods, let me know and I'll see what I can dig up. Regards, Dan Schwarz http://www.winecentric.com/wiki The Wine Wiki

3 5

MAX_PATH mess fix
by Steven Edwards 01 May '02

01 May '02

It seems mingw tries to include stdlib.h after windef.h in the build process and that was the result of the warnings/error. By making this change I don't have to change any of the other headers That depend on MAX_PATH (winnls,wingdi) by adding stdlib.h in them. I don't know if its right by the wine project standards but now I can compile 90% of the wine dll sources without warrnings/errors from stupid MAX_PATH. If someone has a better way please cvs diff -u me =) Thanks Steven Changelog: Fix the MAX_PATH mess under Mingw. (for real this time) cvs diff -u windef.h Index: windef.h =================================================================== RCS file: /home/wine/wine/include/windef.h,v retrieving revision 1.62 diff -u -r1.62 windef.h --- windef.h 10 Mar 2002 00:02:34 -0000 1.62 +++ windef.h 30 Apr 2002 21:41:42 -0000 @@ -149,6 +149,10 @@ #endif #endif /* NOMINMAX */ +#ifdef __MINGW__ +#include <stdlib.h> +#else + #ifndef _MAX_PATH /* FIXME: These are supposed to be in stdlib.h only */ #define _MAX_DRIVE 3 @@ -156,9 +160,13 @@ #define _MAX_DIR _MAX_FNAME #define _MAX_EXT _MAX_FNAME #define _MAX_PATH 260 -#endif +#endif /* _MAX_PATH */ + +#ifndef MAX_PATH #define MAX_PATH _MAX_PATH +#endif /* MAX_PATH */ +#endif /* __MINGW__ */ #define HFILE_ERROR ((HFILE)-1)

2 4

word can't open documents...
by Michael Cardenas 01 May '02

01 May '02

With yesterday's cvs, opening a document causes it to crash with this output on the console: fixme:listview:LISTVIEW_UnsupportedStyles LVS_SHAREIMAGELISTS fixme:listview:LISTVIEW_SetItemCount flags LVSICF_NOINVALIDATEALL LVSICF_NOSCROLL not implemented fixme:file:FindFirstChangeNotificationA this is not supported yet (non-trivial). fixme:mpr:WNetGetUniversalNameW (L"Z:\\DOS\\My Documents\\Lkdjs ldkjsdlkj sdlkj s.doc", 0x00000001, 0x40552218, 0x4055263c): stub fixme:mpr:WNetGetUniversalNameW (L"Z:\\DOS\\My Documents", 0x00000001, 0x40553d68, 0x4055418c): stub fixme:mpr:WNetGetUniversalNameW (L"Z:\\DOS\\My Documents\\Lkdjs ldkjsdlkj sdlkj s.doc", 0x00000001, 0x4055435c, 0x40554780): stub fixme:mpr:WNetGetUniversalNameW (L"Z:\\DOS\\My Documents\\Lkdjs ldkjsdlkj sdlkj s.doc", 0x00000001, 0x405532b0, 0x405536d4): stub X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x0 Serial number of failed request: 30392 Current serial number in output stream: 30395 -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

1 5

Re: patch for cups printers
by Marcus Meissner 01 May '02

01 May '02

> --- winehq/dlls/gdi/printdrv.c Thu Mar 28 17:22:05 2002 > +++ wine/dlls/gdi/printdrv.c Mon Apr 29 15:29:42 2002 > @@ -482,6 +482,8 @@ > > if (!strncmp("LPR:",pszOutput,4)) > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > + if (!strncmp("CUPS:",pszOutput,4)) > + sprintf(psCmd,"|lp -d%s",pszOutput+4); > else > { > HKEY hkey; This is wrong, the else { } is handled in the LPR: case too so you break /etc/printcap based printing. Ciao, Marcus

4 6

wineconsole (Eric?) problem
by Ann and Jason Edmeades 01 May '02

01 May '02

Hi again, Another bug I have spotted can be demonstrated clearly by dir /s /w on wcmd on a small set of directories a couple of times (once my patch for /w is on). The first time it writes to the screen without scrolling and all is ok, the second time as it scrolls, it misses off 'Total files listed' and 'bytes free' two lines near the bottom. Basically the wineconsole is not being updated 100% correctly and skips some lines. Looking closely at the wineconsole code (by dumping out the screen at each event) I have worked out what is going on, but am not 100% sure about the 'proper' way to fix it. The problem is the console routines generally generate a sequence of events (assume an n line screen) v-scroll(x) (Make the xth line of the buffer the top line) update(x+n, x+n) (Write to the new bottom line of the screen) In the failing case I see v-scroll(x) (Make the xth line of the buffer the top line) update(x+n, x+n) (Write to the new bottom line of the screen) update(x+n+2, x+n+3) (Write beyond the bottom line of the screen) Although the data is retrieved correctly, it never gets displayed (An invalidaterect appears to happen) A simple way of avoiding this is to update wineconsole as follows: case CONSOLE_RENDERER_UPDATE_EVENT: Trace(1, " update(%d,%d)", evts[i].u.update.top, evts[i].u.update.bottom); /* test fix - Force updates to occur on visible screen */ if ((data->curcfg.win_pos.Y+data->curcfg.win_height) < evts[i].u.update.bottom) { Trace(1, " Forced vscroll \n"); data->fnScroll(data, evts[i].u.update.bottom - data->curcfg.win_height, FALSE); data->fnPosCursor(data); } else if (data->curcfg.win_pos.Y > evts[i].u.update.top) { Trace(1, " Forced vscroll2 \n"); data->fnScroll(data, evts[i].u.update.top, FALSE); data->fnPosCursor(data); } WINECON_FetchCells(data, evts[i].u.update.top, evts[i].u.update.bottom); The question is, is this correct, or is the server generating incorrect events, is the refresh not occurring properly etc? Thoughts please? Regards, Jason jason @ the-edmeades.demon.co.uk

2 4

Bugzilla: A Call to Arms
by Andriy Palamarchuk 01 May '02

01 May '02

We already had discussion on wine-devel about importance of polishing Wine, making a set of applications to work very well. Cruicial in this process is prioritizing of the issues, work distribution between developers. The companies already have internal testing and bug fixing process. Of course, each company has their own product-specific work, but most of the problems are general for Wine. I suggest to share this work more actively using Bugzilla. Recently there was some work done in cleaning the issues database and it is in pretty much usable condition. To start using bugzilla more actively I suggest following steps: 1) define subsystem/direction owners. The owners will get their system-specific bugs. They won't necessary fix the bugs themselfs, but will have complete picture about all the issues in their subsystems and coordinate the bug fixing. Developers, please let me know your areas of expertese. I can overview Wine applications. 2) more formally define process of bugs handling and use this process. There is no high qualification needed to filter out bad bug reports, duplicates, request users for more information, attach relay trace to the bug, etc, etc. Result - developers will have to spend less time on discussion trivial bugs with users, will have better bug reports to work on, users will be more involved with more active feedback. Some users are very cooperative and some bug reports are really excellent! I see that Tony Lambregts, Michael Cardenas, others do a great work with the Bugzilla database. I'm also going to contribute some time for this. 3) Prioritize bugs. This is, probably, part of (2). Some bugs, while relatively easy to fix provide very big value for the end user. Often developers do not choose such issues to work on, exactly because these issues do not present challenge to them. BTW, I do not see a field "Priority" in the bugs entries. 4) Ask users to submit there problems in Bugzilla. Submitting Bugzilla report allows us to involve users more actively, persist their bug reports. Bugzilla is a more scalable approach than using mailing list only. Of course we still will discuss bugs on the mailing lists, bug big part of communication will be unloaded. There is a lot to do and discuss. For me the goal is to have this process not worse than in Mozilla project. This is impressive: http://webtools.mozilla.org/miscstats/ http://mothra.mozilla.org/webtools/miscstats/ I also like their bug report form: http://www.mozilla.org/quality/help/bugzilla-helper.html And this is for 1 application only! I'm sure Wine can generate much bigger volume of bug reports ;-) Look forward for your comments. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com

6 8

Re: SafeDisc FAQs
by Tels 30 Apr '02

30 Apr '02

-----BEGIN PGP SIGNED MESSAGE----- Moin, On 30-Apr-02 Tels carved into stone: > And even if it did, what could non-americans care about that? http://www.theregister.co.uk/content/4/25088.html Ouch! Seems we Europeans are in for much worse things :-( Cheers, Te"I wanna move - to the Mars"ls - -- "Why do you go so slowly? Do you think this is some kind of game?" PGP key available on http://bloodgate.com/tels.asc or via email. perl -MDev::Bollocks -e'print Dev::Bollocks->rand(),"\n"' confidentially deliver eligible mindshares -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. iQEVAwUBPM8lO3cLPEOTuEwVAQEPZAf+O4FH8K6alJQRo3HYwWktedcZ7j+co6as RlN1AH3f94c2mVRZ33gzNKZlXnCgpmNYXlxPI69dgiKuxTLs/zwUj13lIPviR79H PLzp/jJde6Rb1TSkoCbLTwx2OXJClFNyb6ElhpxKDMgNKK8m22RFfuFDjoz64q4e kPJrl5lBEPDggo0ppGpn5iN0QswhP1F5XmNv6l+qlq3mnYGk4w7K9xYFxSvEVaiE iAxP89rzuE7pODsNhK0JwMyorxea7dzHrVtqYc9ryWVuva7Ab3yVwMDoIYJhri7L DQqM6Q/NIQsmdcVXRMkxljfaNBoKVhCVn1pZoE5NT5nwoYdvmcVz5Q== =AadL -----END PGP SIGNATURE-----

1 0

Re: wine/win32 editline.c
by Eric Pouech 30 Apr '02

30 Apr '02

Alexandre Julliard a écrit : > Modified files: > win32 : editline.c > > Log message: > Jason Edmeades <us(a)the-edmeades.demon.co.uk> > - Added f8 (history retrieval from partial command) support > - Delete key deletes current character > - Ctrl + end deletes to end of line > - Ctrl + right stopped before the word itself <patch excerpt> static KeyEntry EmacsKeyMapCtrl[] = { { CTRL('@'), WCEL_SetMark }, @@ -617,6 +664,7 @@ {/*VK_END*/ 0x23, WCEL_MoveToEnd }, {/*VK_UP*/ 0x26, WCEL_MoveToPrevHist }, {/*VK_DOWN*/ 0x28, WCEL_MoveToNextHist }, + {/*VK_DEL*/ 0x2e, WCEL_FindPrevInHist /*L_DeleteCurrChar*/ }, { 0, NULL } }; </patch excerpt> there's a typo in the patch. the VK_DEL entry should point to WCEL_DeleteCurrChar and not to WCEL_FindPrevInHist A+

1 0