Options that relate to a specific view are set via the views menu and are discussed in the relevant chapter of this guide. However, there are a number of options that apply more generally and they are set via the Choices Dialogue.
Select Choices... from the Icon Bar Menu to open the dialogue.
Enabled: discard any changes made to a specific view's settings when the view is closed. You can use the Save Settings option from the view's menu to save settings manually. View settings saved via the menu are permanent. That is, they are remembered even after you exit !EnBank.
Disabled: settings are persistent. That is, they are remembered when a view is closed and re-applied the next time the view is opened. Settings are not permanent, that is they are lost when you exit !EnBank, unless Auto Save is also enabled.
Save window placement, persistent view settings and choices automatically on exit.
Note: To permanently disable Auto Save, you must Save the change.
Enabled: value conversion from one currency to another uses the Matrix Currency Model.
Disabled: value conversion uses the Base Currency Model.
The Matrix Currency Model is better suited for operating accounts in different currencies because it converts directly from one currency to another. However, it requires the maintenance of more exchange rates.
The Base Currency Model requires less maintenance as all exchange rates are stated in terms of Base Currency. Values are converted from Local Currency to Base Currency before been converted from Base Currency to target currency. The Base Currency Model is better suited to installations where all accounts operate in Base Currency.
Refer to the Currency Services documentation for more information on currency models.
Enabled: Transaction Maintenance Dialogue defaults currency for new entries to the current Display Currency for the parent view. That is, the view from which the dialogue was launched.
Disabled: currency default to Base Currency.
The default Exchange Rate Type to be used when currency defaults to Base Currency.
Select which type of Transactions should have their Local Currency values directly converted to Display Currency. The alternative, type not selected, is that the Transactions Converted Account Currency value is converted to Display Currency.
Direct conversion considerations:
Indirect conversion considerations:
Select the Font, Size, Style and Colour to be used for all views from the Font Field Group.
From the Item Colouring Group you can choose specific colours to identify various item states. Colouring for Analysis Views are defined via the Analysis View Menu.
Projections are future dated transactions that enable you to project the future balance of an account based on your standing order schedule.
To include projected values in your Account Balance and to have projected transactions available for inclusion in Statement of Account and Analysis views Enable them here and specify a cut-off date.
The Until Date can be specified as either:
Note: Delta Times are not converted to Absolute Time, they are used to specify a rolling time frame.
Select which types of Standing Order you wish to have projected.
The value projected depends on the Standing Order Type and whether a Projection Value has been specified.
Note: Prompted Orders only project when a Projection Value has been specified.
Enables the JavaScript run-time environment for event driven scripts.
Disable the environment to save resource unless you have any active scripts. The run-time environment for Import Scripts is unaffected by this option.
Click on Edit to the left of the event you wish to provide a script for. This will launch your chosen text editor to create a new, or edit the current, script.
Click on Enable to validate and enable the script for processing. You must resolve any errors in the script before it can be enabled. Validation only ensures the script is syntactically correct. Errors that only occur when the script is run, run-time errors, will not be detected.
Note: if a run-time error occurs in a script then it is disabled and no further attempts to run the script will be made until it has been modified and re-enabled.
Scripts are not re-entrant. That is, the scripts are not invoked for events occurring as a result of a script action.
Invoked after validation of a new transaction but before the transaction is actually added to file.
Script can modify Current Transaction.
Script return status: True, add Transaction. False, don't add Transaction.
If the script returns a status of 'false' then the Transaction is not added and the Transaction Maintenance Dialogue is left open. Any modifications to the Transaction will be reflected in the dialogue.
Invoked after a new transaction is added to file.
Script can read, but not modify, Current Transaction.
Script return status is ignored.
Internally, dates are converted to, and used in, UTC format. The options in this part of the Choices dialogue control the representation of date fields when converted to local time for input and display purposes.
Specifies the date, and optionally time, format you wish to use for Input Fields and Display Fields.
Input Format specifies the desired date format for date fields within dialogues. The format affects only the display of existing or default dates. Any valid date format can be used to enter new dates.
The Display Format is used when displaying dates in list views. The format string uses the standard RISC OS date & time variables and may contain text.
For example: %24 %m3 &ce%yr, %24:%mi (%tz)
produces: 02 Jan 2004, 14:00 (GMT)
Date & Time Format Variables | |
%se | seconds |
%mi | minutes |
%12, | hours in 12 hour format |
%24, | hours in 24 hour format |
%am | 'AM' or 'PM' |
%we | weekday (full) |
%w3 | weekday (3 characters) |
%wn | weekday as a number |
%dy | day of the month |
%st | 'st' 'nd' 'rd' or 'th' |
%mo | month name, in full |
%m3 | month name (3 characters) |
%mn | month as a number |
%ce | century |
%yr | year within century |
%wk | week of the year |
%dn | day of the year |
%tz | Time-zone |
To avoid leading zeros on number fields you can use %z. On the second day of the month %dy would return '02' while %zdy would return '2'.
With this option enabled the software compensates for changes in 'Daylight Saving Time'. In other words, a time entered while DST was in force will display the same time after the switch back to normal time, that is DST is no longer in force. With the option disabled the time displayed would reflect the 'shift' in local time.
For example, if you were in the UK and entered '1 Nov 2003, 00:00' while BST, British Summer Time, was in effect. Then following the switch back to GMT the time would show as '31 Oct 2003, 23:00'. This is technically correct, if a little confusing, as '1 Nov 2003, 00:00 (BST)' is equal to '31 Oct 2003, 23:00 (GMT)'. By electing to compensate for the change the date would continue to show as '1 Nov 2003, 00:00'.
Why? Well, as already mentioned, date-times are stored in UTC format. When you enter a date in local time it is converted to, and stored in, UTC (effectively GMT). This means that date comparisons are not effected by current locale and work correctly across different time-zones. When a date is redisplayed it is converted back from UTC to current local time, which will vary depending on whether DST is, or is not, currently in force.
Note that the time variable %tz always returns the current time-zone, not the time-zone appropriate to the compensated time being displayed. If you do not require the time component of a date field then it is recommended that you have the 'Compensate for DST Changes' enabled (default).
More information on UTC can be found at the National Maritime Museum or the U.S. Naval Observatory web sites.
Specifies the formatting options for both Numbers and Monetary Values.
Most of the values used in !EnBank are monetary values. However, when a transaction value is exported to file it is the number format that is used and the negative and separator settings are ignored.
Negative values can be displayed:
Use the separator character to split up large numbers.
By default values are formatted using the characters specified by the current RISC OS territory. To use an alternative character, enable the desired field and specify the character to use.
Care must be taken to ensure that the specified characters are meaningful. You can not use the same character for two purposes. If, for example, you override the UK territory module and specify a comma ',' as the decimal point you must also override the separator, which by default is a comma, to some other character.
Specifies the size of each group of digits before a separator is inserted. This list is a comma separated list of group sizes starting with the least significant group. If the last group size in the list is specified as 0 (zero) then the previous group size is repeated for the rest of the number.
Examples: