made more clear that GetItemRect() returns physical coords

[wxWidgets.git] / docs / latex / wx / wxmsw.tex

diff --git a/docs/latex/wx/wxmsw.tex b/docs/latex/wx/wxmsw.tex
index 2f6ec969bfce5c91e66aa47a8be5f74cf7eaa6b6..15031681d81768b74527b1936e1783c95d50362e 100644 (file)
--- a/docs/latex/wx/wxmsw.tex
+++ b/docs/latex/wx/wxmsw.tex
@@ -134,7 +134,7 @@ and unregister the button when you're done with it. For example:
   win->UnregisterHotKey(0);
 \end{verbatim}
 
   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
 since other applications will grab the buttons.
 
 There is currently no method of finding out the names of the special


@@ -165,7 +165,7 @@ and wxTopLevelWindow::SetRightMenu, for example:
 #endif
 \end{verbatim}
 
 #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
 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


@@ -252,6 +252,13 @@ Tooltips are not currently supported for controls, since on PocketPC controls wi
 tooltips are distinct controls, and it will be hard to add dynamic
 tooltip support.
 
 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}
 
 You can use the help controller wxWinceHelpController which controls
 \subsubsection{Online help in wxWinCE}
 
 You can use the help controller wxWinceHelpController which controls


@@ -316,9 +323,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.
 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
 \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


@@ -335,6 +339,9 @@ control, or have a separately-named control (wxHtmlCtrl), with a syntax as close
 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.)
 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
 \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