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

Home » Public Forums » archive » Re: New Colorbar Missing?
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: New Colorbar Missing? [message #72701 is a reply to message #72688] Sun, 26 September 2010 09:03 Go to previous messageGo to previous message
Jeremy Bailin is currently offline  Jeremy Bailin
Messages: 618
Registered: April 2008
Senior Member
On Sep 25, 2:14 pm, "R.G. Stockwell" <noem...@please.com> wrote:
> "David Fanning" <n...@dfanning.com> wrote in message
>
> news:MPG.2707af52e7d3fd069897f3@news.giganews.com...
>
>
>
>
>
>> Folks,
>
>> I start a new IDL session and type this:
>
>> IDL> graphic = colorbar(rgb_table=5)
>> % Compiled module: COLORBAR.
>> % Attempt to call undefined procedure/function: 'COLORBAR'.
>> % Execution halted at: $MAIN$
>> IDL> Print, !version
>> { x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010   64      64}
>
>> Any ideas!? This is a complete mystery to me. :-(
>
>> I have a COLORBAR *procedure* in the Coyote Library, and
>> that is on the path ahead of the <DEFAULT> IDL libraries,
>> but IDL has always been able to tell the difference between
>> a procedure and a function.
>
>> Clearly that procedure got compiled:
>
>> IDL> Help, /source
>> Compiled Procedures:
>> $MAIN$
>> COLORBAR                  C:\IDL\coyote\colorbar.pro
>
>> Compiled Functions:
>> FSC_COLOR                 C:\IDL\coyote\fsc_color.pro
>> FSC_COLOR_COLOR24         C:\IDL\coyote\fsc_color.pro
>> FSC_COLOR_COUNT_ROWS      C:\IDL\coyote\fsc_color.pro
>
>> Why is IDL getting confused here? Am I going to have
>> to rename most of the routines in my Coyote Library?
>
>> 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.")
>
> I don't know if this is relevant, but I have noticed that any text after the
> "end" statement
> in a pro file, causes this error message exactly.
>
> I run into that all the time, debuging some code, or just doing some data
> exploration, where
> I have a main level script that reads data, analyzes data makes some plots.
>
> I often want to just stop the code at a point, and examine a data product.
> It used to be
> very convenient to just drop an end in the middle of the code, to end the
> program and return
> to the main level.   alas, no more.
>
> cheers,
> bob
>
> PS even if everything is commented out after the 'end', it still causes that
> error

You could use stop and then do a return as soon as it quits to get
back to the main level.

-Jeremy.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: mpfit questions /strange behavior
Next Topic: IDL_IDLBridge and IDL8

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

Current Time: Sat Oct 11 22:01:16 PDT 2025

Total time taken to generate the page: 1.44716 seconds