Known Issues for WPF Controls

If you select two controls of the same type in a left-to-right order, and then copy and paste the controls together, the scripts of the pasted controls are inverted, with the script of the leftmost pasted control corresponding the script of the original rightmost control, and the script of the rightmost pasted control corresponding to the script of the original leftmost control.

Workaround: Copy and paste controls of the same type one control at a time.

If you select a Tab control and a different type of control, such as a CommandButton, and then copy and paste them together, the second control is listed twice in the Script view drop-down list and in the PB Object Outline, and causes a compiler error when you build the application.

Workaround: Copy and paste Tab controls and other controls separately.

When you call SaveDocument in a WPF RichTextEdit control, the text that is saved depends on the current focus. If the focus is in the header, only the header text is saved. Similarly, if the focus is in the the document body, only the content of the body is saved, and if the focus is in the footer, only the footer text is saved. InsertDocument also inserts only that part of a document that corresponds to the area of the RichTextEdit control that has focus.

You can add pictures to the PictureName collection in a PictureListBox, DropDownPictureListBox, or ListView using the top button in the Property editor for the PictureName property. The tooltip for this button is "Insert before selected item." If you then delete all pictures that you added, the button becomes disabled.

Workaround: You can add pictures again with the second button in the Property editor. The tooltip for this button is "Insert after all items."

If you create a standard visual object based on the DropDownListBox and do not select its ShowList property, then drag this control from the Solution Explorer to the middle of a window, the height of the visible part of the control is extended. This does not happen when you place the same control at the top or bottom of the window.

In the Windows 7 IDE, if you place a standard visual object based on a CommandButton onto a custom visual user object, the height of the button is extended.

Workaround: Manually adjust the size of the controls.

When you select the Add Tab context menu item on a Tab control at design time, you may see a slight flickering on the monitor.

If you add several tab pages to a Tab control, PowerBuilder automatically adds arrow buttons to allow users to click through all of the tabs, some of which are hidden. However, in PowerBuilder .NET, the arrow buttons can hide part of the text of a TabPage, giving it a cut-off appearance at design time and runtime. At design time, the outline of a tab page may appear outside the boundaries of the main Tab control.

If you add mixed-case text to a SingleLineEdit control while the TextCase property in the Properties view is set to Upper! or Lower!, the text does not automatically use the case indicated by the property.

Workaround: You can change the case by selecting a different value for the TextCase property, then reselecting the original value.