[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Exceed and IDL
- Subject: Re: Exceed and IDL
- From: Liam Gumley <Liam.Gumley(at)ssec.wisc.edu>
- Date: Wed, 07 Jul 1999 11:34:44 -0500
- Newsgroups: comp.lang.idl-pvwave
- Organization: Space Science and Engineering Center, University of Wisconsin-Madison
- References: <3781382A.2B4A4755@garnet.acns.fsuMMER.edu> <3781FFBA.B34A027A@met.rdg.ac.uk> <37820941.3557AB7F@ssec.wisc.edu> <378262CC.E96@llama.pilz.cack> <37835BEB.2C1EA8BD@ssec.wisc.edu> <378368A9.40AC@llama.pilz.cack> <MPG.11ed28f44513782f989815@news.frii.com>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:15584
David Fanning wrote:
> Several obtuse reasons for setting RETAIN=0 in a draw widget
> come immediately to mind:
>
> (1) You are using object graphics in the window, in which
> case RETAIN should *always* be set to 0.
>
> (2) You know how screwy colors can be and you wish to
> protect the colors associated with this application
> by "restoring" your colors every time the widget is
> exposed.
David points out some good reasons why an IDL programmer should not
assume a particular value for RETAIN. Here's a few other values/settings
that I've learned not to take for granted when an application runs (i.e.
I don't assume any particular value).
(1) DEVICE keywords:
RETAIN
DECOMPOSED
SET_CHARACTER_SIZE
(2) System variables:
!ORDER (order for displaying images)
!D.TABLE_SIZE (size of the color table)
!D.N_COLORS (number of colors available)
!D.NAME (name of the current display device)
!D.WINDOW (index of the current graphics window)
(3) Widget appearance:
WIDGET_CONTROL keyword DEFAULT_FONT
Anyone else care to add to the list?
Cheers,
Liam.
--
Liam E. Gumley
Space Science and Engineering Center, UW-Madison
http://cimss.ssec.wisc.edu/~gumley