comp.lang.idl-pvwave archive: archive » Re: IDL workbench & windows

Home » Public Forums » archive » Re: IDL workbench & windows

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: IDL workbench & windows [message #58430 is a reply to message #58422]

Fri, 01 February 2008 08:52

elwood
Messages: 23
Registered: February 2007

Junior Member

I guess my main problem was that under linux when I used IDL
I was in a directory creating programs.
Data files were usually also in this directory.

But under workbench, my current working dir is not the same as the
project directory
and that is driving me nuts.
Data files may be in the projectr dir, but if my current working dir
is not the project dir,
idl doesnt know about them.
I dont want to have to lookup (using cd,current=junk) my current dir
all the time,
figure out what directory the project is in and then type an
additional command to cd to that dir.

When you open a project workbench is opening a directory essentially.
I looked around in IDL and couldnt figure out what the variable was
that held
the project dir name, so that I could hardwire the following into my
startup:

"When a project is opened change current dir to the project dir"

The organization of workbench files and the potential for linked files
is very different from what I am used to under linux.

Does anyone know what the system variable is that holds the value of
the project directory
in which you are currently working?

Thanks,
Elisha

On Jan 31, 9:21 pm, David Fanning <n...@dfanning.com> wrote:
> elwood writes:
>> One last note for any illustrious readers:
>> When I have re-opened a project, the project explorer shows my idl
>> source file
>> and the fits file that I am trying to read.
>> However Even though the path to the fits file is in my IDL path,
>> it doesnt seem to know where the fits file is unless I cd to the
>> directory where it is located.
>
>> My quick read of how the idl path works under windows is that it
>> search for .pro and .save files in those locations.
>> How can I make it know about other files??
>
> Why would you think IDL does this kind of thing? It
> has never done it in the past. The documentation
> (*.pro and *.sav files only) seems pretty clear to me.
> Are you possibly expecting things from IDL that it
> can't deliver?
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")

Report message to a moderator

[Message index]

		Re: IDL workbench & windows By: David Fanning on Fri, 01 February 2008 09:57
		Re: IDL workbench & windows By: elwood on Fri, 01 February 2008 08:52
		Re: IDL workbench & windows By: Steve[5] on Fri, 01 February 2008 01:01
		Re: IDL workbench & windows By: David Fanning on Thu, 31 January 2008 19:33
		Re: IDL workbench & windows By: David Fanning on Thu, 31 January 2008 19:21
		Re: IDL workbench & windows By: elwood on Thu, 31 January 2008 17:04
		Re: IDL workbench & windows By: elwood on Thu, 31 January 2008 16:50
		Re: IDL workbench & windows By: R.Bauer on Fri, 08 February 2008 01:43
		Re: IDL workbench & windows By: David Fanning on Fri, 08 February 2008 05:59
		Re: IDL workbench & windows By: elwood on Mon, 04 February 2008 14:51

Previous Topic:	from 6.4 to 7.0
Next Topic:	K- Nearest neighbor classification

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 06:59:49 PDT 2025

Total time taken to generate the page: 0.31800 seconds