wine-devel May 2002

106 participants
296 discussions

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

clipping message
by Medland, Bill 01 May '02

01 May '02

Did someone want to know about this one? err:clipping:CLIPPING_UpdateGCRegion hVisRgn is zero. Please report this. (Our application printing a Crystal reports report from a DB2 database. I don't know if it's relevant but the data is read and under windows the preview display includes a treeview on the left with a couple of empty labels) If no-one else is interested I'll look into it later. Bill

1 0

Statusbar broken?
by Medland, Bill 01 May '02

01 May '02

I've just noticed that in the past few days all the stuff that normally appears in the statusbar etc at the bottom of our application has disappeared. Is this a known regression that someone is looking into or is it up to me? Bill

1 0

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

Ntddk.h wcstol question
by Steven Edwards 01 May '02

01 May '02

On some of the dlls this is a problem. Wine - include/ntddk.h INT __cdecl wcstol(LPCWSTR,LPWSTR*,INT); Mingw - stdlib.h long wcstol (const wchar_t*, wchar_t**, int); ReactOS - msvcrt/stdlib.h long wcstol (const wchar_t* wsNumber, wchar_t** pwsAfterNumber, int nBase); Anyone have a idea about what to do here? Thanks Steven "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson

1 0

Jump to page:

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 May 2002