Common Features

Table 1. Events

Support Level	Feature Name	Description
Supported	Clicked
Supported	Constructor
Supported	Destructor
Supported	DoubleClicked
Supported	DragDrop
Supported	DragEnter
Supported	DragLeave
Supported	DragWithin
Supported	GetFocus	In PowerBuilder, when a control gets focus and then loses focus, a series of LoseFocus and GetFocus events are triggered. In the mobile application, the rule is simplified as following: For the control which has focus, when tapping on the window, the control will not lose focus. For the control which has focus, when Hide() is called, the event order of the control (called Control A) is as following: Control A lost the focus. The window lost the focus. The control whose TabOrder is in the first place gets the focus (If the TabOrder of all controls is 0, Control A still gets the focus, even if it is invisible.)
Unsupported	Help
Supported on Web Only	Key	This event is supported in the Appeon Web application, but unsupported in the mobile application.
Supported	LostFocus
Supported	LostFocus
Unsupported	Other
Supported	RButtonDown	In the mobile application, you will need to turn on the Right-click mode in the Assistive Touch Bar, so that RButtonDown event will be triggered, but with the following exceptions: For SingleLineEdit and MultiLineEdit controls, no RButtonDown event will be triggered. For TreeView, ListView, DropDownListBox, PictureDropDownListBox, and DataWindow, when they are in the editing state, no RButtonDown event will be triggered.

Table 2. Functions

Support Level	Feature Name	Description
Supported	ClassName
Supported	Clear
Supported	Copy
Supported	Cut
Supported	Drag	In the mobile application, you may utilize the Assistive Touch Bar to avoid conflicts between drag and scroll. Please see the section called “Event-handling model” in Mobile UI Design & Development Guide (Mobile only). Avoid using Drag in the following situations, otherwise Drag will not take effect: In the control's LButtonDown event, avoid calling Drag(Begin) to drag another control. If Drag is triggered by Postevent, avoid triggering it before LButtonUp. The general rule is to avoid triggering Drag to drag other controls before LButtonUp. If no drag icon is specified, the default icon designed by Appeon Mobile will be used. The drag icon can be in any image format that is supported by Appeon Mobile, while in Windows, only ICO format is supported.
Unsupported	GetContextService
Supported	GetParent
Supported	Hide
Supported	Move
Supported	Paste
Supported	PointerX
Supported	PointerY
Supported	PostEvent
Unsupported	Print	Mobile platform difference: For Android: Print is unsupported. For iOS: Print is unsupported for all controls except for DataWindow control.
Supported	ReplaceText
Supported	Resize
Supported	SelectedLength
Supported	SelectedStart
Supported	SelectedText	If the second parameter is larger than the length of the remaining string, the number of the remaining string is returned, but in PowerBuilder, the second parameter is returned.
Supported	SelectText	If the second parameter is larger than the selected string length, the number of characters actually selected is returned, but in PowerBuilder, the second parameter is returned. In Windows, Newline and Carriage Return display as two bytes (\r\n), but in iOS and Android, they display as one byte (\n). This causes difference in multi-line text, for example, for a MultiLineEdit that has contents like "<newline>test1", selecttext(3,4) selects "test" in Windows, while selects "est1" in iOS and Android.
Supported	SetFocus
Supported	SetPosition
Supported	SetRedraw	In PowerBuilder applications, SetRedraw() is mainly to optimize the client performance, which is often called in pairs in a function or an event. In the mobile application, SetRedraw() will be handled differently: SetRedraw() should be used in pairs, and between SetRedraw(false) and SetRedraw(true) there should be no manual intervention such as clicking a button or popping up a MessageBox etc. UI painting of the corresponding object is suspended when SetRedraw(false) is executed, and will start painting again according to the latest properties after SetRedraw(true) is executed. Other than the above difference, SetRedraw() can be used in the same way and achieve the same result as in PowerBuilder.
Supported	Show
Supported	TriggerEvent
Supported	TypeOf

Table 3. Properties

Support Level	Feature Name	Description
Unsupported	Accelerator
Unsupported	AccessibleDescription
Unsupported	AccessibleName
Unsupported	AccessibleRole
Supported	BackColor	The RGB color will be displayed the same in iOS and Android as in Windows, but the system color such as ButtonFace may be mapped to a different color in iOS and Android, in order to conform to the mobile UI style. Transparent value is unsupported.
Supported	Border
Supported	BorderStyle	When BorderStyle is set to Box, the border displays the same in iOS and Android as in PowerBuilder; but when set to the other styles, the border will always display as rounded rectangle.
Supported	BringToTop
Unsupported	ClassDefinition
Supported	DragAuto
Supported	DragIcon	Other than the situations below, DragIcon is consistent with PowerBuilder. If DragIcon is not specified, use the default DragIcon and add the glow effect. If use the default icon in PowerBuilder as DragIcon, add the glow effect to DragIcon.
Supported	Enabled
Supported	FaceName	If the specified font also exists in iOS or Android, then the same font will be used, otherwise the font Helvetica will be used.
Supported	FontCharSet	Only ANSI character set is supported, and the display effect of other character sets may not be displayed as expected.
Supported	FontFamily	It depends on the FaceName. If the value is not consistent with the font corresponding to FaceName, it takes no effect.
Supported	FontPitch	It depends on the FaceName. If the value is not consistent with the FontPitch value of the font corresponding to FaceName, it takes no effect.
Supported	Height
Supported	HScrollBar	The scrollbar will be automatically displayed as the mobile-style scrollbar, rather than the Windows-style scrollbar.
Supported	Italic	The Italic property is font-dependent in iOS or Android, and not all of the fonts support italic.
Supported on Web Only	Pointer
Supported	RightToLeft
Supported	TabOrder	Switching focus via the Tab key is not supported. When a window opens, the focus will be automatically placed onto the control with the smallest TabOrder value (TabOrder>0).
Supported	Tag
Supported	Text	For "&" character in iOS and Android: Shortcut key operation is unsupported for all the controls in iOS and Android. If there are other characters following the "&" character, the "&" character will not display; and the following characters will not have underlines. The display rule for consecutive "&" characters: The only one "&" character will not display; An odd number (n) of consecutive "&" characters will display this number of "&" characters: (n-1)/2; An even number (n) of consecutive "&" characters will display this number of "&" characters: n/2. Additionally, the following two situations also use the above rules: Controls in the DataWindow with Text property, such as Button, Text, GroupBox. The "&" character used in the string in the Expression property of the Computed Filed object.
Supported	TextColor	Refer to the BackColor property.
Supported	TextSize
Supported	Underline	The Underline property is font-dependent in iOS and Android, and not all of the fonts support underline.
Supported	Visible
Supported	VScrollBar	The scrollbar will be automatically displayed as the mobile-style scrollbar, rather than the Windows-style scrollbar.
Supported	Weight	The Weight property is font-dependent in iOS and Android, and not all of the fonts support bold.
Supported	Width
Supported	X
Supported	Y

Prev	Up	Next
System Objects and Controls	Home	Controls

Supported PB Features for Appeon Mobile (Mobile only)System Objects and Controls

Common Features

Supported PB Features for Appeon Mobile (Mobile only)
System Objects and Controls