4.5.43 (Feb 2011)

New features

• Official support for <gridTable/> with its documentation
• Add antiAlias support to <content> child of <chart> (See 10863)
• Resource usage is limited when using PerformanceMeter (See 10871)
• Support MS Windows style behavior of the restore button in window component (See 10872)
• Add method isVisible() to DisplayService which allows developer to determine if an element is visible (See 10888)
• Add method transferFocus(), transferFocusNext() and transferFocusPrevious() to FocusManager API (See 10904)

Defects Resolved (Java)

10668 Scrollbar in disabled widgets can still be scrolled by mouse wheel

Now by default, a scrollbar can only be scrolled by a mouse wheel when it is enabled. Backward compatibility can be allowed by setting "<ignore-scrollWheelEvent-on-disabled>false<ignore-scrollWheelEvent-on-disabled/>" under <client-app> in nexaweb.client.xml.

10863 Add antiAlias support to the <content> child of <chart>

To enable Anti-aliasing on <chart>, set its child element <content antiAlias="true" .../>.

10871 The resources used by PerformanceMeter is unlimited

PerformanceMeter stores information in WeakHashMap. When <performance-meters-enabled> is set to false, none of the performance meters is added to WeakHashMap. When it is set to true, it is fixed such that IntervalStatistics are no longer added to WeakHashMap and there can be only limited number of LifeTimeStatistics.

10872 Added the option to make restore button in window component behaves in standard MS Windows style, instead of the Unix style by default
 

To use the MS Windows style behavior, please add "<windows-style-restore>true</windows-style-restore>" under <client-app> in nexaweb.client.xml.

10888 When a widget's visible attribute is set to false, it can still receive a focus

A method isVisible() is added to DisplayService which allows developer to determine if an element is visible. An element is invisible if it is not shown on the screen. Besides the basic case where the element's visible attribute is set to false, some other cases include: the element is inside a collapse row, or inside a unselected tab/card pane, etc.

10904 When input on a field reaches its max-length, 'Tab key' events should be fired automatically on that field

The following methods are added to the FocusManager API, and should transfer the focus where indicated, if the currently focused component allows it, and the specified location is focusable.

/**
* Transfer the focus to the specified element. This method is unlike the focusNext() and
* focusPrevious() methods, in that it can fail if the currently focused component is a Nexaweb
* component and it denies the focus change using the onBeforeActiveLost method.
*
* @param e The element in the UI document to transfer the focus to.
*
* @since 4.5.43
*/
public void transferFocus(Element e);


/**
* Transfer the focus to the next focusable component. This method is unlike the focusNext()
* method, in that it can fail if the currently focused component is a Nexaweb
* component and it denies the focus change using the onBeforeActiveLost method.
*
* @since 4.5.43
*/
public void transferFocusNext();


/**
* Transfer the focus to the previous focusable component. This method is unlike the focusPrevious()
* method, in that it can fail if the currently focused component is a Nexaweb
* component and it denies the focus change using the onBeforeActiveLost method.
*
* @since 4.5.43
*/
public void transferFocusPrevious();

10912 Restore/minimize/maximize button of a window receives focus when its minimizable/maximizable attribute is set to false

When minimizable/maximizable/closable is set to false and focus is set on these buttons, the focus will be transfered to its parent window.

10916 Security flag for cookie is not set when HTTPS is used

Secure flag for cookie can be set by adding "<secure-session-cookie>true<secure-session-cookie/>" under<server> in nexaweb-server.xml.