| iimage tool [message #39896] |
Tue, 15 June 2004 07:10  |
Francois
Messages: 8
Registered: May 2004
|
Junior Member |
|
|
Hello,
I am trying to use the iimage tool.
When I start it like this, it works fine:
1) IDL> iimage
2) browse and open my file.
When I launch it in my code, then it jams:
1) ar = read_tiff('C:\image.tif')
2) iimage, ar
Is this normal ?
Thank you,
Francois Leduc
|
|
|
|
| Re: iimage tool [message #39948 is a reply to message #39896] |
Wed, 23 June 2004 20:16  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Mark Hadfield writes:
> Have you noticed that FSC_SURFACE exhibits the behaviour? :-)
Humm. No, I *hadn't* noticed this. Weird, isn't it. :-)
>
> The no-event-handling-while-waiting-at-a-breakpoint issue applies to all
> (non-blocking) widget programs. Some will display a graph in this
> situation, some will show an empty window (probably waiting for an
> expose event), but in all cases you can't interact with them because the
> widget queue is stopped.
Yes, I think this is waiting for an expose event. It is odd
when certain things happen and when they don't. I was surprised
the other day when a notify realize happened *immediately*
when the widget was created, before I had actually saved the
widget id in my object. I recall another problem with a
CleanUp routine being called in a different order under
Windows than it was in UNIX. That frustrated me for a day
or so.
> This has frustrated me for some time.
Really!? I would have thought there wasn't much that
could happen in IDL that I haven't been frustrated about
at one time or another, but I have to admit this "problem"
has never shown up on my radar screen.
> When I stop a program at a
> breakpoint I want to be able to make use of the full range of
> visualisation tools, not just blocking widgets and non-widget commands.
I guess here is the difference between us. When I stop a program
it is to figure out what dumb ass mistake I have made, not to use
the full power of IDL visualization. :-)
> Based on Daryl Attencio's code, I came up with the routine below
> (currently called MGH_YIELD, but I'm sure there's a better name).
Well, I have to admit this is neat. I'm just trying to figure
out if I can upgrade my programming enough to make it useful. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: iimage tool [message #39950 is a reply to message #39896] |
Wed, 23 June 2004 19:24 |
Mark Hadfield
Messages: 783
Registered: May 1995
|
Senior Member |
|
|
Mark Hadfield wrote:
> Based on Daryl Attencio's code, I came up with the routine below
> (currently called MGH_YIELD, but I'm sure there's a better name).
I've changed it to a script, with the following, all on one line:
while 1 do begin & wait, 0.1 & void = widget_event(/NOWAIT) & endwhile
When this is interrupted with Ctrl-Break, IDL returns to the point where
the script was invoked.
--
Mark Hadfield "Ka puwaha te tai nei, Hoea tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
