| Re: Trouble running demo [message #45066 is a reply to message #45065] |
Mon, 01 August 2005 22:26   |
Mark Hadfield
Messages: 783
Registered: May 1995
|
Senior Member |
|
|
Richard G. French wrote:
> Good call, Mark - I renamed the file to be demoobj__define.pro instead of
> demoObj__define.pro and it was able to compile the demo. This is something
> that RSI should definitely fix on the Mac distribution.
And on other distributions, I shouldn't wonder.
> As for not finding the demo.sav file, I do have $IDL_DIR/lib/hook in my
> path, but it occurs after $IDL_DIR/examples/demo/demosrc in the !PATH, so
> that is why it finds the source file first. For my path definition, I have
>
> setenv IDL_PATH +/usr/local/rsi/idl_6.2/:
>
> How do you have your path set so that the hook savefiles come first?
The entry in my path definition (the "File/Preferences/Path" dialogue
box) is <IDL_DEFAULT>. This gets expanded to...
D:\Program Files\RSI\IDL62\lib\hook
D:\Program Files\RSI\IDL62\lib\itools\components
D:\Program Files\RSI\IDL62\lib\itools\framework
D:\Program Files\RSI\IDL62\lib\itools\ui_widgets
D:\Program Files\RSI\IDL62\lib\itools
D:\Program Files\RSI\IDL62\lib\obsolete
D:\Program Files\RSI\IDL62\lib\utilities
D:\Program Files\RSI\IDL62\lib\wavelet\source
D:\Program Files\RSI\IDL62\lib
D:\Program Files\RSI\IDL62\examples\data
D:\Program Files\RSI\IDL62\examples\demo\demodata
D:\Program Files\RSI\IDL62\examples\demo\demoslideshows\slideshowsrc
D:\Program Files\RSI\IDL62\examples\demo\demosrc
D:\Program Files\RSI\IDL62\examples\demo
D:\Program Files\RSI\IDL62\examples\doc\ActiveX\SecondExample
D:\Program Files\RSI\IDL62\examples\doc\ActiveX\VBCopyPrint
D:\Program Files\RSI\IDL62\examples\doc\ActiveX\VBLoadCt
D:\Program Files\RSI\IDL62\examples\doc\ActiveX\VBObjGraph
D:\Program Files\RSI\IDL62\examples\doc\ActiveX\VBPalette
D:\Program Files\RSI\IDL62\examples\doc\bridges\COM
D:\Program Files\RSI\IDL62\examples\doc\dicom
D:\Program Files\RSI\IDL62\examples\doc\file_io
D:\Program Files\RSI\IDL62\examples\doc\guibuilder
D:\Program Files\RSI\IDL62\examples\doc\image
D:\Program Files\RSI\IDL62\examples\doc\itools
D:\Program Files\RSI\IDL62\examples\doc\language
D:\Program Files\RSI\IDL62\examples\doc\objects
D:\Program Files\RSI\IDL62\examples\doc\plot
D:\Program Files\RSI\IDL62\examples\doc\project
D:\Program Files\RSI\IDL62\examples\doc\sdf
D:\Program Files\RSI\IDL62\examples\doc\signal
D:\Program Files\RSI\IDL62\examples\doc\utilities
D:\Program Files\RSI\IDL62\examples\doc\widgets
D:\Program Files\RSI\IDL62\examples\HP_TIFF
D:\Program Files\RSI\IDL62\examples\imsl
D:\Program Files\RSI\IDL62\examples\misc
D:\Program Files\RSI\IDL62\examples\widgets\wexmast
D:\Program Files\RSI\IDL62\examples\widgets
D:\Program Files\RSI\IDL62\examples
I've just been reading about the EXPAND_PATH function. Now what I find
(slightly) interesting is that if I type...
IDL> print, expand_path('<IDL_DEFAULT>')
...I get the above list, but if I type the Windows counterpart of your
setenv statement, ie...
IDL> print, expand_path('+D:\Program Files\RSI\IDL62')
...I get a different order, with "examples" and its subdirectories
before "lib".
--
Mark Hadfield "Kei puwaha te tai nei, Hoea tahi tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
