Xaaes.cnf

From SpareMiNT Wiki
Jump to: navigation, search

Contents

xaaes.cnf

This lets you set several runtime-options for XaAES and its clients and start programs at start-up. It uses mostly the same syntax as is used in mint.cnf. Have a look at the xaaes.cnf example file. how it should look like.

Commands are not case sensitive unless otherwise mentioned.

If a command isn't understood, it gets ignored.


Global Commands

Default values are false for bool, 0 for numbers or empty for strings unless otherwise mentioned.


  • LAUNCHPATH <character-sequence>


Define the initial directory that is opened by the XaAES-launcher to start programs. A pattern to select typical executable files may be appended.

Example: launchpath = u:\usr\gem\|*.prg|*.app|!*.*|*.acc

See also: XaAES-Pattern-Matching

  • CLIPBOARD <character-sequence> (default c:\clipbrd)

Set the GEM clipboard to be in <directory>

  • SNAPSHOT <character-sequence> define snapshot-program

The external snapshot is called with the arguments: '0 T 1 [x y w h]' where

T=0: full screen, T=2: top window

If x, y, w, h are provided, this rectangle should be snapped. If XaAESSnap is not loaded, the external program that is defined in xaaes.cnf for snapshots is called, if present.


  • ACCPATH <character-sequence>

Set the location that XaAES will try to load accessories from (default is c:\). When ACCPATH is present in the Environment this precedes the config-variable.

  • RESOURCE <character-sequence> main resource filename (default xaaes009.rsc)

See Resource-Files

  • WIDGETS <character-sequence> widgets resource filename (default xaaeswdg.rsc)


  • USEHOME <bool>

use $HOME in shell_find

  • NAES_COOKIE <bool>

fake nAES cookie


  • MENUPOP_PIDS <bool>

Setting menupop_pids = true makes XaAES list its clients in the client-list- menupopup using the following format;

" PPID(RPPID) -> PID Client nice name"

where 'PPID' is the physical parent-pid of the Client (which is the AESSYS). 'RPPID' is the Process ID of the process that called shel_write() to start it, it is the "Real Parent PID". 'PID' is the Process ID of the client. If set to 'no' (the default), only the client's nice name (when available, else its 'proc_name') is listed.


  • LRMB_SWAP <bool>

Swap left and right mouse buttons. Setting 'lrmb_swap = true' will make XaAES swap the left and right mouse buttons.

  • WIDGET_AUTO_HIGHLIGHT <bool>

When widget_auto_highlight is set true, standard window widget are automatically highlighted when mouse hovers over them. This is still very experimental, and widgets are not actually highlighted, they are just animated - that is redrawn in SELECTED status.

  • REMAP_CICONS <bool>

Use the palette defined in the resource to remap icons.

  • SET_RSC_PALETTE <bool>

Use the palette defined in the resource as screen-palette.

  • ALERT_WINDOWS <bitmask> default 0xffff

alert_window is a bitmask indicating which alerts coming via the alert pipe will be shown in a window. The idea is that this mask is used to tell the AES which alerts you want like this; bit 0 set -> show alerts with no icon bit 1 set -> show alerts with INFO icon bit 2 set -> show alerts with QUESTION icon bit 3 set -> show alerts with STOP icon etc., etc.

Because there is no consideration as to which icon is used (for example, kernel's PROCESS KILLED alerts have icon #1, the same as used for other warnings/informative ALERTS), the implemention is not complete. So for now use this to either turn off or on alerts altogether. To turn on alert windows, use a mask where all bits are set, y0xffff, and to turn off clear all bits, 0x0000

THE IMPLEMENTATION IS NOT DEFINATE AND ONLY PARTIAL AS OF NOW


  • FONT_ID <number> (default 1)

Standard GDOS fontid for windows & stuff

  • STANDARD_POINT <number> (default 10)

Size of the 'standard' AES font (for window titles, etc), high resolution

  • MEDIUM_POINT <number> (default 9)

Size of the 'standard' AES font (for window titles, etc), low resolution

  • SMALL_POINT <number> (default 8)

Size of the 'small' AES font.


  • POPSCROLL <number> (default 0)

Set number of lines of a popup above which it will be made scrollable

  • DC_TIME <number/ms> (default 50)

double click time (ms)


  • MP_TIMEGAP <number/ms> (default 3)

Mouse packet time-gap. This is the time (in 200hz timer ticks) that must pass after a button-release event before a new button-press event is accepted by moose.adi. Because of unstable mouse-buttons, a button-press may follow immediately after a button-release, creating an "extra" mouse-click. This is especially annoying when releasing the right-button after a drag-session (Thing's directory-window, for example), and the "extra-click" fires some unwanted action.

  • VIDEO <number> (default 1)

See Video-Modes

  • REDRAW_TIMEOUT <number/ms> (default 500)

This is the time in ms XaAES will wait for clients to service WM_REDRAW messages between actions that generate redraws, like moving/closing/opening/etc. windows. If a client is busy and this 'timeout' happens, it is marked as lagging and XaAES will service the redraws for it. When this happens, XaAES just draws the areas not serviced with dark gray color until the client re-enters evnt_multi(). For slow machines, this timeout must be higher (longer) than on faster machines.

  • POPUP_TIMEOUT <number/ms> (default = 10)

Time in milliseconds before popups open.

  • POPOUT_TIMEOUT <number/ms> (default 1000)

Time in milliseconds before popups close.

  • SETENV

same as for mint.cnf

  • NEXT_ACTIVE <'client' or 'window'> (default 'window')

Selects wether the previous active application or the owner of the previous topped (or only) window should be set active upon client termination.

  • CLOSE_LASTWIND <'client' or 'window'> (default 'window')

DEPRECIATED - OBSOLETE close_lastwind = 'client' or 'window' (default is 'window')

Selects what to do when the last window of a client is closed.

Setting to 'client' will keep the application whose last window is closed as the top application. This prevents XaAES from putting infront another application when the last window of the application currently infront is closed.

Setting to 'window' will make XaAES put the application who owns the foremost window infront, making it active. This is the normal behaviour done by other AES's we thinks.


  • APP_OPTIONS <string>

See Commands for XaAES-clients.

  • CANCEL <comma-separated string-list>

List of words that XaAES interpretes as Cancel. A button containing a word from this list in a dialog or alert will be selected if Undo is pressed.

  • FILTERS <comma-separated string-list>

List of patterns that will be contained in the filter-menu of the fileselector. See also: XaAES-Pattern-Matching.

  • CTLALTA_SURVIVORS <comma-separated string-list>

The strings are the filename part of the program file, padded with spaces to fit 8 characters. This is NOT the 'nice' name. So, if your Toswin2 binary is named "tw2.app", you use "tw2 ". Each app-name is separated with comma. This will allow you to specify which applications XaAES does not attempt to terminate when user presses CTRL-ALT-A to quit all applications. Normally, this keycombo quits all running applications leaving only XaAES. However, most of the time, keeping certain applications running is preferred, such as the desktop, the taskbar, av-server application, etc, etc. One special name is '_aes_shell_', which will prevent XaAES from terminating the desktop loaded via "shell = " configuration variable. One can still use the name of the desktop program if it is konwn, but an easier way is to use '_aes_shell_', as that will work without further configuration modifications when one changes desktop from, say, Thing to Jinnee. If you want to bypass this setting, and quit ALL applications, leaving only XaAES, you can press ctrl-alt-shift-a.

The following will keep the desktop, taskbar and toswin2 running after a ctrl-alt-a action:

cltalta_survivors = "_aes_shell_", "taskbar ", "toswin2 "

Applications that do not act on AP_TERM will also survive.

  • KILL_WO_QUESTION <comma-separated string-list>

Applications found in this list will be killed immediately during shutdown. The same rule as for CTLALTA_SURVIVORS applies to the strings

  • ?MENU <'pull', 'push', 'leave', or 'nolocking'> (default 'leave')

Determines whether a menu opens by hovering or clicking. If set to push menus have to be clicked to open. pull is the same as leave, nolocking has no effect.


  • ?HELPSERVER <comma-separated string-list>

List of apps to display help.


  • VERTICAL_WHEEL_ID

See Mousewheel-Configuration.

  • HORIZONTAL_WHEEL_ID

See Mousewheel-Configuration.

  • VERTICAL_WHEEL_AMOUNT

See Mousewheel-Configuration.

  • HORIZONTAL_WHEEL_AMOUNT

See Mousewheel-Configuration.


  • ICNFY_...

See Iconifying


  • GRADIENTS <number> (default 0)

setting gradients to a nonzero value turns on use of color gradients in the window widget and aes object renderer in hc/tc color modes. This is only a temporary configuration that will be gone later on. Only turn this on if you have a fast machine.

  • SHELL <string>

Names the desktop-program

  • RUN <string>

Runs a program at startup. <string> is full-path\program


Commands for XaAES-clients

These may also affect XaAES itself.

The syntax is:

<app_option>: app_options = <app-name>, <options-list>

<options-list>: <options-list>, <option>

<option>: <option-name> = <value>

For option-name see below. Value may be a number or true/false.


Client-options

  • windowner
  • nohide
  • xa_nohide
  • xa_nomove
  • xa_objced
  • xa_none
  • noleft
  • thinwork
  • nolive
  • wheel_reverse
  • naesff
  • naes12
  • naes
  • winframe_size
  • inhibit_hide
  • spaceXinsert <bool> (default false)

exchanges space/insert-behaviour in dialogs and lists. If false, Insert will select a button in a dialog, space will select a list. This option is casesensitive, so for example SPACEXINSERT will not be recognized.

  • clwtna


  • alt_shortcuts <number> (default 3)


    • 0: no shortcuts
    • 1: shortcuts for alerts
    • 2: shortcuts for dialogs
    • 3: shortcuts for dialogs and alerts

Controls how XaAES handles Alt-shortcuts. Since version 0.999 every standard GEM-application gets Alt-shortcuts for dialogs that use form_do, even when there are no shortcuts defined with WHITEBAK in the resource-file.

The shortcuts that are defined in the clients' resource-file are always there.

Personal tools
Resources