Modernize your PowerBuilder Applications

FAQ

What is the current version of Ultimate Suite for PowerBuilder?

Visit USPB release history

Supported versions of PowerBuilder

  • USPB 2022: PB 12.5 and higher
  • USPB 9.x: PB 10.5 to PB 2019

What is the difference between PB UI Themes and Ultimate Suite Themes?

Both features define styles and colors, but not to the same controls:

  • PB UI Themes apply to Standard PB controls
  • Ultimate Suite Themes apply to Ultimate Suite controls

For a consistent UI, the Ultimate Suite themes match the standard PB UI Themes. So you should apply the same theme to both sets of controls.

You can learn more about PB UI Themes and how to define them with this video.

How do I implement Ultimate Suite for PowerBuilder?

The .zip file you have received contains some .PBDs. To test the Ultimate Suite for PowerBuilder controls in your application, simply add the advguicontrols.pbd, advguithemes.pbd and advguiobjects.pbd files to your targets library list. If applicable, also add the canvas.pbd file to your target's library list. You can test these controls with your application.

Does Ultimate Suite for PowerBuilder work well with Citrix?

Ultimate Suite for PowerBuilder Controls work fine with Citrix. Depending on the settings some degradation with the graphics may occur.

Does Ultimate Suite for PowerBuilder support Unicode?

All the Ultimate Suite for PowerBuilder Controls are able to display Unicode characters.

When I purchase a license will I have the source code (PBLs)?

Only the Enterprise version of Ultimate Suite for PowerBuilder is delivered with the source code.

Is Ultimate Suite for PowerBuilder compatible with PFC?

For the most part, they should work well together. The one thing you will have to look at is PFC sheet management if you choose to use PowerDock with TDI. If you use PowerDock with MDI or don't use PowerDock at all, there is no other issue.

How does the powermenu work together with PFC?

My frame window is today inherited from w_frame, but for powermenu to work it must be inherited from w_ribbonwindow.

You have to inject the w_ribbonwindow object into your applications window hierarchy. This is easily done by editing the source and changing the ancestor on a few windows. One thing to note is that menu management is different with the menu. If you have separate menus for your sheets, then a little extra work is needed to make that display properly.

In the trial version the pictures are a bit blurred. Will it be different with the purchased version?

The quality of the images that appear in the UI will depend on the quality of the images being used. The sample application uses some of the built in PB images which are 16x16. When scaled up in size, they don't look very good. If you use a high quality images, your application will look much nicer.

The Helpfile.chm doesn't open properly

Depending on the version of Windows you have, you may need to modify the file properties (right click - security) to display it properly.

Why the canvas.pbd file is not necessary for newer versions of PowerBuilder?

Newer versions of PowerBuilder allow you to import a PBNI extension (PBX file) directly into a PBL. In the past (PB 11.x or older), it had to be built into a PBD and attached to the library list. U_canvase (which was in canvas.pbd) is now in the pbl.

Is there any way that we can use Powermenu features without having to inherit from w_ribbonmenu?

We use PFC framework and it requires our application to inherit the main window\frame from w_frame (which comes with PFC package). Is there any way that we can use Powermenu features without having to inherit from w_ribbonmenu?

You can "inject" the w_ribbonwindow between your PFC window and your main application frame. You would just have to change w_ribbonwindow to inherit from the PFC frame then change your main application window to inherit from w_ribbonwindow. One client is doing this with success.
You can also duplicate all the functions, events and objects in w_ribbonwindow on your main application window.
Note: it's valid for the permanent version not the trial

When I run my application from PowerBuilder all I see is white where the UI Controls should be rendered. Why is this?

The Ultimate Suite for PowerBuilder Controls rely on the PBNI object canvas.pbx to render graphics. Sometimes PowerBuilder loses track of where this file is.

To avoid this problem:

  1. Make sure the canvas.pbx file is in the same directory as your application PBLs
  2. If the canvas is in the same directory as your applicaton PBLs, move it to a directory that's in your PATH environment variable (e.g. the System32 folder).

If I use these controls, will I be able to compile the application using DLL’s (machine code), or just PBD(Pcode) files.

Yes, you can deploy using DLL's without any problems related to the UI controls.

We're in the process of migrating our client-server application to the web / Cloud using PB Cloud Pro and Appeon Powerserver. Are USPB Controls compatible with this setup?

Yes, USPB is compatible with PowerServer 2019 and later We have conducted tests and the results were positive. However, we highly recommend you carry out your own tests to ensure it aligns with your specific expectations and requirements.

Both Appeon and USPB offer Ribbon Bars. What differentiates the USPB Ribbon Bar from Appeon's?

Both Appeon and USPB provide excellent Ribbon Bars, and the choice ultimately depends on your specific needs. One of the standout features of the USPB ribbon is its ability to leverage your existing PB Menu as its source, enabling a quicker ribbon creation without the need to modify any menu-clicked event code. You will keep maintaining your PB menu as usual, all changes will automatically reflect in the USPB Ribbon. Additionally, the USPB ribbon is an entire window control, offering a contemporary appearance with a quick access toolbar in the caption and a backstage view, which is the menu that emerges upon clicking "File."

Can the integration of USPB libraries potentially impact the performance of our application?

All USPB Controls are composed of PB code. You compile, deploy and execute them with your own PB code. Currently, there haven't been any reports or challenges regarding performance drops. Many extensive applications utilize USPB without experiencing any performance hitches.

Our application is based on the PFC. Is it possible to continue using PFC with Ultimate Suite? Particularly, if we inherit window objects from USPB controls, how might PFC be affected?

USPB Controls seamlessly integrate into any window or user object in the same manner as typical PowerBuilder controls. The exceptions are the ribbon window and the Single Page Application (SPA) windows provided by USPB. Guidance on how the ribbon window can be incorporated into an inheritance chain is provided in our help documentation. If you're leaning towards this integration, we would advise opting for the Enterprise license. Having access to the complete source code of USPB will facilitate smoother integration and mitigate any potential challenges.

Are the DLL multilingual in the PBUS Professional edition, i.e. can you modify the Yes/No Toggle button from the parameters and change the text to be displayed in Dutch?

The toggle button has two properties that you can set in the IDE: #OnText, #OffText.You can place your localized text here. This is possible for all controls featuring properties that allow you to define the text to be displayed.

Is there any way you can inherit the controls to all your PB objects without having to apply the UI modifications object by object?

USPB, like many other UI control libraries, are made up of controls that you plug into your application as you need them.

Unless the controls you're using on your windows inherit from a common ancestor that you have in one of your PBL's, I would say this request would be difficult. For example, if you're using the PowerBuilder command button on your windows; there would be no way to automatically convert these to use the USBP Command Button. If you have an object that inherits from the PowerBuilder command button, and you use that object on all your windows, you can probably change that object to inherit from the USPB Command Button instead of the PB control.

One notable exception would be the MessageBox function. PowerBuilder allows us to override global functions with our own global functions. By creating a new function object named MessageBox, PowerBuilder would route all MessageBox calls to our function. In here, we can call out to PowerMessage to display a more modern message box to our users. One thing to note is that we can overload our function objects by editing the source and adding additional function signatures. This would allow us to create many overloads for the MessageBox function.

Is there a way to inherit the controls to all PB objects without having to individually modify each object for the UI?

USPB, like most UI control libraries, is designed to offer controls that can be seamlessly integrated into your application as per your needs. If you have controls within your application that derive from a common ancestor in one of your PBLs, the process is greatly facilitated. For instance, if you employ a custom object that inherits from the PowerBuilder command button across several windows, this object can be adapted to inherit from the USPB Command Button, making the transition smoother. However, it's worth noting that controls without such inheritance can't be automatically converted to their USPB counterparts, so some manual adjustments may be needed in those cases.

When I buy a license, do I get the source code (PBLs)?

The source code is available with the Enterprise version of Ultimate Suite for PowerBuilder.

 

Learn More

For more information check out the PowerBuilderTV webinar on How to Modernize the Look of your PowerBuilder Applications

Click to try or to get pricing information for Ultimate Suite for PowerBuilder.