| Previous Next | Contents |
Class.YN left-aligned caption implemented. Strange that this was never noticed!
Class.LBJ now links on mouse-up (right-mouse menu is still on mousedown) as Dyalog can lose the mouseup otherwise by starting the browser. The effect is that clicking pretty well anywhere on the form will re-run the weblink which can be very annoying for the user!
Class.DC,Class.CB both of these were selecting the text whenever it was refreshed. Not sure why, but better done with the same focus handler as TX has. Future option is to add a no select on focus style if it would be useful.
Class.NM if format was not set, this defaulted to rounding to integer. Now just uses bare thorn in this case so is more flexible.
Class.RTF updated to be a useful text editor, with integral toolbar. The individual tool buttons may be selectively enabled (all are available by default) and the images for the buttons and also the tooltips may be set by the application designer. This allows for customisation into languages other than English.
Class.LV,Class.TR new internal event EDIT added to wrap Dyalogs 301 event. this allows the application to trap and optionally reject editing of labels in the ListView and TreeView. Samples QA.tr and QA.lv updated to reject changes which lead to duplicate labels. Currently only works correctly in the ListView as the TreeView does not handle rejection. Reported to Dyadic support as a bug.
Class.IsPocket marks classes considered suitable for the PocketPC. Basically the Win31 set (simple dialogs rule) with a few things like trackbars. The Designer now has an extra flag to cut down the choice to these.
Class.TB adds the standard style property to permit choices like no 3D in the Designer.
Designer checks for Size= in appropriate form class when creating new objects. This allows the standard designer to make reasonable new forms for the PocketPC screen size.
CPro.ActionLines removes DR check which was looking for multi-line actions in object definitions. This crashed PocketPC APL and was never used, as the Designer was never updated to generate actions of this type.
CPro.Do groups are now more pervasive. This allows a button on a toolbar to disable a bunch of controls on a child form as this now searches back to the base form and then looks for the groups in any children of this. Independently rooted forms are still hidden from each other, but there may be an issue with MDI where a button on one MDI child could disable a bunch of controls on an MDI sibling. This seems reasonable, as a much more likely requirement is for a button on a shared toolbar to disable controls on ALL current MDI children.
Check out cm mdip and cm ¨3½gtptest in QA for examples.
CPro.Substitute works OK with nested DFNS in form actions now.
Designer was handling all Ctrl+... keystrokes in fields which could accept APL chars. Now it allows Ctrl+Insert to get through.
Class.TKB, Class.SB survive a non-integer setting of the data variable. An integer value is always returned if the tracker is used to modify the data.