Unsupported Properties for Controls in Windows Forms – PB Docs 120


Unsupported Properties for Controls in Windows Forms

If your
application uses unsupported properties for Windows Forms targets, you must rework the application before you deploy it.

This table is an alphabetical
listing of unsupported properties. It also indicates the controls on which they are
not supported, and any notes that apply to specific controls.

Unsupported properties for Windows Forms deployment

Property

Controls

Alignment

OmCustomControl

AllowEdit

DatePicker

Activation

OmEmbeddedControl

BackColor

Tab, UserObject (see Tab properties)

Border

DatePicker

BorderColor

StaticHyperLink, StaticText

BorderStyle

DatePicker, Graph

Cancel

OmCustomControl

Columns

MenuCascade

ColumnsPerPage

UserObject

ContentsAllowed

OmEmbeddedControl

CurrentItem

MenuCascade

Default

OmCustomControl

DisplayType

OmEmbeddedControl

DocFileName

OmEmbeddedControl

DropDown

MenuCascade

FillPattern

StaticHyperLink, StaticText

Height

DatePicker

Help

Menu, MenuCascade

HScrollbar

DropDownListBox

IMEMode

All controls

LinkUpdateOptions

OmEmbeddedControl

Map3DColors

PictureButton

MenuItemType

Menu

MergeOption

Menu

ObjectData

OmEmbeddedControl

ParentStorage

OmEmbeddedControl

RaggedRight

Tab (see Tab properties)

RightToLeft

DataWindow, ListBox, ListView, TreeView

SizeMode

OmEmbeddedControl

StatePictureHeight

TreeView

StatePictureWidth

TreeView

Style

UserObject

TabStop

ListBox, MultiLineEdit

TabTextColor

UserObject (see Tab properties)

ToolbarAnimation

Menu

ToolbarHighLightColor

Menu

ToolbarItemSpace

Menu

FaceName property

If you use a bitmap (screen) font such as MS Sans Serif instead
of a TrueType font for the FaceName property, make sure you select
a predefined font size from the TextSize drop-down list.
PowerBuilder and .NET use different functions (CreateFontDirect and GdipCreateFont)
to render bitmap fonts and they may display larger in the .NET application
than in the development environment or a standard PowerBuilder application.
For example, text that uses the MS Sans Serif type face and the
undefined text size 16 looks the same as size 14 in PowerBuilder,
but looks larger in .NET.

Tab properties

The RaggedRight property for a Tab control works correctly if
the sum of the widths of all the tab pages is greater that the width
of the Tab control, and the MultiLine property is set to true.
However, when the PerpendicularText property is true, RaggedRight
is not supported.

While the TabPosition property value is tabsonleft! or tabsonright!,
and there is not enough room for all the tabs in a single row, the
tabs appear in more than one row, regardless of the Multiline property
setting. If you then dynamically set Multiline to true, the tabs
display on top of the Tab control, regardless of the TabPosition
setting.

Dual position display is not supported by the .NET Tab control (System.Windows.Forms.TabControl),
so the TabPosition value tabsontopandbottom! displays tabs on top
only. The tabsonrightandleft! value displays tabs only on the right,
and the tabsonleftandright! value displays tabs only on the left.

The BackColor and TabTextColor properties for a tab page in
a Tab control are not supported if the XP style is used.


Document get from Powerbuilder help
Thank you for watching.
Was this article helpful?
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x