comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Weird IDL problem?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Weird IDL problem? [message #58823]

Mon, 25 February 2008 09:11

Dave[4]
Messages: 38
Registered: December 2007

Member

Guys:
I use IDL 7.0 + windows. When I run example
"elevation_object.pro", I close the workbench firstly and the
"xobjview" and "IDL Object Window 32" windows is not dissapear at the
same time. So I shut down the those windows, and open "windows task
magnager"(ctrl+alt+delete) and find the processes "idlde.exe",
"idl_opserver.exe" still exists. Why?

dave

Report message to a moderator

Re: Weird IDL problem? [message #58892 is a reply to message #58823]

Tue, 26 February 2008 07:53

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

Chris Torrence writes:

> If you wait a few seconds (say 5), do the IDL windows eventually go
> away by themselves?

They don't on my Windows machine.

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.")

Report message to a moderator

Re: Weird IDL problem? [message #58895 is a reply to message #58823]

Tue, 26 February 2008 07:45

chris_torrence@NOSPAM is currently offline

chris_torrence@NOSPAM
Messages: 528
Registered: March 2007

Senior Member

Hi Dave,

If you wait a few seconds (say 5), do the IDL windows eventually go
away by themselves?

In IDL 7.0, if the IDL Workbench goes away, then the IDL out-of-
process (OPS) should wake up and notice that the Workbench is gone,
and then finally shut itself down. This should take down your graphics
windows. However, there is currently a bug where sometimes the IDL OPS
can hang during shutdown, and then nothing will exit.

This should be fixed in the next IDL Workbench update.

Cheers,
Chris
ITTVIS

Report message to a moderator

Re: Weird IDL problem? [message #58906 is a reply to message #58823]

Tue, 26 February 2008 05:22

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

Dave writes:

> I use IDL 7.0 + windows. When I run example
> "elevation_object.pro", I close the workbench firstly and the
> "xobjview" and "IDL Object Window 32" windows is not dissapear at the
> same time. So I shut down the those windows, and open "windows task
> magnager"(ctrl+alt+delete) and find the processes "idlde.exe",
> "idl_opserver.exe" still exists. Why?

This looks like a bug to me. Have you talked to the folks
at ITTVIS?

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.")

Report message to a moderator

Re: Weird IDL problem? [message #58943 is a reply to message #58895]

Wed, 27 February 2008 12:29

elwood
Messages: 23
Registered: February 2007

Junior Member

I see this bug virtually every time I teach my numerical physics
class (3 times a week).
The students have to go into windows taskmanager and end the idl
process.
It doesnt close itself down even if you wait around.
I miss IDL6.4, never had this kind of problem with it.

On Feb 26, 9:45 am, Chris Torrence <gorth...@gmail.com> wrote:
> Hi Dave,
>
> If you wait a few seconds (say 5), do the IDLwindowseventually go
> away by themselves?
>
> In IDL 7.0, if the IDLWorkbenchgoes away, then the IDL out-of-
> process (OPS) should wake up and notice that theWorkbenchis gone,
> and then finally shut itself down. This should take down your graphicswindows. However, there is currently a bug where sometimes the IDL OPS
> can hang during shutdown, and then nothing will exit.
>
> This should be fixed in the next IDLWorkbenchupdate.
>
> Cheers,
> Chris
> ITTVIS

Report message to a moderator

Previous Topic:	Object Graphics Vector Output
Next Topic:	itools vertical colorbar bug

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 15:11:33 PDT 2025

Total time taken to generate the page: 0.01141 seconds