latex/wx/wxmsw.tex

14 wxMSW is a port of wxWidgets for the Windows platforms
16 Unicode mode (for Windows 95 through the MSLU extension
17 library). wxMSW ensures native look and feel for XP
34 If you don't specify a border style for a wxTextCtrl in rich edit mode, wxWidgets now gives
41 indicate that there should definitely be a border, whose style is determined by wxWidgets for the current platform.
44 capability could not be put into wxWidgets 2.8 except for built-in, native controls. In 2.8, the border
45 must be specified for custom controls and windows. However, to make it easier to decide
47 and it will return a suitable style for the current version of Windows. On Windows CE,
64 need to be aware of when programming for Windows CE devices.
66 \subsubsection{General issues for wxWinCE programming}
72 the amount of spacing used by sizers, for which you can
91 for a qualitative assessment of what kind of display is available,
94 You can also use wxGetOsVersion to test for a version of Windows CE at
98 dynamically adapt the same executable for different major Windows CE
100 wxWidgets adapts its behaviour (such as for menubars) to suit the
103 See the "Life!" example (demos/life) for an example of
104 an application that has been tailored for PocketPC and Smartphone use.
106 {\bf Note:} don't forget to have this line in your .rc file, as for
113 \subsubsection{Testing for WinCE SDKs}
115 Use these preprocessor symbols to test for the different types of device or SDK:
124 \twocolitem{\_\_WINCE\_STANDARDSDK\_\_}{Microsoft-powered Windows CE devices, for generic Windows CE applications}
143 according to the orientation, which you could detect in idle time, for example).
183 to make up for it). When the user clicks on the OK button, your dialog will receive
190 and \helpref{wxTopLevelWindow::SetRightMenu}{wxtoplevelwindowsetrightmenu}, for example:
210 implemented in the future for PocketPC.
212 Modeless dialogs probably don't make sense for PocketPC and Smartphone, since
221 An empty menubar/toolbar is automatically provided for dialogs, to hide
222 any existing menubar for the duration of the dialog.
233 using the wxToolBar class as usual, for example to implement an optional
236 for the main frame toolbar.
240 or with transparency (for example, using XPMs).
246 for you. You may either leave it blank, or access it with wxDialog::GetToolBar
292 Tooltips are not currently supported for controls, since on PocketPC controls with
307 See the Windows CE reference for how to format the HTML files.
318 write a program for the desktop PC that will find the ActiveSync
320 which is obviously much easier for the user.
330 \item Installer creation instructions with a setup.exe for installing to PPC can be found at \urlref{http://www.pocketpcdn.com/articles/creatingsetup.html}{http://www.pocketpcdn.com/articles/creatingsetup.html}.
336 scripts to create a PocketPC installation for ARM-based
345 (not the system or card root directory, for example). This is
346 a known problem for PocketPC developers.
372 Note that there is no separate emulator configuration for Windows Mobile 5.0: the
381 for each configuration and in the Librarian, add a relative path ..$\backslash$..$\backslash$lib to
384 Then, for a sample you want to compile, edit the configuration properties
400 \item {\bf Windows Mobile 5 issues.} It is not possible to get the HMENU for
405 \item {\bf Sizer speed.} Particularly for dialogs containing notebooks,
412 the {\it Programming Windows CE} guide for more on this, and how to have dialogs
418 \item {\bf HTML control.} PocketPC has its own HTML control which can be used for showing
421 \item {\bf Tooltip control.} PocketPC uses special TTBUTTON and TTSTATIC controls for adding
434 frame's menubar. See for example the find dialog in the dialogs sample. However, the menubar is restored
438 \item {\bf Home screen plugins.} Figure out how to make home screen plugins for use with wxWidgets
439 applications (see {\tt http://www.codeproject.com/ce/CTodayWindow.asp} for inspiration).
445 between desktop and mobile applications, in particular for sizer layout.
447 should be catered for, either by hard-wiring the capability into all dialogs and panels,