Limitations

Return to Introduction  Previous page  Next page

For some of the many features of PowerToolbar limitations apply. In this section you'll get a overview of these limitations.

 

Clarion versions supported

Onestep PowerToolbar supports Clarion 6.0 and later with reservation (see below) about the MDI client only being supported in Clarion 6.1 and later.

 

Mimic controls and menu items

Onestep It is possible to mimic menu items and create items on toolbars that directly correspond to menu items.  However, mimicking menu items does not work with all the mimic attributes correctly.  It does, however, work correctly for icons, tooltips, text, hide/unhide, enable/disable for controls on the toolbar or the window.  Only icons and hide/unhide seem to work correctly on menu items.  This limitation is in review and we hope to fix it in early 2010.

 

PowerToolbar MDI Client Extension Template

Onestep This template is not compatible with Clarion 6.0 (tested with build 0.915).  The Clarion RTL does not always post EVENT:GainFocus when a window gains focus, so the MDI client buttons are not enabled.  Note that this was fixed probably in Clarion 6.1.  It does not happen in Clarion 6.3 build 9053 or 9058. 

 

Clarion 7

Onestep Clarion 7 cannot support owner drawn menus.  There for it is currently impossible for PowerToolbar to support menus under Clarion 7.  The template disables the option and turns it off automatically so it will not affect the functionality of the application once converted to Clarion 7.  However we want to point out that Clarion 7 has various theme options for menus that can at least partially replace the menu themes in the PowerToolbar. 

 

Clarion 8

Onestep With May 2012 release of Powertoolbar it does support menu theming in Clarion 7 and Clarion 8.  While this has been in testing for a while we appreciate any feedback on any issues that you may run into!  

 

Clarion 10

Onestep Somewhere along the way in Clarion 10 (could be in previous versions as well), a flicker would appear in the app-frame client area if a centered wallpaper image was used.  It would not occur if the image was larger than the client area.  The solution is to add:

 

  0 {PROP:Buffer} = 1

 

right after the window opens, see image of the embed tree below.

 

Docs_Flicker

 

Clarion controls in Toolbars

Onestep Clarion spin and entry controls on toolbars are themed (flat) even when Classic Windows theme is used in Windows.  We are looking into a fix for this.

Onestep Clarion controls added to toolbars cannot be on tabs on the window.  This can cause bleeding through of other controls on the tabs.  To work around this, simply place the controls on the window and hide/unhide them as needed when tabs are selected.

Onestep See section below on toolbars on dockable windows:

 

 

Toolbars on Dockable windows with Clarion controls in toolbar

 Onestep If you are using PowerToolbar control on a dockable window and you are adding Clarion controls to it, these controls will NOT be moved into the toolbar.  To fix this you must remove the docking attributes from the window and add them in code in the WindowManager.Init method (ThisWindow.Init) at priority 8110 - after the call to the Toolbar.Init method.  Then the controls will be moved correctly into the toolbar.  Example:
 
  Toolbar4.Init()                          

                                           

  ! [Priority 8107]                        

 

  Window{Prop:Docked} = DOCK:Bottom

  Window{Prop:Dock}   = DOCK:Bottom

 

AppFrame Toolbar

Onestep Clarion toolbars and merging Clarion toolbars is NOT supported. If you got any merging toolbars in your application these will most likely corrupt the display of PowerToolbar.

Onestep PowerToolbar will take up the entire Clarion toolbar. Other controls will be overdrawn. (This does not apply when the toolbar is populated into a Window)

Onestep Clarion's Toolbar Browse Control template is not compatible with PowerToolbar (use the PowerToolbar MDI Client template instead).

 

 

Clarion Menus

Onestep If you choose to override the main Clarion menu you can NOT have menus in any child windows, i.e. MDI windows.   

Onestep All items in menu must have a Use-variable set

Onestep All font colors must be COLOR:NONE

Onestep Width must be "default" on all items

Onestep Height must be "default" on all items

Onestep Top level menu-items is not supported

Onestep Runtime added top level-menus are not supported

Onestep The text from the Msg() attribute is not drawn in the status bar.

Onestep HIDE attribute on MENU is not supported.  Use Hide(?MenuLabel) or ?MenuLabel {PROP:Hide}=TRUE in code instead to hide menus.  HIDE is supported on menu ITEMs.  However, it can cause problems and we strongly suggest NOT using HIDE on menu items and hide them at runtime!

 

Native XP Style

Onestep Native XP style requires PowerXP-Theme. If PowerXP-Theme isn't included in the application, the Toolbar-style will fall back to OFFICE2000.

 

XP-Theme colors

Onestep To use colors of the currently selected XP-Theme in Office2003-style, you have to include PowerXP-Theme in your application. If not, colors will fall back to "blue theme".

 

Windows versions and Toolbar styles

Onestep When running under Windows 95/NT4 only OFFICE2000 style is available (all other styles will fall back to OFFICE2000)

Onestep OFFICE2000, OFFICEXP and OFFICE2003 is available under Windows 98, 2000, XP and 2003.

Onestep NATIVEXP is only available when running under Windows XP (or 2003 with Windows Visual Themes switched on).

 

Tooltip

Onestep Balloon type tooltip is only available on WindowsXP and later.

 



Direct link to this page on our website: http://www.icetips.com/manuals/powertoolbar/limitations.htm