Known Issues for the WPF DataWindow

In the Design view of a new Freeform DataWindow object, you can set the border properties of text controls. The border appears correctly in the Preview view and at runtime, but does not appear in the Design view.

You cannot enter or edit the AccessibleName property. Any value you enter for the Pointer property is used as the value for the AccessibleName property.

Using Filter in a child of a Composite DataWindow object does not filter the contents. Using InsertRow does not insert a new row. Using DeleteRow does not delete the row.

If you drag a control outside the DataWindow object boundary by going too far to the right or left, the control disappears. To return it to the editable area, select the control in the Document Outline and then edit the X and Y position properties.

The default value for Tooltip.Delay.Visible is 0 instead of 32000. At first this works, but if you change it and reset it to 0, the tooltip does not appear. The default values for Tooltip.TextColor and Tooltip.BackColor are both 0. The tooltip is legible at first, but if you change the background color, then reset it to 0, the tooltip appears solid black.

The Preview view displays the number of rows retrieved, and the current row you have selected. If the current row has five digits or more, the fifth digit is truncated.

If a database value does not exist in the drop-down DataWindow, the value does not appear when the column is selected. If you select a value in the drop-down DataWindow, the column does not show the correct value from that row.

When you save a DataWindow as a PDF, the font size changes. The font name may also change.

You can assign PNG images to pictures, buttons, and columns in a DataWindow. However, when you set image-related properties at runtime—such as BackColor for a button, Invert for a picture, or BitmapName for a column—the colors of the assigned PNG image do not appear as expected. This issue does not occur in PowerBuilder Classic.

Previewing a DataWindow that uses more than 800MB of memory may cause the PowerBuilder .NET IDE to fail. The failure may also occur, or an OutOfMemory exception may be thrown, when you retrieve the same data at runtime.

If you change the Backedge properties for the Series axis and Values axis, they are not included in the graph. You can set the BackEdge properties only for the Category axis.

Because some of the properties are different, when you change a pie graph to a cone graph at runtime, the graph does not draw correctly.

If you delete a column, then select Undo and Redo, the Grid DataWindow object contains a blank column. You may also see an object reference error.

If you add columns and computed fields by placing them within the grid, the new column or computed field overlaps the existing columns.

Workaround: You can place the new columns or computed fields outside the existing grid, but the behavior of such columns and fields is unpredictable.

Controls in a Label DataWindow object do not appear in the Design view if they are moved to the right. However, they appear correctly in the Preview view and at runtime. This applies to controls within the label area and those outside the label area.

Using InsertRow in a Label DataWindow does not insert a new row. Using DeleteRow does not delete the row.

If the user enters a value of the wrong datatype, there is no error unless you define a validation.

When you save or open a RichText DataWindow object using a file of 400KB or greater, the performance is slow.

At runtime, if you right-click the RichText DataWindow object, select Properties, then unselect Popup Menu, the context menu providing access to the Rich Text Edit dialog box does not appear again until you close and reopen the RichText DataWindow object. However, if you right-click on an input field, the context menu for the input field appears.

In a RichText DataWindow, if the file size exceeds one page, the text for each row after the first page is truncated incorrectly.

If a RichText column crosses two pages, the text is truncated incorrectly at the page break.

If a WPF application user collapses the last top-level node of a TreeView DataWindow, then tries to use the vertical scroll bar to scroll to other TreeView nodes, the application fails. Occasionally, using the scroll bar while other nodes are collapsed may also cause an application failure.

You can set pictures with the "string (pic_path)" DataWindow expression, where pic_path is a DataWindow column that saves the absolute paths of the pictures to use for TreeView DataWindow nodes.