1193.4 |
XTREE bug fix / refinement: Reorganize the code that determines the exitcode when there are multiple possibilities, to avoid conflicts caused by interaction between multiple XTREE controls. This was leading to unexpected exitcodes (like -48) when clicking on one tree while another one was active. |
||||||
1193.3 |
XTREE enhancement: when a call using XTF_NOSEL follows a click on the inactive tree, it now returns the location of the click in the XTR'TARGETROW and XTR'TARGETCOL fields. This is useful in the following scenario: Your program is waiting in some state other than XTREE (perhaps INFLD), but there is a visible (inactive) XTREE control on the screen. The user clicks on a cell in the XTREE. This returns the exitcode defined by XTR'KBDSTR to whatever routine is waiting on input. Your program sees that the exitcode is from clicking on the inactive XTREE, but you want to know what cell was clicked. So you call the XTREE, with opcode XTROP_RESELECT and with the XTF_NOSEL flag set (for an immediate exit). On exit, your program can get the location of the click from XTR'TARGETROW/XTR'TARGETCOL. |
||||||
1193.2 |
XTREE bug fix: Using XTROP_DELSEL with a tree containing editable cells was often scrambling the editable cell data in rows following the last row marked as deleted. |
||||||
1193.1 |
MAXLOCKS bug fix: The MIAME.INI statement MAXLOCKS=### was effectively being ignored, making it impossible to increase the default number of simultaneous locks (100). |
||||||
1193.0.1 |
Compiler (edit 467) / Runtime refinement: STATIC DIMX statements were not acting like other STATIC MAP statements in only executing once. Instead you had to use another static variable to maintain a flag, or some other mechanism, to avoid trying to execute the statement a second time (which would have caused a Basic error). |
||||||
1193.0.2 |
Compiler enhancement (edit 468): It is now possible to use the sizeof(var) compiler function to reference the size of the immediately preceding variable even when it is a structure. Previously, this generated a "variable size not yet finalized" compile error, requiring the insertion of a variable in between the preceding var and the one using the sizeof(var) expression. |
||||||
1193.0.3 |
Compiler enhancement (edit 469): Local non-static DIMX statements are now fully cleaned up on exit from the function or procedure. Previously, the variable descriptor was removed (along with all of the other local stack variables), but the memory handle and allocation remained in effect. With this enhancement, it is no longer necessary to use REDIMX(0...) to "undimx" any DIMX'd arrays at the end of the function. (But it doesn't hurt to perform that step redundantly.) Note that this is purely a compiler adjustment not a runtime fix. |
||||||
1193.0.4 |
W2000 compatibility has been restored. (It was lost when we switched to the VS2010 compiler, a few versions back.) |
||||||
1193.0.5 |
(Windows/ATE) TAB(-1,49) (solid block), TAB(-1,50) (slant-hashed block), and TAB(-1,51) (crosshatch block) were not displaying properly except with the MIAME Terminal font. |
||||||
1193.0.6 |
COMIO.SBR fixes/refinements:
|
