high-ascii input problems and some internal experimentation.
John Bridges
http://www.aftergrasp.com/download/agsetup_20080320.exe
----------------------------------------------------------------------------
Thu, 20 March 2008
INPUT commands were not handling high-ascii characters like £, fixed.
Keyboard input was not allowing high-ascii characters to be entered
via the numeric keypad and alt key. Fixed. This means alt-end,
alt-home, alt-pgup, alt-pgdn, alt-up, alt-down, alt-right, alt-left
are no longer allowed.
Direct keyboard input on non-USA keyboards of high-ascii characters
was sometimes wrong, fixed.
Command name change, text commands previously listed as XY are now RECTS,
they return an array of boxes with LEFT, TOP, RIGHT, BOTTOM. All the
DRAWLIST commands now expect an array of RECTs, not an XY array.
Why do the TEXT RECTS commands return a flat array, and DRAWLIST commands
expect a flat array? Design limits of AfterGRASP make is a poor idea to
create large numbers of 2 dimensional arrays, or arrays of thousands
of separate objects (I looked into using a built in type, RECT).
So I've abandoned all the code I was researching, and I'm sticking with
a simple single dimensional array of integers. Four elements per
character position. I realize this makes for ugly direct access to
individual coordinates (having to multiply the string position by 4).
The next update may switch this to using a memory buffer (like that
created with MEMNEW) since it will be smaller, faster and slightly
easier to use.
Over time I expect all this to grow into some new functions for
rich text editing that will be painless to use.
Some assorted new functions used for internal testing only:
AREAITEM = TOAREA(X1, Y1, X2, Y2)
RECTITEM = TORECT(LEFT, TOP, RIGHT, BOTTOM)
->BOTTOM
->LEFT
->RIGHT
->TOP
->XPOS
->YPOS
----------------------------------------------------------------------------