April 2001 - Wine-Devel - list.winehq.org

STATUS_* codes

by David Howells

Can someone pin numbers on the following codes: STATUS_FILE_IS_A_DIRECTORY STATUS_INVALID_EXECUTABLE_IMAGE At least I think that's what they're called (unfortunately, my book's at home where I can't check it). They're listed in my NT native API book (though that's no guarantee that they exist), but not in the Wine header files, and I don't have a copy of the DDK installed on top of MSDEV. David

April 30, 2001

Re: edit control problem

by Ulrich Czekalla

Hi Mike, What application are you using to reproduce this bug? I can't reproduce this bug using a plain edit control. Could you give me more details. /Ulrich Mike McCormack wrote: > > Hi, > > Wine-20010418 seems to have a (serious) problem in the edit control. > The problem occurs when i press the backspace key, and there is text > after the cursor. (eg. when i am writing a reply to an email on my > web-based email). > > Text following the cursor is not draw correctly... it appears that > there are many characters missing at the beginning of the line, but > the text is only drawn correctly. Perhaps one of the recent > optimizations of the edit control missed something?? > > i don't know if this is fixed in the latest CVS... but the problem > didn't exist in previous wine releases. > > Mike > > ------------------------------------------ > mailto:Mike_McCormack(a)looksmart.com.au > ph +82 16 430 0425 > > __________________________________________________________________ > Get your own free web email at http://www.looksmart.com.au > LookSmart Australia

April 30, 2001

Re: TrueType font metrics for PostScript driver

by Ian Pilcher

Gavriel State wrote: > > What do you find objectionable about making wine work more closely with > FreeType? Absolutely nothing. I just don't think the immediate benefit of getting at TrueType encodings justifies creating the dependency at this time. > What I'd love to see happen with fonts in Wine is this: > > - shift the x11drv and wineps over to using the DDK Font Engine APIs > that are currently just stubs. > > - Implement a FreeType font driver that links to Freetype and uses > the FreeType APIs for all font metrics data as well as rasterization. > > - Implement an X11-dependant font driver in the Font Engine to rely > on as a backup if FreeType isn't available. > I agree with all of this. I did say that these font metrics files are an interim solution. > Now, all of that said, I don't actually have the time to help with > any of this directly (unless someone wants to throw a contract > my way, of course). All I can really do is cheer you on from the > sidelines should you decide to go for it, and perhaps offer the > occasional nugget of advice. Speaking of which, I do hope that you've > seen the font & printing code in the Corel wine tree. It may not > do you much immediate good, but I suspect that it could be a usefull > reference point. > I don't have the time or the skills to do this. For now, I just want to get the driver Unicode-enabled. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

April 30, 2001

Re: TrueType font metrics for PostScript driver

by Gavriel State

Ian Pilcher wrote: > > In order to Unicode-enable the PostScript driver, it needs information > about about font encodings that isn't present in Adobe's AFM file > format (glyph names for character encodings greater than 256). For > Type 1 fonts with a standard encoding, the driver can use the encoding > in the Adobe Glyph List. (There's no other choice.) > > TrueType font designers, however, seem to regard glyph naming as an > opportunity to express their creativity. Besides, the information is > present in the TrueType font files, so the driver might as well use it. > > The driver could read this information directly from the font files, but > this would make Wine dependant on the FreeType libraries, and that > doesn't strike me as a wonderful idea. Instead, I have cobbled together What do you find objectionable about making wine work more closely with FreeType? >From the end user perspective, printing in Wine sucks right now due to the fact that you've got to manually make all these AFM files (or now your proposed TT equivalent), and then just kind of hope that the printer has the font available. If you're printing to a local inkjet or something and you have Ghostscript set up just so, it'll work, but it acts horribly if you're printing to a remote PS device. The only way that that problem can be solved is if we can automatically upload a T1 version of any given font to the PS file. We can only do that if we have access to the glyph outline data, which would require linking to something like FreeType in some way. When we were doing WPO2K for Linux at Corel, we used Bitstream's commercial font server for this purpose. It had an extended API that you could use to get at additional font characteristics and glyph outlines. It was a major pain to use, and it appears to be the top reason that end users have problems with the product (font server configuration is a nightmare for newbies). It's a shame that we didn't use FreeType instead. What I'd love to see happen with fonts in Wine is this: - shift the x11drv and wineps over to using the DDK Font Engine APIs that are currently just stubs. - Implement a FreeType font driver that links to Freetype and uses the FreeType APIs for all font metrics data as well as rasterization. - Implement an X11-dependant font driver in the Font Engine to rely on as a backup if FreeType isn't available. Using FreeType more directly would also allow Wine to do serious typography - the metrics data available from X is awful compared to what you can get directly from FreeType, and doing anything less gives you subtle variations in glyph placement that can completely mess up the decision of where to break a line. If we ever want to see people using Wine for serious graphics and page layout applications, we have no choice but to go for the FreeType approach. Now, all of that said, I don't actually have the time to help with any of this directly (unless someone wants to throw a contract my way, of course). All I can really do is cheer you on from the sidelines should you decide to go for it, and perhaps offer the occasional nugget of advice. Speaking of which, I do hope that you've seen the font & printing code in the Corel wine tree. It may not do you much immediate good, but I suspect that it could be a usefull reference point. Good luck! -Gav -- Gavriel State, CEO TransGaming Technologies Inc. http://www.transgaming.com gav(a)transgaming.com

April 30, 2001

TrueType font metrics for PostScript driver

by Ian Pilcher

In order to Unicode-enable the PostScript driver, it needs information about about font encodings that isn't present in Adobe's AFM file format (glyph names for character encodings greater than 256). For Type 1 fonts with a standard encoding, the driver can use the encoding in the Adobe Glyph List. (There's no other choice.) TrueType font designers, however, seem to regard glyph naming as an opportunity to express their creativity. Besides, the information is present in the TrueType font files, so the driver might as well use it. The driver could read this information directly from the font files, but this would make Wine dependant on the FreeType libraries, and that doesn't strike me as a wonderful idea. Instead, I have cobbled together a small program which reads a TrueType font file and creates a "TrueType Font Metrics" file, which is very similar to an AFM file. (This program does use the FreeType library.) Anyone have any objections to using this approach as a interim measure? -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

April 30, 2001

Problem in DIB section / bitblt

by Marcus Meissner

Hi, Following trace has a BadMatch error related to DIB and XShm. Strangely, if I do: --- bitblt.c 2001/01/15 22:30:51 1.28 +++ bitblt.c 2001/04/29 17:06:14 @@ -1461,7 +1461,8 @@ sDst = X11DRV_LockDIBSection( dcDst, DIB_Status_None, FALSE ); sSrc = X11DRV_LockDIBSection( dcSrc, DIB_Status_None, FALSE ); - if ((sSrc == DIB_Status_AppMod) && (rop == SRCCOPY)) { + if (0 && (sSrc == DIB_Status_AppMod) && (rop == SRCCOPY)) { + FIXME("in fast branch\n"); /* do everything ourselves; map coordinates */ xSrc = dcSrc->DCOrgX + XLPTODP( dcSrc, xSrc ); ySrc = dcSrc->DCOrgY + YLPTODP( dcSrc, ySrc ); it no longer does crash, but proceeds happily. So something is broken in the fast path, but what :/ Ciao, Marcus Call user32.GetDesktopWindow() ret=60cb02ca tid=08063358 Ret user32.GetDesktopWindow() retval=0000008c ret=60cb02ca tid=08063358 Call user32.GetDC(0000008c) ret=60cb02d4 tid=08063358 Call x11drv.GetDC(0000008c,00000088,00000000,0001001a) ret=40783118 tid=08063358 Ret x11drv.GetDC() retval=00000001 ret=40783118 tid=08063358 Ret user32.GetDC() retval=00000088 ret=60cb02d4 tid=08063358 Call gdi32.CreateDIBSection(00000088,40454704,00000000,4a9a94a0,00000000,00000000) ret=60cb02e7 tid=08063358 trace:bitmap:X11DRV_DIB_CreateDIBSection format (16,16), planes 1, bpp 24, size 768, colors 0 (RGB) trace:bitmap:CreateCompatibleBitmap (0ce4,16,16) = trace:bitmap:CreateBitmap 16x16, 65536 colors returning 00000ce8 trace:bitmap:CreateCompatibleBitmap 0ce8 trace:bitmap:X11DRV_DIB_DoProtectDIBSection Changed protection from 4 to 2 Ret gdi32.CreateDIBSection() retval=00000ce8 ret=60cb02e7 tid=08063358 Call user32.ReleaseDC(0000008c,00000088) ret=60cb02f6 tid=08063358 Ret user32.ReleaseDC() retval=00000001 ret=60cb02f6 tid=08063358 Call kernel32.IsBadReadPtr(4ad30000,00000001) ret=60cb08f2 tid=08063358 Ret kernel32.IsBadReadPtr() retval=00000000 ret=60cb08f2 tid=08063358 Call ntdll.RtlEnterCriticalSection(60cc1298) ret=60c9d188 tid=08063358 Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=60c9d188 tid=08063358 Call kernel32.CreateFileA(4a8aafb0 "Y:\\programme\\Mindjet\\MindManager\\sys\\codes\\code6.bmp",80000000,00000001,00000000,00000003,00000080,00000000) ret=60c9e56a tid=08063358 Ret kernel32.CreateFileA() retval=00000068 ret=60c9e56a tid=08063358 Call kernel32.ReadFile(00000068,405b6adc,0000000e,405b6aec,00000000) ret=60c9dfbd tid=08063358 Ret kernel32.ReadFile() retval=00000001 ret=60c9dfbd tid=08063358 Call kernel32.ReadFile(00000068,405b6ab4,00000028,405b6aec,00000000) ret=60c9dfed tid=08063358 Ret kernel32.ReadFile() retval=00000001 ret=60c9dfed tid=08063358 Call kernel32.CloseHandle(00000068) ret=60c9e0b4 tid=08063358 Ret kernel32.CloseHandle() retval=00000001 ret=60c9e0b4 tid=08063358 Call kernel32.CreateFileA(4a8aafb0 "Y:\\programme\\Mindjet\\MindManager\\sys\\codes\\code6.bmp",80000000,00000001,00000000,00000003,00000080,00000000) ret=60c9e56a tid=08063358 Ret kernel32.CreateFileA() retval=00000068 ret=60c9e56a tid=08063358 Call kernel32.SetFilePointer(00000068,00000036,00000000,00000000) ret=60c9d217 tid=08063358 Ret kernel32.SetFilePointer() retval=00000036 ret=60c9d217 tid=08063358 Call kernel32.HeapAlloc(4a260000,00000000,00018010) ret=60cb15a0 tid=08063358 Ret kernel32.HeapAlloc() retval=4a26546c ret=60cb15a0 tid=08063358 Call kernel32.ReadFile(00000068,4a26546c,00018000,405b6ad0,00000000) ret=60c9d4ff tid=08063358 Ret kernel32.ReadFile() retval=00000001 ret=60c9d4ff tid=08063358 trace:bitmap:X11DRV_DIB_Lock Locking 0x40455ea8 from thread 08063358 trace:bitmap:X11DRV_DIB_Coerce AppMod requested in status InSync trace:bitmap:X11DRV_DIB_DoProtectDIBSection Changed protection from 2 to 4 trace:bitmap:X11DRV_DIB_Unlock Unlocking in status AppMod trace:bitmap:X11DRV_DIB_Unlock Unlocked 0x40455ea8 Call kernel32.ReadFile(00000068,4a26549c,00017fd0,405b6ad0,00000000) ret=60c9d4ff tid=08063358 Ret kernel32.ReadFile() retval=00000001 ret=60c9d4ff tid=08063358 Call ntdll.RtlEnterCriticalSection(60cc17d0) ret=60cb3773 tid=08063358 Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=60cb3773 tid=08063358 Call ntdll.RtlLeaveCriticalSection(60cc17d0) ret=60cb3789 tid=08063358 Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=60cb3789 tid=08063358 Call kernel32.HeapFree(4a260000,00000000,4a26546c) ret=60cb1124 tid=08063358 Ret kernel32.HeapFree() retval=00000001 ret=60cb1124 tid=08063358 Call kernel32.CloseHandle(00000068) ret=60c9d22f tid=08063358 Ret kernel32.CloseHandle() retval=00000001 ret=60c9d22f tid=08063358 Call ntdll.RtlLeaveCriticalSection(60cc1298) ret=60c9d236 tid=08063358 Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=60c9d236 tid=08063358 Call ntdll.RtlEnterCriticalSection(60cc1298) ret=60c9d91d tid=08063358 Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=60c9d91d tid=08063358 Call kernel32.CreateFileA(4a8aafb0 "Y:\\programme\\Mindjet\\MindManager\\sys\\codes\\code6.bmp",80000000,00000001,00000000,00000003,00000080,00000000) ret=60c9e56a tid=08063358 Ret kernel32.CreateFileA() retval=00000068 ret=60c9e56a tid=08063358 Call kernel32.ReadFile(00000068,405b6a90,0000000e,405b6aa0,00000000) ret=60c9dfbd tid=08063358 Ret kernel32.ReadFile() retval=00000001 ret=60c9dfbd tid=08063358 Call kernel32.ReadFile(00000068,405b6a68,00000028,405b6aa0,00000000) ret=60c9dfed tid=08063358 Ret kernel32.ReadFile() retval=00000001 ret=60c9dfed tid=08063358 Call kernel32.CloseHandle(00000068) ret=60c9e0b4 tid=08063358 Ret kernel32.CloseHandle() retval=00000001 ret=60c9e0b4 tid=08063358 Call ntdll.RtlLeaveCriticalSection(60cc1298) ret=60c9d9db tid=08063358 Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=60c9d9db tid=08063358 Call gdi32.CreateCompatibleDC(00000000) ret=0040fcda tid=08063358 Ret gdi32.CreateCompatibleDC() retval=00000cec ret=0040fcda tid=08063358 Call gdi32.CreateCompatibleDC(00000000) ret=0040fce2 tid=08063358 Ret gdi32.CreateCompatibleDC() retval=00000cf0 ret=0040fce2 tid=08063358 Call gdi32.CreateBitmap(00000010,00000010,00000001,00000001,00000000) ret=0040fcf5 tid=08063358 trace:bitmap:CreateBitmap 16x16, 2 colors returning 00000cf4 Ret gdi32.CreateBitmap() retval=00000cf4 ret=0040fcf5 tid=08063358 Call gdi32.SelectObject(00000cec,00000cf4) ret=0040fd02 tid=08063358 Ret gdi32.SelectObject() retval=00000044 ret=0040fd02 tid=08063358 Call gdi32.SelectObject(00000cf0,00000ce8) ret=0040fd0c tid=08063358 Ret gdi32.SelectObject() retval=00000044 ret=0040fd0c tid=08063358 Call gdi32.SetBkColor(00000cf0,00c080ff) ret=0040fd1b tid=08063358 Ret gdi32.SetBkColor() retval=00ffffff ret=0040fd1b tid=08063358 Call gdi32.BitBlt(00000cec,00000000,00000000,00000010,00000010,00000cf0,00000000,00000000,00cc0020) ret=0040fd33 tid=08063358 trace:bitblt:BitBlt hdcSrc=0cf0 0,0 16 bpp->hdcDest=0cec 0,0 16x16x1 rop=cc0020 trace:bitmap:X11DRV_DIB_Lock Locking 0x40455ea8 from thread 08063358 fixme:bitblt:X11DRV_BitBlt in fast branch trace:bitmap:X11DRV_DIB_CopyDIBSection (0x4045610c,0x40455ee8,0,0,0,0,16,16) trace:bitmap:X11DRV_DIB_DoCopyDIBSection Copying from DIB bits to Pixmap trace:bitmap:X11DRV_DIB_SetImageBits XPutImage(0x8054790,29361387,0x8074680,0x808bbe8,0,0,0,0,16,16) X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 147 (MIT-SHM) Minor opcode of failed request: 3 (X_ShmPutImage) Serial number of failed request: 5544 Current serial number in output stream: 5545 [

April 29, 2001

edit control problem

by Mike McCormack

Hi, Wine-20010418 seems to have a (serious) problem in the edit control. The problem occurs when i press the backspace key, and there is text after the cursor. (eg. when i am writing a reply to an email on my web-based email). Text following the cursor is not draw correctly... it appears that there are many characters missing at the beginning of the line, but the text is only drawn correctly. Perhaps one of the recent optimizations of the edit control missed something?? i don't know if this is fixed in the latest CVS... but the problem didn't exist in previous wine releases. Mike ------------------------------------------ mailto:Mike_McCormack(a)looksmart.com.au ph +82 16 430 0425 __________________________________________________________________ Get your own free web email at http://www.looksmart.com.au LookSmart Australia

April 29, 2001

Re: Quickbooks 5 and printing

by Dan Engel

Dmitry Timoshkov wrote: > > As I already asked, please do +relay,+module trace, compress it, put > somewhere on the net and post an url here. (Also please do not add any > other debugging switches without additional request). > Okay, here are the traces. Here (ftp://sourceharvest.com/pub/wine_qb4.log.gz) is the QB4 trace. QB4 printing works. The other (ftp://sourceharvest.com/pub/wine_qb5.log.gz) is the QB5 trace. QB5 printing doesn't work. -Dan

April 28, 2001

Re: InstallShield and ole question...

by Mike Bond

From: "Jeremy White" <jwhite(a)codeweavers.com> > juergen.schmied(a)debitel.net wrote: > > For local marshalling we could use our own protocol and even our own way of ipc if we don't try to mix processes with native and wine com-dll's. It com server is only interested in the result ;-). And isn't the com marshalling similar to the dce one? > > For networking - the dcom protocoll is documented (IMHO). > > With COM, the other issue is that someone needs to look at the MS > patents > in this area. Mainsoft is telling people that they can't use Wine to > port COM code, because Microsoft holds patents on some of the Vtable > logic used > in COM (and no, I don't have any more detail than that, this came to me > third hand). > I've also asked the FSF for help tracking this FUD down and refuting it. That would be unfortunate, I would like to hear more about what you find out from FSF. > The upshot of my comment is that it's critical that we use our own > marshalling/ipc protocol. The only problem with this is that CLSCTX_REMOTE_SERVER would then be limited to connecting only to other Wine apps, which could be fairly crippling. If, on the other hand, there is a way to work around these patents, then it would probably be best to not implement the protocol twice. It may well be better to wait a bit and hear the FSF response. > DCOM is documented, and what's more it appears to be well documented, > and what's more, it doesn't look as though the implementation will > be particularly hard... Yes, DCOM is very well documented.

April 28, 2001

Re: InstallShield and ole question...

by Andreas Mohr

On Thu, Apr 26, 2001 at 04:47:01PM -0700, Dan Kegel wrote: > Jeremy White wrote: > > > This getes me back to the other part of the question, is anyone currently > > > working on this? I know people at CodeWeavers supposedly were working on > > > getting the various mutations of InstallShield working, this error seems > > > to be pretty common across all InstallSheild v6 based installers I've seen. > > > I had also heard there was progress getting Alice install working at > > > TransGaming, is that InstallSheild v6 based? > > > > AFAIK, no one is actively doing this. We're working hard on the > > installers, including everything up to the point of actually > > diving of the COM/DCOM cliff. > > http://freedce.sourceforge.net/ is an open source project to implement COM. > It's been around quite some time, and started off from the same > DCE sources that Microsoft based its stuff on. > (See also http://linas.org/linux/corba.html ) > It was dormant for a while, but I think it's being worked on again. > > I wonder if that might not be useful here? Actually linuxtoday.com happens to link to an article at www.consultingtimes.com/DCE.html just today :-) (headline "The Free DCE project - Trying to regain lost ground...") -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.germany.net/100-30936/

April 27, 2001