1. Euphoria's current_dir() bug
Apparently current_dir() returns a different directory name
when using drag and drop for filenames, then when just
double clicking the exe filename without dropping a filename
onto the exe.
Double clicking the exw or bindw'd exe filename,
current_dir() returns the expected directory name.
Dragging a filename onto a bound exe (bindw)
causes the current_dir() name to always be c:\.
To demonstrate the problem,
bindw the following program:
include get.e
sequence currdir
atom i
currdir=current_dir()
printf(1,"%s\n",{currdir})
i=wait_key()
Then do the following:
1. Run the exe program and note the result printed on the screen.
2. Drag and drop a filename onto the exe program and
note the new result printed to the screen.
Note that the results from (1) and (2) above are different.
Any ideas?
--Al
2. Re: Euphoria's current_dir() bug
Al Getz writes:
> Double clicking the exw or bindw'd exe filename,
> current_dir() returns the expected directory name.
Yes.
> Dragging a filename onto a bound exe (bindw)
> causes the current_dir() name to always be c:\.
In my case it was c:\windows,
but it's not a bug in current_dir().
The current directory _really was_ c:\windows.
I confirmed this by having the Euphoria program
successfully open a file located in c:\windows
without specifying any directory path.
This is some quirk of drag&drop in Windows.
It's not a problem with current_dir().
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
