Karma Home Page
Next: D Annotation File Format
Up: Karma User Manual
Previous: B Setting up
All the GUI visualisation tools define a number of resources
which control the appearance and functionality of the tools. Many of
these resources are common to other non-visualisation programmes for
the X Window system, such as the <xterm> programme. Listed
below are those resources which are specific to Karma visualisation
tools. These resources may be set in your 
/.Xdefaults
file, which is the standard file into which to put your personal
resources. Some systems use the non-standard /.Xresources
file instead, although the format is the same. On SGI systems you may
need to put your Karma resources in a separate file and run:
xrdb -merge <filename>
in your window system startup script. You
may also/instead (on SGI systems) need to set resources in your
/.Sgiresources file.
In some cases you will need to prepend the application classname
(i.e. Kvis) to the resource name. First try specifying the
particular resource as shown and if that doesn't work prepend the
application classname.
- *ZoomPolicy.fixAspect this controls whether the
aspect ratio will be fixed (True) or not (False)
- *ZoomPolicy*integerXZoomToggle.state this controls whether
horizontal zooming will be forced to integer multiples (True)
or not (False)
- *ZoomPolicy*integerYZoomToggle.state this controls whether
vertical zooming will be forced to integer multiples (True) or
not (False)
- *IntensityPolicy*resetIntensityToggle.state this controls
whether the intensity range will be reset upon loading of a new file
(True) or not (False)
- *iscaleMenu*setChoice this controls the default
intensity transformation. The folowing are supported:
- linear the screen intensity is proportional to the input
data values
- log(val-min) the screen intensity is proportional to the
logarithm of the input data values
- log(max-val) the screen intensity is proportional to the
logarithm of the negative input data values
- sqrt(val-min) the screen intensity is proportional to the
square root of the input data values
- *MagnifierPopup.fastPanner this controls whether the
magnifier window will use a fast, large-memory mode (True) or
not (False) panner. The default is to use the slower,
small-memory panner. In most cases the default mode is quite fast
enough, unless you enlarge the magnifier window so it nearly fills
your screen. The reason the default is to use the small-memory mode is
that if you have a large image (say 2k*2k) then the fast mode would
require 64 MBytes of RAM just to store one copy of the image! Unless
you have lots of RAM in your computer, you will be forced to wait a
long time while your machine swaps to disc, hence the default
- *ImageDisplay.fastPanner as above, but applies to the main
image window. The default is to use the fast, large-memory
panner. This is only of significance when you use panning mode
(i.e. select ``Panner'' from the ``Zoom'' menu)
- *MagnifierPopup.showCrosshair this controls whether
magnifier windows should show a crosshair (True) or not (
False)
- *displayAxisLabelsToggle.state if this is True then
most windows which support axis labels will have enabled them by
default. You also need to set the *OverlayMenu.createAtInit
resource to True (see below)
- *OverlayMenu.createAtInit if this is True then
creation of certain control panels is performed at programme startup,
rather than being delayed until if (and when) required. Normally,
delayed creation is preferred, since it speeds application startup,
but this prevents some resource specifications from taking effect
until sometime later. Some programmes provide the shorthand ``
-create_at_init'' option
- *transient if True all popup windows will be
iconified if the main window is iconified
- *AnimateControl*pinToggle.state this controls
whether the animation control will be stay popped up when an image is
displayed (True) or will be popped down (False)
- *AnimateControl.transient as above but specifically only
for the AnimateControl widget (section 2.3)
- *Cmapwinpopup.transient as above for the
Cmapwinpopup widget (section 2.2)
- *Dataclip.transient as above for the
Dataclip widget (section 2.2)
- *Dataclip*subsetToggle.state this controls whether a
subset of the input data will be used to compute a histogram for the
Dataclip widget (section 2.2)
- *Dialogpopup.transient as above for the
Dialogpopup widget
- *DressingControl.transient as above for the
DressingControl widget (section 2.8)
- *Filepopup.transient as above for the
Filepopup widget (section 2.1)
- *Filepopup*dotsToggle.state control whether (True)
or not (False) hidden files and directories are shown by default
in the Filepopup widget (section 2.1)
- *Filewin.numLines the desired size of the directory
browser (in lines). The default is that the browser size is
automatically configured
- *Filewin*list.translations may be used to change the file
browser mouse behaviour. The default is to highlight the entry under
the current mouse pointer position. If you specify
<Btn1Down>:Set()
n<Btn1Up>:Notify() then highlighting only
occurs when an entry has been selected. The only advantage of this
behaviour is that it leaves the last selected entry highlighted
(i.e. moving the mouse won't highlight a different entry)
- *IntensityPolicy.transient as above for the
IntensityPolicy widget (section 2.2)
- *LoadAndDecimate.transient as above for the
LoadAndDecimate widget (section 2.1.1)
- *MagnifierPopup.transient as above for the
MagnifierPopup widget (section 2.9)
- *MomentGenerator.transient as above for the
MomentGenerator widget (section 2.16)
- *OverlayEditorControl.transient as above for the
OverlayEditorControl widget (section
2.19)
- *PannerPopup.transient as above for the
PannerPopup widget (section 2.10)
- *Postscript.transient as above for the
Postscript widget (section 2.4)
- *SlaveImageDisplayPopup.transient as above for the
SlaveImageDisplayPopup widget
- *TracePopup.transient as above for the
TracePopup widget (section 2.11)
- *View2Datasets.transient as above for the
View2Datasets widget (section 4)
- *ZoomPolicy.transient as above for the
ZoomPolicy widget (section 2.7)
- Kvis.geometry the size and placement of the main display
window for <kvis>. The default is +0+0 (top left)
- Kvis*firstDataBrowserShell.geometry the size and placement
of the first data browser window for <kvis>. The default is
+540-0 (to the right of the main display window and at the
bottom of the screen)
- Kvis*imageDisplayShell1.geometry the size and placement
of the second display window for <kvis>. The default is
-0+0 (top right)
- *Postscript*nameDialog*font the name of the font to use in
the text-entry dialog for the output filename in the
Postscript widget (section 2.4)
Karma Home Page
Next: D Annotation File Format
Up: Karma User Manual
Previous: B Setting up
Richard Gooch
Mon Aug 14 22:25:04 PDT 2006