| Re: Why is the content of my object graphics window being wiped? [message #84876 is a reply to message #84860] |
Sat, 15 June 2013 03:29  |
Haje Korth
Messages: 651
Registered: May 1997
|
Senior Member |
|
|
+1 for a fix from me. It's not a show-stopper but an annoyance in debugging programs. Haje
On Friday, June 14, 2013 2:13:08 PM UTC-4, Mark Piper wrote:
> On Wednesday, June 12, 2013 4:35:01 PM UTC-6, Paul van Delst wrote:
>
>> On 06/12/13 16:13, David Fanning wrote:
>
>>
>
>>> Paul van Delst writes:
>
>>
>
>>>
>
>>
>
>>>> I'm having a similar problem, but with Function graphics.
>
>>
>
>>>>
>
>>
>
>>>> I've gotten an nVidia driver installed (which apparently doesn't play
>
>>
>
>>>> nice with RHEL6). Could that be the cause of the problem?
>
>>
>
>>>>
>
>>
>
>>>> How does one set the FG equivalent of RETAIN=2?
>
>>
>
>>>
>
>>
>
>>> Really!? Can you show me an example of what you mean? I wouldn't have
>
>>
>
>>> though FG needed any retaining. I would have thought this was all being
>
>>
>
>>> handled via expose events. RETAIN is just going to get you into all
>
>>
>
>>> kinds of trouble.
>
>>
>
>>
>
>>
>
>> Sure. Take a look at:
>
>>
>
>> http://ftp.emc.ncep.noaa.gov/jcsda/CRTM/.plots/Screenshot.pn g
>
>>
>
>>
>
>>
>
>>> I'd be very curious to see what the problem looks like and what commands
>
>>
>
>>> produce it.
>
>>
>
>>
>
>>
>
>> I think the offender is
>
>>
>
>> q = get_kbrd(1)
>
>>
>
>> but that's not an issue for DG window refresh/retain and I can't recall
>
>>
>
>> it being an issue for FG in the past either. I pause to peruse and
>
>>
>
>> compare FG plots all the time.
>
>>
>
>>
>
>>
>
>> As far as I can remember (it did take an entire month to get IDL
>
>>
>
>> reinstalled on my "upgraded" computer) this is new behaviour. Whether
>
>>
>
>> it's caused by IDL v8.2.2 or by the use of the nVidia driver in RHEL6 --
>
>>
>
>> or some unholy combination of the two -- I'm trying to figure out.
>
>>
>
>>
>
>>
>
>> cheers,
>
>>
>
>>
>
>>
>
>> paulv
>
>
>
> Hi Paul,
>
>
>
> When called from the command line, NG are widget programs. So, on UNIX-based systems, if you're stopped inside a routine, the NG window won't get the expose event until you .continue the interpreter. There's a related issue when using NG in the Workbench which we're looking at repairing in IDL 8.3. We may also look at this for NG called from the command line.
>
>
>
> I would like to get this fixed because it's key to be able to visually explore data with IDL.
>
>
>
> mp
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
