Known Issues for the WPF Script and XAML Editors

When you drag a control from a window to a Tab control on the window, then double-click the control that you dragged, the Script view opens for that control. If you then switch to the Layout view, drag the control from the Tab control back to the window, and double-click the control again, the Script view for the control is disabled.

Workaround: Right-click the current tab at the bottom of the Script view and select Close, then reselect the control name in the top left drop-down list. You can also close and reopen the Window painter to enable the Script view for the control.

Many types of invalid input, including undefined variables, incorrect implicit conversion types, argument errors, and so on, are not detected by the PowerBuilder .NET compiler.

When you modify text using the Quick Replace or Replace in Files tabs of the Find and Replace dialog box, the text may be replaced in the source files, but not in the Script views of open painters. This can occur when these two check boxes on the Documents page of the Options dialog box are not selected: "Detect when file is changed outside the environment" and "Autoload changes, if saved." By default, the first check box is selected, but the second one is not.

Workaround: Reload the solution to view the replacement text in the painters.

After you delete a function, event, or other item containing syntax errors, the syntax errors remain in the Error List.

An instance variable that you declare in a Script view is not immediately added to the PB Object Outline, even after you have saved the window or object for which you make the declaration.

Workaround: To view the instance variable in the PB Object Outline window, close and reopen the window or object.

When you open an ancestor and one of its descendant objects in the Script view, event state icons in the descendant have two colors, indicating that scripts exist for both objects even when only the ancestor event is scripted. In a related error, the Extend Ancestor option is enabled in the Script view and in its context menu when only the ancestor event is scripted.