4.2.1 (Apr 2006)
Macros
Macro definitions now support a property that determines whether or not the macro will be sent through a MessageFormat format() upon execution. This property may be set declaratively as an attribute on the macro definition or programmatically on the client side using the Macro interface.
The attribute "useMessageFormat" is a boolean value. If the attribute is not specified, the default (configurable with one of the "ensure-pre-4-dot-2" params) will be used.
When this value is false, parameters are NOT supported for that particular macro.
Declarative Example:
<!-- Single ticks will NOT have to be escaped here because useMessageFormat is false. -->
<macro:macro name="mymacro" useMessageFormat="false" xmlns:macro="http://nexaweb.com/macro" >
<mco:execute ... />
</macro:macro>
Defects Resolved
| Id | Description |
| 5575 | Column headers that are right aligned have cutoff text |
| 5568 | Access key underline on a button is not set correctly |
| 5468 | Button text/image alignment wrong when width or height is specified |
| 5446 | Rich text tag <hr/> not drawing line |
| 5042 | onBeforeActiveLost is not fired when the opposite component is a menu |
| 5347 | Desktop client cannot be maximized on startup |
| 5581 | Tab does not report as an opposite component |
| 5579 | Use of <p/> not working correctly |
| 5530 | Data Binding; space between parameters cause MalformedQueryException |
| 5507 | Copy & paste from <passwordField/> |
| 5604 | Button in table with iterator throws exception |
| 5599 | Mutli-plugins run out client side memory |
| 5657 | ComboBox does not support cursorIndex and endSelectedIndex attributes |
| 5666 | Table does not complete scroll to comboBox field |
| 5662 | Stylesheet class file is missing from nexaweb-client-api.jar |
| 5674 | onMouseOver and disabled (note - only onMouseOver is changing and only for 4.2.x) |
The events like onActiveLost, trying to veto focus movement, etc, might not work well when mixing swing and normal components.