Known Issues for Third-Party Controls

Learn about known issues and apply workarounds for third-party controls in PowerBuilder .NET.

Note: Support for third-party controls in the PowerBuilder .NET IDE is incomplete, and is available only for testing purposes. More comprehensive support will be provided in a maintenance release shortly after the product release. When testing this feature in the product release of PowerBuilder 12.0, take extra precautions, such as frequently saving your code and making backups.

Third-party control issues
CR#	Description
621580	Cannot use resources from relative paths for third-party controls. If you use resources, such as image files, for third-party controls, you must use full paths to identify them at runtime. You can use either full paths or relative paths to identify resources that you assign to PowerBuilder WPF controls.
621554	Double-clicking some third-party controls does not open the Script view. The Script view does not open automatically when you double-click some third-party controls, such as RadCalendar, in a Layout view. This issue also exists in Visual Studio. Workaround: Open the Script view for the window or parent control and select the third-party control from the top left drop-down list.