Professional UI Solutions
Site Map   /  Register


Please Log In to post a new message or reply to an existing one. If you are not registered, please register.

NOTE: Some forums may be read-only if you are not currently subscribed to our technical support services.

Forums » Prof-UIS Tech Support » ProfUIS 2.88 and Windows 7 Collapse All
Subject Author Date
Carsten Pedersen Apr 12, 2010 - 12:23 AM


We’ve created an application in VS 2003 (MS7.1) using ProfUIS 2.88. We have just tried to run the application on windows 7, and it starts up as it should, but there are differences to the normal WindowsXP system that we currently use.

Our application is built as a dialog, with child dialogs inside multiple tab containers. With Windows 7 we have GUI updating issues, as some of the child dialogs dont redraw as they do on Windows XP.

The program is very large, so for now it’s not possible to send a stripped down version of the project. Could you clarify if certain redraw techniques are needed in Windows 7 that weren’t needed in Windows XP?


Thanks in advance

Carsten Panch Pedersen

Technical Support Apr 13, 2010 - 10:09 AM

The DWM subsystem (Desktop Window Manager), which is present both on Windows 7 and Windows Vista does not bring any repainting issue and even removed flickering you could see on Windows XP. The DWM/window glass based desktop is based on the background desktop surface which is processed by the running DWM.EXE process for adding effects like glass and shadows. The repainting issues of your dialogs can depend on one of the following:

1) Your dialogs do not have the WS_CLIPSIBLINGS|WS_CLIPCHILDREN styles. Please check these styles are present in all of your dialogs, including the main dialog. These styles should also be present in tab container windows.

2) You are using some hardware accelerated painting in some controls created inside some of your dialogs. If you need the hardware accelerated painting (3D or Video output), then please implement it in the standalone window which does only the hardware accelerated output, does not perform anything else and does not contain any child windows. For example, the AviFrames sample application plays video inside the scrollable container window. You can scale the video frame and the scroll bars will appear. The scrollable container window contains scroll bars and child window which is responsible for the video output. If you scroll the video frame, then the child video window is moved. That’s how the video scrolling is implemented in this sample application. The video player window does not perform anything but video frames painting. We tried to implement similar sample application and perform the video frame painting directly into the scrollable container window and we saw very funny trash and flicker effects on the screen.