August 2002 - Wine-Devel - list.winehq.org

Re: trying to draw off-screen

by Bill Medland

----- Original Message ----- From: "Jean-Claude Batista" <jcb(a)macadamian.com> To: "Bill Medland" <billmedland(a)look.ca> Cc: <wine-devel(a)winehq.com> Sent: Friday, August 30, 2002 7:23 AM Subject: Re: trying to draw off-screen > Hi, > > Which window manager are you using ? Often it is the window manager that > reposition the window on the top right if the coordinates of the window are > beyond the screen. Not Wine. That's what I was afraid of. (I get a bit confused as to what is the window manager and what is the desktop but) KDE3 I guess. > > -- JcB > Macadamian Technologies. > > ---Original Message ----- > From: "Bill Medland" <billmedland(a)look.ca> > To: "wine-devel" <wine-devel(a)winehq.org> > Sent: Thursday, August 29, 2002 6:28 PM > Subject: trying to draw off-screen > > > > Does anyone know who constrains a window to be on the screen? > > > > Our application, in order to minimise flicker, does the hard work with a > > container application deliberately positioned well off-screen (enormous > > negative coordinates I think). > > > > This works under Windows. > > > > However under WINE the initial window appears in the top right corner of > my > > screen (I think I've seen it appear in other corners too on other > > computers). It then resizes , keeping the same top left corner (with > parts > > of the window off-screen) before correctly repositioning itself into the > > middle of the screen. > > > > Does anyone know which code is doing the initial positioning in the top > > right corner? Is this deliberate? > > > > Bill > > > > > > > Bill

Aug. 30, 2002

Re: trying to draw off-screen

by Jean-Claude Batista

Hi, Which window manager are you using ? Often it is the window manager that reposition the window on the top right if the coordinates of the window are beyond the screen. Not Wine. -- JcB Macadamian Technologies. ---Original Message ----- From: "Bill Medland" <billmedland(a)look.ca> To: "wine-devel" <wine-devel(a)winehq.org> Sent: Thursday, August 29, 2002 6:28 PM Subject: trying to draw off-screen > Does anyone know who constrains a window to be on the screen? > > Our application, in order to minimise flicker, does the hard work with a > container application deliberately positioned well off-screen (enormous > negative coordinates I think). > > This works under Windows. > > However under WINE the initial window appears in the top right corner of my > screen (I think I've seen it appear in other corners too on other > computers). It then resizes , keeping the same top left corner (with parts > of the window off-screen) before correctly repositioning itself into the > middle of the screen. > > Does anyone know which code is doing the initial positioning in the top > right corner? Is this deliberate? > > Bill > >

Aug. 30, 2002

wine regression - win16 file read problem!?

by Rizsanyi Zsolt

Hi! I have recently upgraded wine cvs and done a recompile and install. But now one of the programs I'm using does not work. My last cvs update was about 2 weeks ago. Its an old dictionary program (win16). It starts up ok, but when it tries to open the dictionary data, it says, that it is not found, and I should specify a location. I have looked at the +file debug channel output, and it does not even contain the location I have specified. Does that mean, that it does not even tries to open the file? Does somebody has some ideas where the problem could come from? Or which debug channel should I turn on to get some info about the problem? I just would like to ask for ideas before I start more serious debugging... Thanks Zsolt

Aug. 30, 2002

Re: Wine Status

by tom

> > >A couple of good sources of information about changes >in Wine: >1) Wine Weekly News articles http://www.winehq.com >2) Notes in the release ANNOUNCE file >http://cvs.winehq.com/cvsweb/wine/ANNOUNCE > >Good luck, >Andriy > >Boston, MA, USA > > > > Thanks I will start looking over the WWN articles. Me reading over the source changelog was to get a feel of who the current developers are and there patches. 15,000 lines in the last year :) I would like to say thanks to eveyone who has responded so far And I hope to have a first draft in a week or so .. I will send it here for overview and you can guy's can send patches against it. Tom

Aug. 30, 2002

Re: DOSFS_FindUnixName and "unix" filesystem (was: Re: (HELP) ...)

by Martin Wilck

Am Don, 2002-08-29 um 18.37 schrieb Duane Clark: > Since I also was stumbled for a long period on a similar problem, due to > specifying a "unix" filesystem, perhaps it would be appropriate in the > documentation to put some large warnings on that option. Wait a bit - the usual suspect is not guilty here. My FS used to be "win95" all the time. I just reckoned "unix" might come as a friend here. For "win95", it is inherently clear that "wine" and "Wine" can't be distinguished. For "unix", that shouldn't be so. Thus I suggest improving "unix" and make it work nicely in cases where "win95" cannot possibly do the job, rather than deprecating it. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

Aug. 30, 2002

Re: Wine Ma os X port

by Francois Gouget

On Thu, 29 Aug 2002, Lionel Ulmer wrote: > On Wed, Aug 28, 2002 at 04:51:29PM -0700, Francois Gouget wrote: > > Not necessarily. What you propose to do for Wine can be done for the C > > and X11 libraries. Then you get an emulator that lets you run x86 Linux > > applications on a PPC machine... including Wine. > > Well, yes... But if you have a system that creates for you a 'translation' > layer for all the libraries used by Wine, why not use it directly on Wine > itself ? You cannot have a tool that is going to write the translation layer automatically. I guess it is simpler to write it by hand for the Unix APIs (maybe a couple thousands at most?), rather than for the Windows APIs >> 10 thousands, plus tons of messages, plus tons of callbacks, plus poor documentation, etc. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ It really galls me that most of the computer power in the world is wasted on screen savers. Chris Caldwell from the GIMPS project http://www.mersenne.org/prime.htm

Aug. 30, 2002

Re: RFC: 'test' bugzilla keyword

by Tony Lambregts

Francois Gouget wrote: >On Tue, 27 Aug 2002, Paul Millar wrote: >[...] > > >>>Maybe 'conformance' would work? >>> >>> >>Personally, I prefer "regression" to "conformance", although both are >>applicable names. >> >> > >The problem is we already have a 'regression' keyword with a reasonable >meaning: 'bugs relating to programs that were working at one time but >stoped working for some reason'. But this does not specifically cover >the 'conformance test suite'. > >If a conformance test used to work and no longer does, then I think it >would be reasonable to tag it as 'conformance, regression'. > >But I have also found that some tests do not pass on Windows. IIRC, >there's a test having to do with TEMP that fails if it is set to >'c:\Windows\Temp' rather than 'c:\'. I would like to be able to make a >bug report and tag it with a keyword to indicate it is related to the >'conformance test suite' (or whatever we want to call it). Similarly, >there would be reports to be made about the conformance tests as run on >FreeBSD and Solaris. And note that none of these are regressions. > > > > You have sold me on "conformance" . The real proplem is that we have been calling the conformance test suite by the wrong name if you ask me. The thing is that this is exactly what the suite is for (to be able to track where wine and windows differ in thier behavior.) To be able to have a bug report where the source is available is indispensible. Mr Newman can we please, please, please have this. Tony Lambregts

Aug. 30, 2002

trying to draw off-screen

by Bill Medland

Does anyone know who constrains a window to be on the screen? Our application, in order to minimise flicker, does the hard work with a container application deliberately positioned well off-screen (enormous negative coordinates I think). This works under Windows. However under WINE the initial window appears in the top right corner of my screen (I think I've seen it appear in other corners too on other computers). It then resizes , keeping the same top left corner (with parts of the window off-screen) before correctly repositioning itself into the middle of the screen. Does anyone know which code is doing the initial positioning in the top right corner? Is this deliberate? Bill

Aug. 29, 2002

RE: Added H_SRCS (used by msvcmaker)

by Patrik Stridvall

> Patrik Stridvall <ps(a)leissner.se> writes: > > > Perhaps files such as include/winuser.h should be included > > for USER32 for example? > > > > Anyway what do you think about adding H_SRCS to > > every Makefile.in file? > > I don't think we want that, especially if you want to add all relevant > includes it's going to be a nightmare to maintain. Yes, I'm a little worried about that myself, but then the C_SRCS doesn't change that often and the H_SRCS are likely to change MUCH less. Futhermore it doesn't really matter if it out out sync either. If somebody developing in MSVC misses a file he can add it. It not like Wine won't build correctly. > And make depend (or > some perl equivalent) can easily determine that information for you. Well, if you just want all .h files the DLL depends on MSVC already have that in a automatically generated "folder" called External dependencies. The H_SRCS is mostly for the .h files that you are likely to want to look at or modify while developing the DLL under MSVC. But it is not strictly nessary. It is more a convenience sort of thing. Another reason that I proposed it is that maybe H_SRCS could be used fo something else though I can't think of anything right now... But sure I can search for the .h files in the director{y,ies} of each DLL. However for a DLL like ntdll files like include/wine/exception.h is very much relevent and won't be included is such a case. Not that it really matters that much but still...

Aug. 29, 2002

Re: Added H_SRCS (used by msvcmaker)

by Alexandre Julliard

Patrik Stridvall <ps(a)leissner.se> writes: > Perhaps files such as include/winuser.h should be included > for USER32 for example? > > Anyway what do you think about adding H_SRCS to > every Makefile.in file? I don't think we want that, especially if you want to add all relevant includes it's going to be a nightmare to maintain. And make depend (or some perl equivalent) can easily determine that information for you. -- Alexandre Julliard julliard(a)winehq.com

Aug. 29, 2002