Lines Matching defs:on
27 \subsection{Themed borders on Windows}\label{wxmswthemedborders}
37 already paint themed borders where appropriate. To use themed borders on other windows, such
40 Note that in wxWidgets 2.9 and above, wxBORDER\_THEME will be used on all platforms to
46 what style should be passed, you can use (on Windows only) the function wxWindow::GetThemedBorderStyle()
48 wxBORDER\_SIMPLE will be returned; on Windows 95/98/NT/2K, wxBORDER\_SUNKEN will be
49 returned, and on XP and above where theming is turned on, wxBORDER\_THEME will be returned.
52 In 2.8, wxBORDER\_THEME is normally interpreted as a wxBORDER\_SUNKEN on platforms other than Windows.
56 wxWinCE is the name given to wxMSW when compiled on Windows CE devices;
149 You won't get a wxCloseEvent when the user clicks on the X in the titlebar
150 on Smartphone and PocketPC; the window is simply hidden instead. However the system may send the
180 PocketPC dialogs have an OK button on the caption, and so you should generally
181 not repeat an OK button on the dialog. You can add a Cancel button if necessary, but some dialogs
183 to make up for it). When the user clicks on the OK button, your dialog will receive
188 Smartphone dialogs do {\it not} have an OK button on the caption, and are closed
197 // No OK/Cancel buttons on PocketPC, OK on caption will close
207 provided, to show settings in the correct style on PocketPC and on other platforms.
253 using a nested menu on the right menu button. Any toolbars are simply ignored on
260 or not. The close button on a window does not call the window's
274 \subsubsection{Control differences on wxWinCE}
292 Tooltips are not currently supported for controls, since on PocketPC controls with
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
319 Application Manager and install the CAB file on the device,
342 Allowing the user to access files on memory cards, or on arbitrary
344 shows folders under My Documents or folders on memory cards
401 the command bar on Mobile 5, so the menubar functions need to be rewritten
412 the {\it Programming Windows CE} guide for more on this, and how to have dialogs
415 the correct size on the emulator, but too small on a VGA Pocket Loox device.
425 \item {\bf Focus.} In the wxPropertySheetDialog demo on Smartphone, it's not possible to navigate
428 \item {\bf OK button.} We should allow the OK button on a dialog to be optional, perhaps
431 than preprocessor tests, so that the same WinCE application can run on different
436 not very useful on Windows CE; however, we could perhaps destroy/restore a modeless dialog's menubar
437 on deactivation and activation.
446 \item {\bf Dialog captions.} The blue, bold captions on dialogs - with optional help button -