comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » 6.1 vs. previous: runtime changes working directory
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
6.1 vs. previous: runtime changes working directory [message #43213] Thu, 24 March 2005 14:44 Go to previous message
Vince Hradil is currently offline  Vince Hradil
Messages: 574
Registered: December 1999
Senior Member
I typically deploy programs by creating a .sav file then using a
shell-script to run: idl -rt=/usr/local/idlsavs/whatever.sav

In the main program in the sav file, I check to see if the user started
idl from within our "data" directory hierarchy, something like:

cd, current=cwd
if strpos(cwd,datadirpath) ge 0 then fpath=cwd else fpath=datadirpath

Then I can use this info for my dialog_pickfile:

fname = dialog_pickfile(path=fpath)

And the user doesn't have to navigate through multiple layers of
subdirectories, just to get to where he started.

In previous versions of idl (oh, say 5.4 - 6.0?) this worked fine.
I've just now recompiled in 6.1 and despite starting the program from
within the datadirpath hierarchy, the "cd, current=cwd" sets cwd to be
the directory where the sav file is ("/usr/local/idlsavs" in the
example above)

So, what's my question?
1. Is there a cl flag for idl that will set a working directory - if I
were using Windoze, perhaps I could set "Start in:", but, alas I'm
using Solaris.
2. Is this a feature? If so, why?

TIA
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: 6.1 vs. previous: runtime changes working directory
Next Topic: Re: Displaying floating point values with user specified decimal places?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 06:19:21 PDT 2025

Total time taken to generate the page: 0.09796 seconds