|
|
| Re: compiling itools and utilities [message #38672 is a reply to message #38671] |
Wed, 24 March 2004 08:10  |
Nuno Oliveira
Messages: 75
Registered: October 2003
|
Member |
|
|
Well, seems the problem was on live_contour.sav
The case is that making that help, /source after restoring this file I don't
that procedures that idl was claiming that were missing...
At the moment, if I restore it before compile my project files, and then
make the resolve_all, and after that make IDLitResolveiTools, then I can
save as a SAV file and runs well.
IDL works in mysterious ways?
"David Fanning" <david@dfanning.com> wrote in message
news:MPG.1acb57a462788b8e989710@news.frii.com...
> Nuno Oliveira writes:
>
>> Well, I made
>>
>> lista = findfile('/rsi/idl_6.0/lib/obsolete/*.sav')
>>
>> And the files are:
>>
>> fw_load_extension.sav
>> fw_load_file.sav
>> fw_load_generic.sav
>> live_contour.sav
>> live_control.sav
>
> Oh, oh. Live tools!? I'm outa here!
>
>> After this I've compiled my project files and made the resolve_all and
>> everything's ok. But what .sav file that was about 2M has about 10M,
what is
>> not very nice.
>
> I expect you have more Live Tools than you need. (Some
> may argue that one is too many, but you get the point.)
>
>> But there is still something strange. I did the help, /source after
>> restoring those .sav files and that fw_updatewindow that missing is not
>> listed as compiled.
>
> Humm. Don't know.
>
>> But still it is not very clear to me what is going on... Shouldn't
>> resolve_all restore those files?
>
> I suppose a case could be made for this. But that is not
> how RESOLVE_ALL works at the moment. Something to bring
> up with RSI, probably.
>
>> Is this because somewhere I'm using obsolete routines?
>
> No, using these routines will certainly cause you
> problems, sooner or later, but those problems will
> be completely unrelated to the problem we are
> discussing currently. :-)
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38674 is a reply to message #38672] |
Wed, 24 March 2004 07:31 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Nuno Oliveira writes:
> Well, I made
>
> lista = findfile('/rsi/idl_6.0/lib/obsolete/*.sav')
>
> And the files are:
>
> fw_load_extension.sav
> fw_load_file.sav
> fw_load_generic.sav
> live_contour.sav
> live_control.sav
Oh, oh. Live tools!? I'm outa here!
> After this I've compiled my project files and made the resolve_all and
> everything's ok. But what .sav file that was about 2M has about 10M, what is
> not very nice.
I expect you have more Live Tools than you need. (Some
may argue that one is too many, but you get the point.)
> But there is still something strange. I did the help, /source after
> restoring those .sav files and that fw_updatewindow that missing is not
> listed as compiled.
Humm. Don't know.
> But still it is not very clear to me what is going on... Shouldn't
> resolve_all restore those files?
I suppose a case could be made for this. But that is not
how RESOLVE_ALL works at the moment. Something to bring
up with RSI, probably.
> Is this because somewhere I'm using obsolete routines?
No, using these routines will certainly cause you
problems, sooner or later, but those problems will
be completely unrelated to the problem we are
discussing currently. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38675 is a reply to message #38674] |
Wed, 24 March 2004 07:14 |
Nuno Oliveira
Messages: 75
Registered: October 2003
|
Member |
|
|
Well, I made
lista = findfile('/rsi/idl_6.0/lib/obsolete/*.sav')
And the files are:
fw_load_extension.sav
fw_load_file.sav
fw_load_generic.sav
live_contour.sav
live_control.sav
live_destroy.sav
live_export.sav
live_image.sav
live_info.sav
live_line.sav
live_load.sav
live_oplot.sav
live_plot.sav
live_print.sav
live_rect.sav
live_style.sav
live_surface.sav
live_text.sav
then:
for i = 0, n_elements(lista)-1 do restore, lista(i)
After this I've compiled my project files and made the resolve_all and
everything's ok. But what .sav file that was about 2M has about 10M, what is
not very nice.
But there is still something strange. I did the help, /source after
restoring those .sav files and that fw_updatewindow that missing is not
listed as compiled.
Now I'm going restore one by one and try to see which file fixes the
problem.
I'm going to start from that fw_load_extension.sav
But still it is not very clear to me what is going on... Shouldn't
resolve_all restore those files? Is this because somewhere I'm using
obsolete routines?
Cheers,
Nuno.
"David Fanning" <david@dfanning.com> wrote in message
news:MPG.1acb4c8d1eacc66298970f@news.frii.com...
> Nuno Oliveira writes:
>
>> I don't what SOBs are, :(
>
> It's a term of affection, used for close colleagues. :-)
>
>> What I saw from that help, /source is that many from are compiled from
the
>> fw_load_file.sav file. So I don't have access to the code.
>
> Ah, well. Here we are!
>
> If you are doing this by hand, you will have to restore
> all the save files *before* you compile your program.
> Then I don't think you will have any problem with the
> RESOLVE_ALL.
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38676 is a reply to message #38675] |
Wed, 24 March 2004 06:43 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Nuno Oliveira writes:
> I don't what SOBs are, :(
It's a term of affection, used for close colleagues. :-)
> What I saw from that help, /source is that many from are compiled from the
> fw_load_file.sav file. So I don't have access to the code.
Ah, well. Here we are!
If you are doing this by hand, you will have to restore
all the save files *before* you compile your program.
Then I don't think you will have any problem with the
RESOLVE_ALL.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38677 is a reply to message #38676] |
Wed, 24 March 2004 06:34 |
Nuno Oliveira
Messages: 75
Registered: October 2003
|
Member |
|
|
I don't what SOBs are, :(
What you are saying is that some functions IDL use can be named not
properly? That would mean that if someone else use the functions I'm using
should get the same problem. Is that it?
You say that maybe FW_UPDATEDATAWINDOW and FW_QUERYDEFAULTSTYLE are routines
from a file with a different name when they should be the last program of
the file and so giving the file his name?
What I saw from that help, /source is that many from are compiled from the
fw_load_file.sav file. So I don't have access to the code.
Thanks (again).
Cheers,
Nuno.
"David Fanning" <david@dfanning.com> wrote in message
news:MPG.1acb43c466d6801e98970d@news.frii.com...
> Nuno Oliveira writes:
>
>
> Well, then I guess I'm back to improper naming.
> But, it's not your fault. Blame those SOBs you
> got that code from! :-)
>
> Compile the programs from your project. Then type
> this:
>
> IDL> Help, /Source
>
> Examine the list (it will probably be a long one) to
> see where these files are. Take them out of whatever
> file they are in and name them correctly. Shouldn't
> take more than a day or two. :-)
>
> Cheers,
>
> David
>
> --
> David Fanning, Ph.D.
> Fanning Software Consulting
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38680 is a reply to message #38677] |
Wed, 24 March 2004 06:06 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Nuno Oliveira writes:
> Those functions, that it says that are undefined, are not my functions. I
> was thinking they were some internal function. There are any suggestions for
> a debug action? How can I do something that allows me to see how and where
> these functions appear?
Well, then I guess I'm back to improper naming.
But, it's not your fault. Blame those SOBs you
got that code from! :-)
Compile the programs from your project. Then type
this:
IDL> Help, /Source
Examine the list (it will probably be a long one) to
see where these files are. Take them out of whatever
file they are in and name them correctly. Shouldn't
take more than a day or two. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38681 is a reply to message #38680] |
Wed, 24 March 2004 02:53 |
Nuno Oliveira
Messages: 75
Registered: October 2003
|
Member |
|
|
Those functions, that it says that are undefined, are not my functions. I
was thinking they were some internal function. There are any suggestions for
a debug action? How can I do something that allows me to see how and where
these functions appear?
My project directories are in IDL path.
Cheers,
Nuno.
"David Fanning" <david@dfanning.com> wrote in message
news:MPG.1aca26459b35486f989709@news.frii.com...
> Nuno Oliveira writes:
>
>> Yes, the last program is always the program that gives the name to the
>> file.This is getting weird. For you see how strange this is, forget for
one
>> moment the question about iTools. This happens to me also for
resolve_all.
>> For what I've just saw, when use the files within the project and use
the
>> option BUILD everything goes well. But if pick all the files and compile
it
>> individually and the use the command resolve_all I get that message that
>> I've already post. Do you imagine what this could be? I'm a little bit
>> confused.
>
> Are these files (e.g., FW_UPDATEDATAWINDOW) ones that you
> created? Are the project directories on your IDL path?
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38689 is a reply to message #38681] |
Tue, 23 March 2004 09:48 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Nuno Oliveira writes:
> Yes, the last program is always the program that gives the name to the
> file.This is getting weird. For you see how strange this is, forget for one
> moment the question about iTools. This happens to me also for resolve_all.
> For what I've just saw, when use the files within the project and use the
> option BUILD everything goes well. But if pick all the files and compile it
> individually and the use the command resolve_all I get that message that
> I've already post. Do you imagine what this could be? I'm a little bit
> confused.
Are these files (e.g., FW_UPDATEDATAWINDOW) ones that you
created? Are the project directories on your IDL path?
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38690 is a reply to message #38689] |
Tue, 23 March 2004 09:26 |
Nuno Oliveira
Messages: 75
Registered: October 2003
|
Member |
|
|
Yes, the last program is always the program that gives the name to the
file.This is getting weird. For you see how strange this is, forget for one
moment the question about iTools. This happens to me also for resolve_all.
For what I've just saw, when use the files within the project and use the
option BUILD everything goes well. But if pick all the files and compile it
individually and the use the command resolve_all I get that message that
I've already post. Do you imagine what this could be? I'm a little bit
confused.
"David Fanning" <david@dfanning.com> wrote in message
news:MPG.1aca1bc9e2649ed4989707@news.frii.com...
> Nuno Oliveira writes:
>
>> I try as you said. But I still get problems! The program I want to run
is in
>> a project. I try the two ways possible. In one case I compiled the
programs
>> of the project first of the project and then did the IDLitResolveiTools.
The
>> other case I did the opposite.
>>
>> For each case I get a different error message, but always in the same
place.
>> I hope it is not a installation problem. Anyone has a clue about what's
>> going on?
>
> Are these programs *named* properly? That is, the name of the
> program file is the same as the *last* program module in the file?
> Improper naming is the culprit in the vast majority of these
> cases:
>
> http://www.dfanning.com/tips/namefiles.html
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38692 is a reply to message #38690] |
Tue, 23 March 2004 09:03 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Nuno Oliveira writes:
> I try as you said. But I still get problems! The program I want to run is in
> a project. I try the two ways possible. In one case I compiled the programs
> of the project first of the project and then did the IDLitResolveiTools. The
> other case I did the opposite.
>
> For each case I get a different error message, but always in the same place.
> I hope it is not a installation problem. Anyone has a clue about what's
> going on?
Are these programs *named* properly? That is, the name of the
program file is the same as the *last* program module in the file?
Improper naming is the culprit in the vast majority of these
cases:
http://www.dfanning.com/tips/namefiles.html
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38694 is a reply to message #38692] |
Tue, 23 March 2004 08:17 |
Nuno Oliveira
Messages: 75
Registered: October 2003
|
Member |
|
|
I try as you said. But I still get problems! The program I want to run is in
a project. I try the two ways possible. In one case I compiled the programs
of the project first of the project and then did the IDLitResolveiTools. The
other case I did the opposite.
For each case I get a different error message, but always in the same place.
I hope it is not a installation problem. Anyone has a clue about what's
going on?
Cheers,
Nuno.
This was for one case.
IDL> IDLitResolveiTools
% Attempt to call undefined procedure/function: 'FW_UPDATEDATAWINDOW'.
% Error occurred at: RESOLVE_ALL_BODY 280
/usr/local/rsi/idl_6.0/lib/resolve_all.pro
% RESOLVE_ALL 331
/usr/local/rsi/idl_6.0/lib/resolve_all.pro
% IDLITRESOLVEITOOLS 62
/usr/local/rsi/idl_6.0/lib/itools/framework/idlitresolveitoo ls.pro
% $MAIN$
% Execution halted at: IDLITRESOLVEITOOLS 62
/usr/local/rsi/idl_6.0/lib/itools/framework/idlitresolveitoo ls.pro
% Attempt to call undefined procedure/function: 'FW_QUERYDEFAULTSTYLE'.
% Error occurred at: RESOLVE_ALL_BODY 280
/usr/local/rsi/idl_6.0/lib/resolve_all.pro
% RESOLVE_ALL 332
/usr/local/rsi/idl_6.0/lib/resolve_all.pro
% $MAIN$
% Execution halted at: $MAIN$
and for the other.
IDL> resolve_all
% Restored file: LIVE_DESTROY.
% Compiled module: SLICER3.
% Compiled module: WRITE_IMAGE.
% Compiled module: XLOADCT.
% Compiled module: XVOLUME.
% Compiled module: COLORMAP_APPLICABLE.
% Compiled module: CW_DEFROI.
% Compiled module: CW_RGBSLIDER.
% Compiled module: DIALOG_READ_IMAGE.
% Compiled module: DIALOG_WRITE_IMAGE.
% Attempt to call undefined procedure/function: 'FW_QUERYDEFAULTSTYLE'.
% Error occurred at: RESOLVE_ALL_BODY 280
/usr/local/rsi/idl_6.0/lib/resolve_all.pro
% RESOLVE_ALL 332
/usr/local/rsi/idl_6.0/lib/resolve_all.pro
% $MAIN$
% Execution halted at: $MAIN$
"David Fanning" <david@dfanning.com> wrote in message
news:MPG.1ac9e74c31b84918989706@news.frii.com...
> Nuno Oliveira writes:
>
>
> You need to know about the undocumented file IDLitResolveITools:
>
> http://www.dfanning.com/itool_tips/runtime.html
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: compiling itools and utilities [message #38695 is a reply to message #38694] |
Tue, 23 March 2004 05:19 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Nuno Oliveira writes:
> I'm trying to make a .sav file from which I can call some itools and
> utilities. I add the corresponding .pro files (in the case, xvolume.pro and
> ivolume.pro) to a project that I build (and that includes /resolve all). But
> when I try to run it, I get an error, because he needs all the procedures
> that itools and utilities call, like the ones related to creation of
> objects.
>
> Do I need to compile explicitly all the procedures that are associated to
> itools? Or there is another way to get itools on a .sav file to call from
> virtual machine?
You need to know about the undocumented file IDLitResolveITools:
http://www.dfanning.com/itool_tips/runtime.html
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
