Known Issues for Miscellaneous Items

If you change the screen resolution, there are differences between the appearance at design time and runtime.

Customized constructor events that are defined in NVUOs do not display in a PB Assembly referenced in the Solution Explorer. You must inherit from this NVUO to get information of the constructor event into the Script painter or PB Object Outline.

We are unable to replicate the behavior of Windows Help using HTML Help. Windows Help has been deprecated by Microsoft.

If pbwpf:window.skin is not the last property of a control in the XAML view and you select multiple controls to set their skin at the same time, this error appears: "The property 'skin' is set more than once."

In the REST client wizard or project painter, when you enter sample data for the primitive datatype such as a string or array of strings, then it will be failed to generate the assembly. For the primitive datatype, select Use primitive datatype (select Array option for an array of primitive datatypes) in the wizard or Project painter instead of entering the XML data and generating a new assembly.

Shortcut key for Assembly Dependencies window changed

In PB12.5 .NET IDE, the keyboard shortcut to open the Assembly Dependencies window (Ctrl+Alt+A in the previous version) is changed.

In the Windows XP theme, the 3-D property does not affect the appearance of the Checkbox control. It always appears as 3-D.

If you uninstall a .NET assembly case, you will see an non-English interface (such as the German language).

The public properties of an NVO inherited from a .NET class are not exposed in a .NET assembly.

The array property is not exposed in a deployed DLL, nor is an array's instance variable with name of "names." Other instance variables are exposed.

This error occurs if you set the Solution and then use FullBuildSolution. It does not matter if there is an error in the solution, or if IncrementalBuildSolution is used instead of FullBuildSolution. Sybase recommends that you use only FullBuildSolution without using <Solution first.

If you create a class member but do not save it, and then open the project, that new class member is listed in the Object tab.

You cannot toggle InputFieldNamesVisible after using PasteRTF.

The names of WPF SmartClient applications are always generated using all lowercase characters. Consequently, if the manifest specifies an application name that contains uppercase letters, the installation fails to install.

Workaround: Use only lowercase characters when you specify the WPF application executable name in the Project painter General page.

Fixed in 12.1 EBF.

In Windows 7, PowerBuilder .NET behavior is inconsistent when saving objects, depending on the type of object and the type of Windows user. For example, PowerBuilder might clear the layout view after an administrator saves a window painter, but not if a regular user launches the IDE using Run As Administrator.

If the current user does not have write permission for the directory assigned to the TMP environment variable, an error message appears in the Output window after the user attemps to create a project with a target or project wizard.

Workaround: Set the TMP variable to a directory for which the current user has write permission.

If two users add the same solution from a Perforce 2008 depot, then the first user checks in a new object for the solution, the second user can select Get Latest User (Recursive) to add the new object. However, although the new object is visible in the Solution Explorer of the second user, it is not added to that user's PBL directory.

Workaround: The second user must close and reopen the solution to complete the GetLatestUser action and get all the updates.

Although double-clicking a resource item in the Solution Explorer should open the editor associated with the item's file type, on FDCC-configured Windows XP computers, the Move dialog box opens instead. This does not occur on non-FDCC computers or on FDCC-configured computers using the Windows Vista operating system.

If your Windows license server host has IPv6 enabled, the served license does not perform correctly. http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc71335.1550/doc/html/ate1274477728881.html provides more details.

In PowerBuilder .NET, if you create a workspace in the root path of the c: drive, then create a target in the root path, the target does not appear in the Solution Explorer.