Re: Interface for working directories/launchers

2004-12-24 Thread Alexandre Julliard
Mike Hearn <[EMAIL PROTECTED]> writes: > My proposal is to have a new winelib app "winemenulauncher" which simply > takes the working directory, program and arguments, and runs the program > but switching current directory first, ie the menu entry would look like: > > Exec=wine winemenulauncher c

Re: Interface for working directories/launchers

2004-12-23 Thread Mike Hearn
On Thu, 23 Dec 2004 16:03:13 -0500, Dimitrie O. Paun wrote: > Why not just: > > Exec=winemenulauncher c:\games\supreme supreme.exe Could be, but we already dump lots of programs into the path. The other thing is that win32 launchers have "working directory" and "command": we should reproduce them

Re: Interface for working directories/launchers

2004-12-23 Thread Dimitrie O. Paun
On Thu, Dec 23, 2004 at 06:14:09PM +, Mike Hearn wrote: > Exec=wine winemenulauncher c:\games\supreme supreme.exe > > Does this sound sensible? Why not just: Exec=winemenulauncher c:\games\supreme supreme.exe -- Dimi.

Interface for working directories/launchers

2004-12-23 Thread Mike Hearn
Hi, Wine currently creates launchers (.desktop files) with an Exec line like this: Exec=wine 'c:\games\supreme\supreme.exe' But, some games expects to be run from its working directory. As working directory typically doesn't matter to UNIX apps, some desktop environments like GNOME don't let you