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

Re: common file dialogs

by Marcus Meissner

On Fri, Jan 31, 2003 at 10:56:28AM +0000, Mike Hearn wrote: > Hi, > > Is there a reason that: > > a) The Wine open/save dialog boxes don't show or follow symlinks and > b) They show dotfiles? > > I seem to recall a discussion on wine-devel way back on the topic of > dotfiles, but a quick archive search didn't turn up much of use. At the > very least I think it should be a pref, wading through lots of dotfiles > in your home dir makes it much harder to open files with wine, and > obviously non-technical users will wonder what is going on with all > these stranges folders that I never made...... Check out the config file: [wine] ;"ShowDirSymlinks" = "1" ;"ShowDotFiles" = "1" Ciao, Marcus

Jan. 31, 2003

Re: common file dialogs

by Fabian Cenedese

>I seem to recall a discussion on wine-devel way back on the topic of >dotfiles, but a quick archive search didn't turn up much of use. At the >very least I think it should be a pref, wading through lots of dotfiles >in your home dir makes it much harder to open files with wine, and >obviously non-technical users will wonder what is going on with all >these stranges folders that I never made...... Don't forget that the users are still Linux users, even if they use a Windows program :) bye Fabi

Jan. 31, 2003

common file dialogs

by Mike Hearn

Hi, Is there a reason that: a) The Wine open/save dialog boxes don't show or follow symlinks and b) They show dotfiles? I seem to recall a discussion on wine-devel way back on the topic of dotfiles, but a quick archive search didn't turn up much of use. At the very least I think it should be a pref, wading through lots of dotfiles in your home dir makes it much harder to open files with wine, and obviously non-technical users will wonder what is going on with all these stranges folders that I never made...... -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 31, 2003

Re: common file dialogs

by Dimitrie O. Paun

On January 31, 2003 07:06 am, Mike Hearn wrote: > Thanks. I wonder why I didn't see them before.... Actually I wonder why you are seeing the dot files in the first place -- they should be hidden, unless they are explicitly enabled in the conf file. -- Dimi.

Jan. 31, 2003

Re: half-life

by Johan Gill

On Fri, Jan 31, 2003 at 09:05:17AM +0000, Mike Hearn wrote: > Not sure. I think some people have got half life to work. > > It sounds like the program is getting stuck in a loop trying to allocate > GDI resources, which are presumably limited. I don't know if Wine > simulates the Win9x resource limitations or not (i hope not!). Try doing > a relay trace and looking at what happens just before it starts to die. Well, in some cases the objects are allocated on a pretty limited heap. The palette object was moved to a larger heap because of this. -- Johan Gill, johane(a)lysator.liu.se

Jan. 31, 2003

RE: w2k Explorer makes wine crash in RtlRaiseException

by Rolf Kalbermatter

Mike Hearn wrote: > > Yep. We need to implement a lot of shell hooks... > > people want to be able to install plugins that add features > > to Explorer. > > Yuck. That's not going to be fun. I once tried to write Explorer shell > objects to make virtual folders and such, along the way I somehow > managed to completely trash explorer such that it'd not display the > listview control for the directory at all. That part of Windows is > really not documented at all well, and there are precious few examples. > Certainly doing stuff like ZipFolders is pretty evil. Went through that hell as well. Wrote a shell extension to display the contents of a private file archive format and it took me quite some time to get it right. Didn't get results as bad as yours, but it definitely started to get strange at times. The entire shell extension interface isn't exactly well documented, not quite well designed and in my view an adhoc implementation, which unfortunately happened to survive its "proof of concept". Also subtle differences between the different Windows versions can drive you really crazy. Due to the traditional bad documentation there are many shell extensions out there who happen to work on certain Windows versions more by luck than by design and getting these things in Wine all to work in the same strange ways is going to be a nightmare. My shell extension was a self contained extension based on the early semi-official cabview shell extension from MSDN from Microsoft. Never really seriously tried to use the built in ShellView object which got only recently very limited documentation in the course of the trial decision to document many private Win32 APIs. > Is there a compelling reason why people need to do this? I can't see why > you'd want to use Explorer to browse files unless it's truly > necessary.... Well, running Explorer on Wine is IMO not a very hot topic. And most of the actual functionality of Explorer really is in shell32 and friends and Explorer is just the process who starts a user interface and ties all the things together, so what we actually would need is a very thorough implementation of the shell32 functionality anyhow. Eventually writing a WineExplorer seems to me a little more interesting although it really is a rather low priority thing (and making it work with shell extensions is going to be quite some work). It is a little bit a catch 22 situation here. Quite some APIs in shell32 and other related DLLs are mainly used in Explorer although with the recent documentation of them other applications are likely to start to use them too. To test and torture those APIs Explorer would be nice. On the other hand Explorer really does not add a lot of functionality in terms of user experience, as your Unix X desktop has very likely a filesystem browser which is more fun to use. Having our own WineExplorer is not likely to use all those APIs, as many functionality in Explorer is probably never really used in an obvious way and therefore is unlikely to be built into a WineExplorer. Rolf Kalbermatter

Jan. 31, 2003

Re: half-life

by Mike Hearn

Not sure. I think some people have got half life to work. It sounds like the program is getting stuck in a loop trying to allocate GDI resources, which are presumably limited. I don't know if Wine simulates the Win9x resource limitations or not (i hope not!). Try doing a relay trace and looking at what happens just before it starts to die. On Thu, 2003-01-30 at 22:29, Scott Jackson wrote: > halflife majorly crashes on me: > err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 112 bytes > for thousands of lines, until it eventually pukes and wants to debug. then it tells me: > Couldn't start process '148738992 0x84 ' (twice) > Why? I don't know. I remember installing it under wine, but it always puked on me like that afterwards. I have 128MB of RAM so that shouldn't be a problem. -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 31, 2003

Re: font metrics

by Mike Hearn

I think if you delete the cachedmetrics file in ~/.wine that'll do it On Thu, 2003-01-30 at 22:20, Scott Jackson wrote: > how can I force wine to do font metrics? -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 31, 2003

Re: [RFC] The Wine UI page

by Mike Hearn

> So guys, if you can think of stuff that should go on this page, > *please* speak up. WebBrowser control? Argh! *ducks* -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 31, 2003

Re: w2k Explorer makes wine crash in RtlRaiseException

by Mike Hearn

> Yep. We need to implement a lot of shell hooks... > people want to be able to install plugins that add features > to Explorer. Yuck. That's not going to be fun. I once tried to write Explorer shell objects to make virtual folders and such, along the way I somehow managed to completely trash explorer such that it'd not display the listview control for the directory at all. That part of Windows is really not documented at all well, and there are precious few examples. Certainly doing stuff like ZipFolders is pretty evil. Is there a compelling reason why people need to do this? I can't see why you'd want to use Explorer to browse files unless it's truly necessary.... -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 31, 2003