4.5.9 (Dec 2007)

Java Improvement

Overview

One of the goals of this MR is to bring consistency to the use of popups. This section outlines the order of events that occur after a particular action. The following bugs identify several areas of inconsistencies with the use of the popups and popupMenus as context popups that were addressed in this maintenance release. (See the end of this 4.5.9 MR note for a full list of fixed defects.)

1. onBeforeActiveLost on invoker ( the component on which right mouse button was clicked)
2. onActiveLost on Invoker
3. onActiveGained on context popup (either popup or popupMenu)

Notes:

• The onBeforeActiveLost() allows for potential validation on the invoking component before bringing up the popup or popupMenu.
• The activeGained on the context popup, allows focus to be sent to any component when using a popup.
• Since focus is being taken away from the invoker, this means that the selection in a textField will also be taken away. Bug 8794, states that they wanted selection to stay. This can be done by setting the attribute of the textField to "always".

Proposed new order of events

This means that if you click into a textField while a context popup is visible, the popup will go away and the textField will gain focus and be selected. This is a change from how it worked before Platform 4.5.9. Previously, in order to select the textField, you had to click twice. Once to dismiss the context popup, and a second time to select the textField.

Popup
Previously, nothing happened when pressing escape when the context popup is defined as popup. Version 4.5.9 has the following behavior.

• onBeforeActiveLost on popup
• onActiveLost on popup
• onActiveGained on invoker

More Java Improvements

Selection behavior using right click of mouse

The following outlines the improved right-click selection behavior. 

• Any right mouse click within a selection of cells, rows, or columns, should not result in the selection being changed, but should show the context menu. This is regarless of whether the control or shift keys are down.
• A right mouse click outside the current selections should select the single cell, row or column and bring up the context menu.
• Ctrl-Right mouse Click or Shift-Right mouse click, should add rows, columns, or cells, to the selection if the occurs outside the current selections.

Combo box's width respects explicit setting
If a developer explicitly defines the combo box width, then the combo box width will render with that width regardless of the length of the contents of the largest list item.
 

Window improvement when using attribute centered="true"
When using centered="true", now, window will not re-center itself everytime window is redrawn.
 

Styling of heavy weight components in table (XAL) have been improved
Styling such as font and background color inside heavy-weight components now render correctly. This issue was present in XAL only.
 

onMouseDrag is now fully supported
onMouseDrag has been added to the documentation for components such as panels, widgets and cell, listItem.

listItem and row height now support "px" in XAL
It is now possible to specify row and listItem height using "px" when using the XAL syntax.

Ctrl-X now generates an onTextChange event
The onTextChange event will now fire when Ctrl-X (cutting of text) is used.

Events can now be stored in Style Sheets
It is now possible to add events to elements in style sheets.

For example,

stylesheet.xss:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  <styleSheet>
    <style applyTo="cell">
      <normal fontItalic="true" 
       onCreate="macro://addRow.execute('Create')" 
       onDoubleClick="macro://addRow.execute('DoubleClick')" 
       onMouseDown="macro://addRow.execute('MouseDown')" 
       onMouseUp="macro://addRow.execute('MouseUp')"/>
    </style>
</styleSheet>

Contents of cells inside table can now be aligned vertically
Support has been added to allow table cell contents to be aligned vertically. The name of this attribute for each syntax is, "alignVertical" (NXML), and "verticalAlignment" (XAL). This attribute has the following three values: "top|bottom|center". Details of this attribute have been added to the schema documentation.

To allow a workaround, we have exposed (undocumented class) com.nexaweb.client.xml.ThreadBasedSynchronizer. Where a change or changes to the UI DOM are needed, surround them with a call to push synchronization state and pop synchronizations state. Pop MUST be called when push is called - example:

public void onAttributeSet(AttributeChangeEvent arg0) {
  try {
  ThreadBasedSynchronizer.pushSynchronizationState(true);
  // change some attributes... }
  finally {
    ThreadBasedSynchronizer.popSynchronizationState(true);
  }
}

Defects Resolved (Java)