January 2003 - Wine-Devel - list.winehq.org

Re: [RFC] The Wine UI page

by Dan Kegel

Dimitrie O. Paun wrote: > There is a new page in my little Wine WWW -- the UI status page: > > http://www.dssd.ca/wine/Wine-UI.html Very cool. Does that include the UI issues mentioned in http://www.winehq.com/hypermail/wine-devel/2003/01/1053.html ? Duane's looking at the missing messages; I'd like to look into the misplaced scrollbars, but probably need a hint about where to start looking. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

Jan. 30, 2003

Re: [RFC] The Wine UI page

by Eric Pouech

> (I think MDI falls more intuitively into the Window Management > section than in the control section) agreed (that's why I put "control" in quoted) > Common Dialog > -- File Open/Save > -- Font Selection > -- etc. maybe, if you want full UI coverage, you could add a windowing driver section (X11, TTY, SDL...) IMO, this type of information should be integrated in current status page. A+ -- Eric Pouech

Jan. 30, 2003

Re: [RFC] The Wine UI page

by Eric Pouech

> This is a page that I've been meaning to create for many months now. > Please check it out, and let me know if you notice any inaccuracies. I'd add the MDI "control" to the list too, and maybe the def procs (window, dlg...) A+ -- Eric Pouech

Jan. 30, 2003

Re: Why is IOCTL_CDROM_READ_TOC so slow?

by Eric Pouech

Waldeck Schutzer wrote: > Hi Eric, > > It is very strange indeed, but I just tested it again and I'm convinced > that on my system that call can take a few seconds. I'm also pretty sure > there is no concurrent access to the drive and automount is not running. > I even did this on a failsafe session just to be sure, but still the > same thing. maybe you could try it with a simple C program: 1/ open fd 2/ do the read toc ioctl 3/ close time the operation 2/ > I wonder there is something wrong with my kernel (2.4.18), > or worse, with my computer. On the other hand, it works pretty fast on > Windows. rather strange... I reran on my computer win98 cdplayer, and everything's ok. I wonder if the CD ROM driver in Linux is not to blame then A+ -- Eric Pouech

Jan. 30, 2003

Re: [RFC] The Wine UI page

by Dimitrie O. Paun

On Thu, 30 Jan 2003, Eric Pouech wrote: > maybe, if you want full UI coverage, you could add a windowing driver > section (X11, TTY, SDL...) That's a good idea, it will be another section. > IMO, this type of information should be integrated in current status page. Sure, it's just so much easier to work with it on my site. I am a bit concerned that merging this page with the big status page will result in a huge page that is not that useful. I think that UI elements deserve a special place (I have not explained yet why I think so, that's another matter). Nevertheless, once this thing stabilizes, it can be integrated in the big status page if people feel it's a good idea. Or we can put it on the official site as a separate page, and link to it from the main status page. Details, let's get the content down first. :) -- Dimi.

Jan. 30, 2003

Re: [RFC] The Wine UI page

by Dimitrie O. Paun

On Thu, 30 Jan 2003, Eric Pouech wrote: > I'd add the MDI "control" to the list too, and maybe the def procs > (window, dlg...) I will add two more sections: Fundamentals: -- Visible Region Handling -- Window Management -- MDI (I think MDI falls more intuitively into the Window Management section than in the control section) Common Dialog -- File Open/Save -- Font Selection -- etc. Dan, currently it does not include the MDI issues you reported. First I will like to get a full inventory of items that make up the User Interface (UI). Once that's in, we can add notes to keep track of all this problems (and maybe link them to bugs in bugzilla). So guys, if you can think of stuff that should go on this page, *please* speak up. -- Dimi.

Jan. 30, 2003

Re: w2k Explorer makes wine crash in RtlRaiseException

by Dan Kegel

Rolf Kalbermatter wrote: > before Explorer is going to run under Wine, there needs to be > a whole lot more done than that. The entire shell support in Wine is not > at the point where Explorer will be able to do anything useful... Yep. We need to implement a lot of shell hooks... people want to be able to install plugins that add features to Explorer. > Explorer although an application is so tightly bound to the underlying OS, > that I doubt that you could mix the Explorer application with different > Windows versions itself. You definitely can't run W2K Explorer on a W9x > platform and vice versa. > > In general I think it is probably simpler to get a Wine equivalent of Explorer > written than to get Wine to the point where it will run Windows Explorer. Probably. We'll still need to implement those shell hooks, though. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

Jan. 30, 2003

Re: Run from the build tree possible?

by Zsolt Rizsanyi

On Thursday 30 January 2003 14:54, Uwe Bonnes wrote: > >>>>> "Dimitrie" == Dimitrie O Paun <dpaun(a)rogers.com> writes: > > Dimitrie> On January 30, 2003 08:34 am, Ferenc Wagner wrote: > >> Hello, > >> > >> is it possible somehow to run Wine from the build tree? I mean > >> without 'make install'? It's too lengthy to install after every one > >> line change during printf-debugging... > > Dimitrie> Short answer: Yes, you can run out of the tree, but you can't > Dimitrie> compile winelib apps. If you just want to run a program like > Dimitrie> so: wine <myprog> than there's no problem. You just need to > Dimitrie> set the env right. This is what I use: > > Dimitrie> WINEHOME=/home/dimi/dev/wine/wine export > Dimitrie> LD_LIBRARY_PATH="$WINEHOME" export > Dimitrie> WINEDLLPATH="$WINEHOME/dlls:$WINEHOME/programs" alias > Dimitrie> wine="/home/dimi/dev/wine/wine/wine" > > Isn't already wine a script that takes care of setting all those variables? There is. Look at tools/winewrapper. There is even a symlink (named 'wine') to it in the base dir. Regards Zsolt

Jan. 30, 2003

Re: wine/dlls/x11drv x11drv_main.c

by Alexandre Julliard

liu spider <liuspider(a)yahoo.com> writes: > And I think maybe exchange the calling order of > XCloseIM and XCloseDisplay is a better method than > just comments out XCloseIM ( I think this will lead to > some other problems). Exchanging them makes it crash on my machine, so I think we have to avoid the close, unless someone wants to chase the bug. I suspect the problem is in Xlib though, we're probably the only app trying to properly close an IM... -- Alexandre Julliard julliard(a)winehq.com

Jan. 30, 2003

Re: Run from the build tree possible?

by Ferenc Wagner

Vincent Béron <vberon(a)mecano.gme.usherb.ca> writes: > Of course, wine let's you use it inside it's build dir, so > it may be easier to just do that. Yes, it seems to work now. One catchup: I had to define a new drive for /usr/local/src/wine/programs to be able to use the debugger. What a deal... Feri.

Jan. 30, 2003