1704.4 |
Fix |
XTREE export to spreadsheet: TreeID strings containing special characters like colon or slash where interfering with the creation of the spreadsheet export files. |
||||
1704.3.1 |
Error message refinement: when location counter are displayed in screen error messages, they are now preceded by &h to make clear that they are hex. |
|||||
1704.3.2 |
Fix |
Ashlog: the location counters appearing in the prefix section of each ashlog message are now back to hex. They were inadvertently switched to decimal in 6.5.1702.0 while upgrading some format specifiers for compatibility with newer standard library conventions. |
||||
1704.3.3 |
Fix |
SCALE: .VALX(a$) wasn't applying the SCALE factor properly, resulting in values one or more powers of 10 larger than they should have been. |
||||
1704.2.1 |
Mouse cursor reporting sequence enhancement: The TAB(-1,158) scheme for converting mouse clicks into byte sequences now works with controls that are nested within parent controls (such as a TABX or dialog) rather than being directly part of the main window. Previous enhancement (see 6.5.1702.0 below) only worked for controls that were direct children of the main window. |
|||||
1704.1.1 |
Language refinement, compiler edit 947: all standard string functions now support the optional $ suffix on the name (e.g. STR(x) or STR$(x).) The following functions did not previously support the optional $ suffix: AUTOCAP$(a$), LCS$(a$), ODTIM$(date,time,flags), RTRIM$(a$), UCS$(a$). |
|||||
1704.1.2 |
IMGDSX.LIT 1.0(115) refinements:
|
|||||
1704.1.3 |
Fix |
WEBCACHE refinement: web repository URLs using https:// or an explicit :port were failing to work properly. Note that IMGDSX provides a convenient way to test the WEBCACHE feature:
You should then be able to display them using IMGDSX fspec. Also note that in the case of ATE, you have to enabled WEBCACHE on the ATE client using AG_WEBCACHE. |
||||
1704.0 |
Language enhancement, compiler edit 946, auto-mapped for/next loop variables: You may now create a new variable on the fly to act as the loop counter in a for/next loop by preceding the variable name with a % as in this example: for %i = 1 to 10 print %i next %i xx
The variable %i will be automatically mapped (as an F,6), with its scope limited to the boundaries of the for/next loop. Besides acting as "syntactic sugar" to save typing (i.e. by eliminating the need to separately map the loop counter variable), the feature also has the benefit of reducing the chance of an accidental conflict between the loop counter and an existing concurrent use of the same variable. The concept is similar to the $$i iterators. |