X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/ea9aa80e7c667e2951ac0967da903d2b9ec5e2b6..65baafba0e8cd74f2264b7e2f7625ff5bea84864:/docs/latex/wx/wxmsw.tex diff --git a/docs/latex/wx/wxmsw.tex b/docs/latex/wx/wxmsw.tex index ee801cd08c..d73426584c 100644 --- a/docs/latex/wx/wxmsw.tex +++ b/docs/latex/wx/wxmsw.tex @@ -20,7 +20,7 @@ most of wxMSW is common to Win32 and Windows CE but there are some simplifications, enhancements, and differences in behaviour. -For installation instructions, see docs/msw/wince in the +For building instructions, see docs/msw/wince in the distribution. The rest of this section documents issues you need to be aware of when programming for Windows CE devices. @@ -64,6 +64,13 @@ style of device. See the "Life!" example (demos/life) for an example of an application that has been tailored for PocketPC and Smartphone use. +{\bf Note:} don't forget to have this line in your .rc file, as for +desktop Windows applications: + +\begin{verbatim} +#include "wx/msw/wx.rc" +\end{verbatim} + \subsubsection{Testing for WinCE SDKs} Use these preprocessor symbols to test for the different types of device or SDK: @@ -127,7 +134,7 @@ and unregister the button when you're done with it. For example: win->UnregisterHotKey(0); \end{verbatim} -You may have to register the buttons in a wxEVT_ACTIVATE event handler +You may have to register the buttons in a wxEVT\_ACTIVATE event handler since other applications will grab the buttons. There is currently no method of finding out the names of the special @@ -158,7 +165,7 @@ and wxTopLevelWindow::SetRightMenu, for example: #endif \end{verbatim} -For implementing property sheets (flat tabs), use a wxNotebook with wxNB_FLAT|wxNB_BOTTOM +For implementing property sheets (flat tabs), use a wxNotebook with wxNB\_FLAT|wxNB\_BOTTOM and have the notebook left, top and right sides overlap the dialog by about 3 pixels to eliminate spurious borders. You can do this by using a negative spacing in your sizer Add() call. The cross-platform property sheet dialog \helpref{wxPropertySheetDialog}{wxpropertysheetdialog} is @@ -192,10 +199,12 @@ using the wxToolBar class as usual, for example to implement an optional formatting toolbar above the menubar as Pocket Word does. But don't assign a wxToolBar to a frame using SetToolBar - you should always use CreateToolBar for the main frame toolbar. -\item Deleting and adding tools to wxToolMenuBar is not supported. +\item Deleting and adding tools to wxToolMenuBar after Realize is called is not supported. \item For speed, colours are not remapped to the system colours as they are in wxMSW. Provide the tool bitmaps either with the correct system button background, or with transparency (for example, using XPMs). +\item Adding controls to wxToolMenuBar is not supported. However, wxToolBar supports +controls. \end{itemize} Unlike in all other ports, a wxDialog has a wxToolBar, automatically created @@ -221,15 +230,34 @@ wxID\_EXIT, it will do the right thing. \subsubsection{Control differences on wxWinCE} +These controls and styles are specific to wxWinCE: + +\itemsep=0pt +\begin{itemize} +\item {\bf wxTextCtrl} The wxTE\_CAPITALIZE style causes a CAPEDIT control to +be created, which capitalizes the first letter. +\end{itemize} + These controls are missing from wxWinCE: \itemsep=0pt \begin{itemize} \item {\bf wxCheckListBox} This can be implemented using a wxListCtrl in report mode with checked/unchecked images. +\item {\bf MDI classes} MDI is not supported under Windows CE. +\item {\bf wxMiniFrame} Not supported under Windows CE. \end{itemize} -This section is currently incomplete. +Tooltips are not currently supported for controls, since on PocketPC controls with +tooltips are distinct controls, and it will be hard to add dynamic +tooltip support. + +Control borders on PocketPC and Smartphone should normally be specified with +wxSIMPLE\_BORDER instead of wxSUNKEN\_BORDER. Controls will usually adapt +appropriately by virtue of their GetDefaultBorder() function, but if you +wish to specify a style explicitly you can use wxDEFAULT\_CONTROL\_BORDER +which will give a simple border on PocketPC and Smartphone, and the sunken border on +other platforms. \subsubsection{Online help in wxWinCE} @@ -277,6 +305,24 @@ shows folders under My Documents or folders on memory cards a known problem for PocketPC developers, and a wxFileDialog replacement will need to be written. +\subsubsection{Embedded Visual C++ Issues} + +\wxheading{Run-time type information} + +If you wish to use runtime type information (RTTI) with eVC++ 4, you need to download +an extra library, {\tt ccrtrtti.lib}, and link with it. At the time of +writing you can get it from here: + +\begin{verbatim} +http://support.microsoft.com/kb/830482/en-us +\end{verbatim} + +Otherwise you will get linker errors similar to this: + +\begin{verbatim} +wxwince26d.lib(control.obj) : error LNK2001: unresolved external symbol "const type_info::`vftable'" (??_7type_info@@6B@) +\end{verbatim} + \subsubsection{Remaining issues} These are some of the remaining problems to be sorted out, and features @@ -295,9 +341,6 @@ and the remaining area, by calling SHSipInfo. We also may need to be able to sho the SIP programmatically, with SHSipPreference. See also the {\it Input Dialogs} topic in the {\it Programming Windows CE} guide for more on this, and how to have dialogs show the SIP automatically using the WC\_SIPREF control. -\item {\bf Drawing.} The "Life!" demo shows some droppings being left on the window, -indicating that drawing works a bit differently between desktop and mobile versions of -Win32. \item {\bf 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. \item {\bf wxStaticLine.} Lines don't show up, and the documentation suggests that @@ -307,11 +350,26 @@ in report mode, using icons for checkbox states. This is necessary because owner are not supported on Windows CE. \item {\bf wxFileDialog.} A more flexible dialog needs to be written (probably using wxGenericFileDialog) that can access arbitrary locations. +\item {\bf 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. +\item {\bf 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 +be required.) +\item {\bf 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. \item {\bf 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. \item {\bf 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. +\item {\bf 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. \item {\bf Home screen plugins.} Figure out how to make home screen plugins for use with wxWidgets applications (see {\tt 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