Learn about known issues and apply workarounds for inheritance in PowerBuilder .NET.
CR# | Description |
---|---|
624278 |
Deleting ancestor menu items can cause descendant menus to fail integrity check.
When you delete a menu item in an ancestor menu, the Object Integrity Failure dialog box sometimes appears when you try to open the descendant menu, and the descendant menu may be blank if you subsequently open it in the Menu painter. Workaround: Click OK in the Object Integrity Failure dialog box, then select PowerScript Editor in the Open With dialog box. The editor highlights the deleted menu item in source code with a straight red underline. If you comment out or delete all Type ... End Type and On ... End On clauses containing the underlined menu item, you can open the descendant menu again in the Menu painter. |
606121 |
Inherited third-party control does not show default event.
If you select the check box (on the page of the Options dialog box) to display unscripted .NET events in the Script editor, you see the default .NET event for a third-party control that you add to a window. However, when you inherit from the same third-party control and add the inherited object to a window, you cannot see the default event. |
577019 |
Properties view does not show inherited variables.
In PowerBuilder .NET, if you declare instance variables on a custom visual user object, and then inherit from that object, the variables are not included in the Properties view of the child user object. |