PRIMER 22.1

Menu Attributes: Customising Menu Size Fonts Dynamic Viewing and Handedness

As described in Selecting a Graphics Design, the scale of the menu interface, the font typeface and size, and also the left-handedness of the menu interface may be customised interactively using Options > Menu Attributes.

Gives the menu attributes panel:

Display Factor Is a factor on the overall scale of the display, lying in the range 0.5 to 2.0, default 1.0.

Larger values make the display seem bigger to the software, resulting in smaller menu panels and fonts.
Smaller values increase the size of menu panels, buttons and fonts, and can be useful for the visually impaired.

This factor can be especially useful on "wide screen" displays with very asymmetric horizontal and vertical resolutions.

The operating system should determine the physical size of the display correctly. However we have observed a few instances where this does not happen, the symptoms being that fonts and menus appear either far too big or too small and cannot be corrected by using Display Factor . In this situation you may need to tell PRIMER the physical dimensions of your display, and this process is described under "Setting the correct physical resolution for your display" in the extra section on graphics.

Font size,
quality and
scaling
The default font size normally works best, but occasionally smaller or larger fonts may look better on your display. Get the Display Factor right first, then adjust the font size if necessary.

"Proof" quality will look best on most displays. However on low resolution displays it can look a bit fuzzy due to anit-aliasing, and "Anti-alias" (which is coarser) or "Plain" (no anti-aliasing) may be preferable.

Font scaling allows text in menu interface buttons to be scaled downwards to a smaller font size (if one exists) if it is too long for the button. This shows more characters, but it can look messy when the user interface has a mixture of font sizes. Turning font scaling off prevents this happening, giving a more consistent appearance. (However it is generally better to adjust the Display Factor in order to find a menu scale that gives consistent font sizes.)

Cached fonts is an obscure setting that will only apply on Linux systems where the "core" X11 font package has not been loaded, and the software reverts to cached bitmaps. If you have font problems on Linux please contact Oasys Ltd Support for advice and help.

Font Typeface

The default for the User interface is still Helvetica for menu panels (the "Menus font") and either Courier New (Linux) or Lucida Sans Typewriter (Windows) for listings (the "Listing font"), but you can use the popup menus to select from any of the fonts on your computer. The range of fonts available will depend both on the operating system and what has been installed, but typically there can be many. To try to make the choice manageable these are separated into

Proportionally spaced fonts, where character width varies. This is preferred for GUI panels with buttons.
Monospaced fonts, where each character width is the same. This is preferred for text listings.

Within each category fonts are also sorted by weight, with "normal" being the most commonly used. "Light" options tend to be narrower, permitting more characters to fit in a button, "Heavy" options tend to use bold text, and can be useful when using very large fonts - perhaps on a projector or when setting up the user interface for someone who is visually impaired.

CJK fonts These are the C hinese, J apanese and K orean unicode fonts used for extended typeface support in JavaScript widgets. Separate descriptors are required on Unix/Linux and Windows because of the differences in the ways that fonts are handled on the two systems.
Brightness
Saturation
These affect the overall brightness and also the colour saturation of the user interface. They both lie in the range 0.0 to 1.0, default 1.0.
Left-Handed support

By default PRIMER is set up for right-handed usage, which has influence on both mouse buttons and the keyboard "meta" keys: <shift> and <ctrl>. (The left and right meta keys have different functions during dynamic viewing: see Dynamic Viewing (Using the Mouse to Change Views))

You can swap the handedness of mouse and/or meta keys, which will reverse them in the left <=> right sense.

Note : This swapping is local to PRIMER , and is applied after any system user interface configuration. So if you configure your computer to swap mouse buttons globally, then swap them here, the net effect will be to have unswapped buttons again!

Dynamic
viewing
By default PRIMER uses the following dynamic viewing keyboard + mouse key actions:
Keyboard meta key
Viewing mode
Mouse button
Viewing action
<shift>
Normal
} {
Left
Rotate in XY or Z
<ctrl>
Wireframe
} + {
Middle
Translate
<shift + ctrl>
Free edge
} {
Right
Zoom (+ve upwards)

However different users have different tastes, and users who swap between different applications find it easier if they behave in similar ways. Therefore the following permutations are available:

Viewing mode , may be assigned to keyboard meta-key(s) (ie <shift>, <ctrl> or <shift + ctrl>

Normal will use the current display mode
Wireframe only the line vectors in the current display mode
Free-edge special "free edge lines only" display mode

Dynamic rotation options , assigned to mouse buttons

Rotate XYZ traditional D3PLOT behaviour, rotates in XY if cursor's initial position is in centre 2/3rd of screen, otherwise about Z
Rotate XY rotates about screen XY only, regardless of where the cursor's initial position
Rotate Z rotates about screen Z only, regardless of cursor initial position
Rotate Sphere free rotation about any of XYZ, like grabbing a point in a virtual sphere and dragging it

Dynamic translation options, assigned to mouse buttons

Translate model follows cursor movement in screen XY plane

Zoom options, assigned to mouse buttons

Zoom (up +ve) up and to the right enlarge, down and to left reduce
Zoom (down +ve) down and to the right enlarge, up and to left reduce
Presets
These preset options configure PRIMER 's dynamic viewing controls to operate in a similar way to those of the listed programmes. The descriptions "Like (program name)" are given only for ease of reference to certain combinations of key and mouse buttons used for dynamic viewing control.

ANIMATOR is a product of GNS mbH
ANSA is a trademark of BETA CAE systems SA
HYPERMESH is a registered trademark of Altair Engineering, Inc.
MEDINA is a registered trademark of T-Systems GmbH

The configurations these produce may not match exactly the actions in the given application, but they are the best that can be achieved at the present time with the options available.

Scroll
factor
Determines the rate at which using the mouse scroll wheel to zoom in/out changes the image magnification factor. Smaller values will act more slowly, and larger ones more quickly - it is best set by experiment.
Zoom
factor
Determines how rapidly the <meta key + mouse key> dynamic zoom operations above work. Again this is best set by trial and error.
3D Mouse tuning Factors that are applied to translations/rotations when using a 3D mouse produced by 3DConnexion.
Mouse Picking Setting for the middle and right mouse button action during picking. Options available are:

Apply Selection - Apply the current selection (for example when picking nodes to create a CONSTRAINED_NODAL_RIGID_BODY, this option will create the entity (this can speed up the process of creation of many entities through picking).

Reject Last - Reject the most recent selection (middle mouse button default).

Deselect - Deselect items selected, either individually or by area (right mouse button default).

MENU_
AUTO_
CONFIRM
This is a special setting designed mainly for "batch" style usage, and it controls how "popup" windows that normally wait for acknowledgement from the user should respond.

If it is switched on then these windows will assume that the user has clicked the default action (usually "OK") and continue operation without waiting. This can be useful when replaying scripts, but it is not recommended for normal interactive usage.

Saving Menu Attributes settings

The attributes above may be saved in the "oa_pref" file by using Save_Settings . Subsequent sessions of PRIMER will pick these up and re-apply them.

For backwards compatibility these attributes may also be set using environment variables as described in Appendix M. Where conflicting settings exist those in the "oa_pref" file generated by the panel above (or by hand) will "win".

Note : Oasys LS-DYNA Environment potentially reads four "oa_pref" files when an application starts, in the following order:

(1) The OA_ADMIN directory (if present)
(2) The OA_INSTALL directory (where the software is installed)
(3) Your OA_HOME directory (by default $HOME on Unix/Linux, and %USERPROFILE%, typically C:\Documents and Settings\ user_id , on Windows)
(4) The current working directory (typically "Start in" directory on Windows)

Save_Settings in this panel updates the file (#3) above in OA_HOME, on the principle that you will have write permission there and - usually - it will not affect other users. However all "oa_pref" file settings are applied on the "last found wins" basis, so if you have file in your current directory with different settings these, being the last to be found, will "win".

Full details of all "oa_pref" file options and environment variables are given in Appendix M