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

Home » Public Forums » archive » Re: IDL workbench & windows
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL workbench & windows [message #58576 is a reply to message #58445] Fri, 08 February 2008 01:43 Go to previous messageGo to previous message
R.Bauer is currently offline  R.Bauer
Messages: 1424
Registered: November 1998
Senior Member
David Fanning schrieb:
> 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

Hi

In the past I was entering a dir where I do have my sources. If I did
start in that dir idlde this path was searched for routines.

And there was a rule in the past that's this dir is in front of the
search path.

This is gone now for idlde but still in the old way for the idl shell.

cheers
Eeimar
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: from 6.4 to 7.0
Next Topic: K- Nearest neighbor classification

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

Current Time: Fri Oct 10 06:56:54 PDT 2025

Total time taken to generate the page: 0.15994 seconds