4.72. openmotif

Bug Fixes

BZ#492529

Attempting to use a keyboard accelerator such as Ctrl+S, failed to achieve the intended effect when the Caps Lock, Scroll Lock or NumLock keys were activated. This was caused by missing support for the X11R6 modifiers scheme. Support for the modifiers scheme has been implemented in this update so that keyboard accelerators can be used as expected even when modifiers, such as Caps Lock, Scroll Lock or NumLock, have been activated.

BZ#557453

Redisplaying a Label or the LabelGadget widget could have caused a BadDrawable X error and resulted in an invisible label. This update resolves the problem with unspecified pixmaps so that labels do not become invisible and BadDrawable errors are not incurred.

BZ#568730

Selecting an item in the MultiList widget resulted in that item becoming invisible due to the same color being used for both foreground and background colors. The same problem occurred with "insensitive" labels, buttons, icons and list entries. With this update, foreground and background colors in widgets have been differentiated so that the items do not become invisible during operation.

BZ#634094

Due to 32-bit time stamp problems, attempting to copy and paste on 64-bit architecture using the clipboard may have failed occasionally. With this update, the underlying source code has been modified to ensure the time stamp always contains a "CARD32" value, so that copy and paste on 64-bit architectures works as expected.

BZ#638553

Previously, a check that would limit removing a callback to valid windows while the focus is reset was missing in the code. Consequently, destroying a torn-off menu with a submenu mapped caused the application to terminate unexpectedly. With this update, the underlying source code has been modified to ensure that the focus is reset for valid windows only and destroying a torn-off menu with a submenu mapped now works as expected.

BZ#772937

The RHBA:2011-1451 advisory introduced a regression by specifying the XmI.h header file in the include directive of multiple files. However, if the file was not installed, compiling applications that used the Label and LabelGadget widgets failed with the following message:

/usr/include/Xm/LabelGP.h:48:17: error: XmI.h: No such file or directory

With this update, the include directive containing "XmI.h" has been removed. Applications using the Label and LabelGadget widgets can now be compiled as expected.

BZ#818655

Previously, OpenMotif did not detect certain keystrokes, such as Home, Insert, Del, PgUp, PgDn on the keypad if the NumLock key was not engaged. This was caused by Motif overriding the existing keycode-to-keysym routine for its own virtual keysyms. As a result, the XmTranslateKey() function substituted the shifted keysym when it should not have. After this update, disengaging the NumLock key does not affect the detection of the aforementioned keystrokes.

BZ#864409

Previously, using the XmList widget in Openmotif to view log output from an application was obstructed by a very slow performance. This was due to the XmListSetPos() function, which is used to scroll to the end of the list, being too slow. With this update, a patch has been provided to fix the code and the performance problem has been resolved.

BZ#867792

Before this update, OpenMotif was missing certain strings on the Label Widget. This update adds the missing strings which are now displayed on the Label Widget.

BZ#880914

Previously, OpenMotif displayed its frame too large in size. After updating and counting children on the form, OpenMotif updated and repainted the form but it took extra space after replacing the children. With this update, the frame takes up only the required space.

BZ#980577

Previously, the size set in the GeometryManager() function based on the XmFormConstraint "preferred_width" field was not updated when the label was changed and still contained the previous label length. Consequently, if the label text was modified while the window was smaller than the actual label width, the resulting size was incorrectly computed and the label text truncated. With this update the values are updated and the fault no longer occurs in the scenario described.