latex/wx/wxmsw.tex

3 %% Purpose:     wxMSW and wxWinCE platform specific informations
15 including Windows 95, 98, ME, 2000, NT, XP in ANSI and
17 library). wxMSW ensures native look and feel for XP
20 including MS VC++, Borland 5.5, MinGW32, Cygwin and
36 sunken border. Other native controls such as wxTextCtrl in non-rich edit mode, and wxComboBox,
40 Note that in wxWidgets 2.9 and above, wxBORDER\_THEME will be used on all platforms to
42 wxWidgets 2.9 and above will also be better at determining whether there should be a themed 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,
49 returned, and on XP and above where theming is turned on, wxBORDER\_THEME will be returned.
50 This function does not exist in wxWidgets 2.9 and is not part of the official API.
57 most of wxMSW is common to Win32 and Windows CE but there are
58 some simplifications, enhancements, and differences in
68 Mobile applications generally have fewer features and
70 lines and controls in your dialogs, and use comboboxes instead
87 and wxWidgets will take care of showing the current instance and
97 values are hard-wired according to the build, and you cannot
104 an application that has been tailored for PocketPC and Smartphone use.
118 \twocolitem{\_\_SMARTPHONE\_\_}{Generic mobile devices with phone buttons and a small display}
144 When input panel (SIP) is shown, top level windows (frames and dialogs) resize
150 on Smartphone and PocketPC; the window is simply hidden instead. However the system may send the
155 Smartphone and PocketPC will send a wxEVT\_HIBERNATE to the application object in low
156 memory conditions. Your application should release memory and close dialogs,
157 and wake up again when the next wxEVT\_ACTIVATE or wxEVT\_ACTIVATE\_APP message is received.
159 in Smartphone and PocketPC, since these platforms do not support WM\_ACTIVATEAPP.)
164 under Smartphone and PocketPC. You should first register each required button with \helpref{wxWindow::RegisterHotKey}{wxwindowregisterhotkey},
165 and unregister the button when you're done with it. For example:
180 PocketPC dialogs have an OK button on the caption, and so you should generally
188 Smartphone dialogs do {\it not} have an OK button on the caption, and are closed
190 and \helpref{wxTopLevelWindow::SetRightMenu}{wxtoplevelwindowsetrightmenu}, for example:
204 and have the notebook left, top and right sides overlap the dialog by about 3 pixels
207 provided, to show settings in the correct style on PocketPC and on other platforms.
209 Notifications (bubble HTML text with optional buttons and links) will also be
212 Modeless dialogs probably don't make sense for PocketPC and Smartphone, since
213 frames and dialogs are normally full-screen, and a modeless dialog is normally
216 \subsubsection{Menubars and toolbars in wxWinCE}
218 \wxheading{Menubars and toolbars in PocketPC}
224 Menubars and toolbars are implemented using a combined control,
226 and toolbar. However, there are some restrictions:
232 to implement the combined toolbar and menubar. Otherwise, you can create and manage toolbars
237 \item Deleting and adding tools to wxToolMenuBar after Realize is called is not supported.
247 and add buttons, then calling wxToolBar::Realize. You cannot set or recreate
250 \wxheading{Menubars and toolbars in Smartphone}
263 defines this accelerator by default and if your application handles
276 These controls and styles are specific to wxWinCE:
293 tooltips are distinct controls, and it will be hard to add dynamic
296 Control borders on PocketPC and Smartphone should normally be specified with
300 which will give a simple border on PocketPC and Smartphone, and the sunken border on
309 \subsubsection{Installing your PocketPC and Smartphone applications}
313 in your SDK will compile the CAB file from the .inf file and
317 device and execute the CAB file using File Explorer. Or, you can
319 Application Manager and install the CAB file on the device,
326 \item A setup builder that takes CABs and builds a setup program is at \urlref{http://www.eskimo.com/~scottlu/win/index.html}{http://www.eskimo.com/~scottlu/win/index.html}.
337 devices. In particular, {\tt build.bat} builds the distribution and
357 an extra library, {\tt ccrtrtti.lib}, and link with it. At the time of
381 for each configuration and in the Librarian, add a relative path ..$\backslash$..$\backslash$lib to
385 and make sure {\tt ..$\backslash$..$\backslash$lib$\backslash$\$(PlatformName)$\backslash$\$(ConfigurationName)} is in the Linker/General/Additional
395 These are some of the remaining problems to be sorted out, and features
403 new Mobile 5 convention of using only two menus (and no bitmap buttons) needs to be
407 \item {\bf Notification boxes.} The balloon-like notification messages, and their
410 and the remaining area, by calling SHSipInfo. We also may need to be able to show and hide
412 the {\it Programming Windows CE} guide for more on this, and how to have dialogs
416 \item {\bf wxStaticLine.} Lines don't show up, and the documentation suggests that
421 \item {\bf Tooltip control.} PocketPC uses special TTBUTTON and TTSTATIC controls for adding
427 and note that the default OnActivate handler in src/msw/toplevel.cpp sets the focus to the first child of the dialog.
437 on deactivation and activation.
442 options to display information in a particular way using icons and text from
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,
448 or by providing a standard component and sizer.