These are some of the remaining problems to be sorted out, and features
to be supported.
- Font dialog. The generic font dialog is currently used, which
needs to be simplified (and speeded up).
- Sizer speed. Particularly for dialogs containing notebooks,
layout seems slow. Some analysis is required.
- Notification boxes. The balloon-like notification messages, and their
icons, should be implemented. This will be quite straightforward.
- SIP size. We need to be able to get the area taken up by the SIP (input panel),
and the remaining area, by calling SHSipInfo. We also may need to be able to show and hide
the SIP programmatically, with SHSipPreference. See also the Input Dialogs topic in
the Programming Windows CE guide for more on this, and how to have dialogs
show the SIP automatically using the WC_SIPREF control.
- wxStaticBitmap. The About box in the "Life!" demo shows a bitmap that is
the correct size on the emulator, but too small on a VGA Pocket Loox device.
- wxStaticLine. Lines don't show up, and the documentation suggests that
missing styles are implemented with WM_PAINT.
- wxCheckListBox. This class needs to be implemented in terms of a wxListCtrl
in report mode, using icons for checkbox states. This is necessary because owner-draw listboxes
are not supported on Windows CE.
- wxFileDialog. A more flexible dialog needs to be written (probably using wxGenericFileDialog)
that can access arbitrary locations.
- HTML control. PocketPC has its own HTML control which can be used for showing
local pages or navigating the web. We should create a version of wxHtmlWindow that uses this
control, or have a separately-named control (wxHtmlCtrl), with a syntax as close as possible to wxHtmlWindow.
- Tooltip control. PocketPC uses special TTBUTTON and TTSTATIC controls for adding
tooltips, with the tooltip separated from the label with a double tilde. We need to support this using SetToolTip.
(Unfortunately it does not seem possible to dynamically remove the tooltip, so an extra style may
- Focus. In the wxPropertySheetDialog demo on Smartphone, it's not possible to navigate
between controls. The focus handling in wxWidgets needs investigation. See in particular src/common/containr.cpp,
and note that the default OnActivate handler in src/msw/toplevel.cpp sets the focus to the first child of the dialog.
- OK button. We should allow the OK button on a dialog to be optional, perhaps
by using wxCLOSE_BOX to indicate when the OK button should be displayed.
- Dynamic adaptation. We should probably be using run-time tests more
than preprocessor tests, so that the same WinCE application can run on different
versions of the operating system.
- Modeless dialogs. When a modeless dialog is hidden with the OK button, it doesn't restore the
frame's menubar. See for example the find dialog in the dialogs sample. However, the menubar is restored
if pressing Cancel (the window is closed). This reflects the fact that modeless dialogs are
not very useful on Windows CE; however, we could perhaps destroy/restore a modeless dialog's menubar
on deactivation and activation.
- Home screen plugins. Figure out how to make home screen plugins for use with wxWidgets
applications (see http://www.codeproject.com/ce/CTodayWindow.asp for inspiration).
Although we can't use wxWidgets to create the plugin (too large), we could perhaps write
a generic plugin that takes registry information from a given application, with
options to display information in a particular way using icons and text from
a specified location.
- Further abstraction. We should be able to abstract away more of the differences
between desktop and mobile applications, in particular for sizer layout.