GUI Differences when Running Compact JADE

You can run only a deployed JADE application on Compact JADE. The JADE development environment is not supported.

Compact JADE does not use JADE initialization files. For details about configuring JADE on a Windows Mobile device, see "Configuring Compact JADE", in Chapter 2 of the JADE Installation and Configuration Guide.

When you run Compact JADE:

A hand-held device generates mouseMove events only when the mouse is down.

Printing is not implemented, and is ignored or it raises an exception.

We recommend that the Form class alwaysOnTop method should not be used, as the display of new forms, including the message box, will probably be behind this form.

Windows metafile (.wmf) and enhanced metafile (.emf) image files are not supported and their use generates a not available exception.

The JadeRichText control class is not handled, and it generates an unavailable exception.

The ActiveXControl, JadeEditor, JadeTextEdit, JadeXamlControl, MultiMedia, Ocx, and OleControl control classes and any associated methods on the Application class are not handled, and generate an unavailable exception.

Calls to the CMDFont class generate an unavailable exception, as the dialog does not exist.

Font substitution is not supported and is ignored.

The interrupt icon support is not available.

Accessibility support is not available.

Defined menu accelerator keys are ignored and are not included in the displayed menu item text.

Windows Compact devices do not support images on submenu items. Images can be displayed only on top‑level items that are displayed on the menu bar.

Windows Compact devices do not support JPEG2000 images.

The Multiple Document Interface (MDI) is not supported and is ignored.

Form ::setFormParent is not supported and its use generates a not available exception.

The Window class drawTextCharRotation and drawTextRotation graphics properties are not available and their use generates a not available exception.

The Window class drawFillStyle graphics property is not available; that is, it is ignored.

The Window class drawArc, drawChord, drawFloodFill, and drawPie graphics methods are not available and their use generates a not available exception.

Animated cursors are not available and their use generates a not-available exception.

Cursors other than the standard pointer and the busy (hourglass) cursor have no effect.

Because the size of an image created using the createPicture method has a significant impact when using Compact JADE in thin client mode over a wireless network, the Window class createPictureAsType method enables you to convert the captured image to the specified type before returning it to the calling method.

Minimizing a form is not available and is ignored.

Help requests are ignored.

The Form class minimumHeight and minimumWidth properties are ignored.

Although docking controls can be floated, they can never be docked again because the required mouseMove events are not received.

Use of hatch brushes during drawing is not supported. The fill is therefore always solid.

Setting the TextBox::maxLength property is ignored, as this is not supported.

Table ::partialTextIndication is not available and is ignored.

Because mouseMove events are never received, you cannot resize table rows and columns.

No selected event is generated for a submenu parent menu. The selected event is generated only for a top-level menu.

The Window::hwnd method always returns zero (0).

The Form::scaleForm property is always ignored.

Standard Windows Button images are not available and are ignored.

The hand-held device runs Unicode.

A Unicode hand-held presentation client can connect to an ANSI application server. However, if non‑ANSI characters are transmitted, unexpected failures may occur.

ListBox images are not drawn transparently.

Drawing lines are always solid, as other styles are not supported.

The default font is Tahoma 8.25.

We recommend that your application uses only the Tahoma font, as that is usually the only font available.

Although skins are supported, a form itself is never skinned (that is, there is no ability to draw the form borders). You should limit skin use, however, because they are likely to generate out-of-memory and resource issues.

Maximizing a form adds the ( button to the hand-held top caption if the form has a Close button.

The Compact JADE control panel configuration program (jadeconfig.cpl) adds a permanent soft menu bar. Under Windows Mobile 6.5.3, this bar contains an OK button. For earlier Windows Mobile versions, the OK button is displayed in the caption line of forms. This enables users to commit configuration changes under version Windows Mobile 6.5.3.

The jade.exe program for all Windows Mobile versions creates a standard Windows soft menu bar if there are two or fewer visible top‑level menu items and they do not have images defined. Those top‑level menus are assigned to the soft menu buttons on the menu bar (a maximum of two are available).

Under Windows Mobile 6.5.3, the menu bar also contains the Windows button and an X or OK button, if required, for a maximized form. For earlier Windows versions, the X or OK button continues to be displayed in the caption line of the form. If there are more than two visible top‑level menu items or a top‑level item has a defined image, a standard Windows soft menu bar cannot be created. The menu bar is user‑defined, and under Windows Mobile 6.5.3, there is no X or OK button displayed.

In this situation, your application has to include a user‑defined menu item that performs the close functionality using JADE logic. The alternative solution is to redefine the menu structure so that there are two top‑level menu items only.

With the use of a standard Windows menu bar, a soft menu item button displays only a small amount of text. If the text is too long, the text is truncated with trailing points of ellipsis (…).

Changing the Form::maxButton property value at run time requires the form to be hidden and then redisplayed, which is unattractive when redrawn.

The hand-held device has a tendency to place a form at the top left of the available area. Positioning a non‑maximized form does not always succeed.

Form borders of resizable and fixed (that is, BorderStyle_Sizable, BorderStyle_Double, and BorderStyle_None) are always drawn as single; that is, you cannot resize a form, whose border is always created as BorderStyle_Single.

Folder TabsPosition_Left and TabsPosition_Right values are treated as being at the top (that is, TabsPosition_Top).

A form created under Compact JADE fills the work area of the Windows Mobile device, ignoring the left, top, width, and height property values of the form. This ensures that a form is visible in the device and that the screen work area is fully utilized. Although the Windows Mobile device does this automatically under some conditions if JADE does not do so, JADE always does so for consistency.

In addition, if a form with a caption is dragged, the Windows Mobile device sometimes repositions the form to the top left work area. If required, your logic can reposition and resize a non-maximized form after it has been created.

In addition, the TcpIpConnection class readUntil and readUntilAsynch methods under Compact JADE raise exception 1068 (Feature not available in this release), because certain operating system features are not available on Windows Mobile devices.

See Appendix A of the JADE Thin Client Guide for details about: