| Re: Creating a Run-Time IDL Application [message #13528] |
Thu, 19 November 1998 00:00 |
Dick Jackson
Messages: 347
Registered: August 1998
|
Senior Member |
|
|
Eric Frans wrote:
> My goal is to get an IDL widget application to launch by simply double
> clicking on an icon and have no evidence of the IDL Development
> Environment in the background.
>
> I have successfully used this process on one widget application and I
> was extremely pleased. However, I tried the same methodology on some
> other widget applications and when I double click on the .sav icon, all
> I see is the "Runtime App" icon appear on my windows (95) toolbar for a
> few seconds and then disappear without ever launching the widget
> application. Has anyone else experienced this?
Quick check: is there a blank (' ') character anywhere in your .sav
file's path? (I know, you're thinking "What an odd question!" :-)
If so, you have stumbled on a bug in IDL Runtime for Windows that I
came across a little while back. The bug was still there in IDL 5.2b1,
but I was told that it was going to be in 5.2 final, and indeed it
seems to be fixed in 5.2b2. For now, of course, you can remove any
blanks in enclosing directory names, if that isn't too inconvenient.
Hope this helps!
Cheers,
--
-Dick
Dick Jackson Fanning Software Consulting, Canadian Office
djackson@dfanning.com Calgary, Alberta Voice/Fax: (403) 242-7398
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: Creating a Run-Time IDL Application [message #13530 is a reply to message #13528] |
Thu, 19 November 1998 00:00  |
Eric Frans
Messages: 13
Registered: October 1998
|
Junior Member |
|
|
David Fanning wrote:
>
> I've just been fooling around a bit, trying to get a
> program to fail in the way yours does. I can't seem to
> do it. :-)
>
> My *guess* is that not all the procedures and functions
> required by the function have been compiled and saved
> with the save file. (You are sure you used Resolve_All
> and that you hand-compiled things like objects and
> maybe structure definition files?) My other guess is
> that maybe you have hardcoded paths into the program
> and these paths are not valid from where the program
> is being run.
> I don't know. I need more clues. :-)
Thanks for the reply.
No paths are hardcoded in the procedure. However, after trying the
process again on the same widget application, it looks like the
following built-in IDL functions/procedures are not being compiled after
using Resolve_All: string, eof, strmid, fix, ishift, dialog_pickfile,
fstat and systime. Do all these need to be hand compiled? I was unable
to find any of these in the IDL library directories, though. I assume
they are embedded somewhere.
- Eric Frans
|
|
|
|
| Re: Creating a Run-Time IDL Application [message #13549 is a reply to message #13528] |
Wed, 18 November 1998 00:00 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Eric Frans (epfrans@west.raytheon.com) writes:
> My goal is to get an IDL widget application to launch by simply double
> clicking on an icon and have no evidence of the IDL Development
> Environment in the background.
>
> I have successfully used this process on one widget application and I
> was extremely pleased. However, I tried the same methodology on some
> other widget applications and when I double click on the .sav icon, all
> I see is the "Runtime App" icon appear on my windows (95) toolbar for a
> few seconds and then disappear without ever launching the widget
> application. Has anyone else experienced this?
>
> I suspect the reason for this anomaly is due to slight differences in
> the way the widget applications were coded. Admittedly, I am new to the
> world of widgets, so I may have left off a keyword or something so the
> auto launch method isn't working. However, the widget applications I am
> having problems with launching from a .sav icon work perfectly when run
> in the IDL Development Environment manually...
I've just been fooling around a bit, trying to get a
program to fail in the way yours does. I can't seem to
do it. :-)
My *guess* is that not all the procedures and functions
required by the function have been compiled and saved
with the save file. (You are sure you used Resolve_All
and that you hand-compiled things like objects and
maybe structure definition files?) My other guess is
that maybe you have hardcoded paths into the program
and these paths are not valid from where the program
is being run.
I don't know. I need more clues. :-)
Cheers,
David
[Note: This follow-up was e-mailed to the cited author.]
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
