Professional UI Solutions
Site Map   /  Register
 
 

Forum

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 General Discussion » MDI Maximised Child Window Collapse All
Subject Author Date
James Hughes Sep 21, 2003 - 5:04 AM

Hi There,

I am looking at the trial version with a view to registering for the full license.

However I am having a problem with test application I have built. I used the VC6 prof-UIS appwizard to create a MDI application, when I run it and maximise the child window CPU usage goes constantly to 80-90% (for the task).

I built the sample MDI application you supply and had the same result with that.

Cheers

B.T.W. OS is WindowsXP (SP1)

Sergiy Lavrynenko Sep 21, 2003 - 9:01 AM

Dear James,

The CPU usage effect is specific for the debug versions of MDI apps, especially if app uses Office 2003 style which is slower than other styles due to complicated painting routines. Like standard window menu line, the Prof-UIS menu bar needs to add/remove system-menu-like icon at right and minimize/maximize/restore/close buttons at left when an MDI child window has been maximized/restored. The size of menu bar can be changed after adding/removing MDI-specific buttons. As result, mutual positions of all the bars inside a frame window may also changed. So, Prof-UIS needs to recalculate mutual layout of control bars when the maximized state of the MDI child frame window is changed. This recalculation causes quick CPU usage effect which is not visible in release builds.

Best regards, Sergiy.

James Hughes Sep 21, 2003 - 11:43 AM

Dear Sergiy,

Thanks for the quick response.

The CPU is constantly at 80-90% when the child window is maximised, and this goes for the Windows 2000, XP and 2003 styles. I understand that the debug libaries are going to be slower than the released :)

Since posting the first comment I have found that running the application(s) outside of the VS environment the CPU useage is just fine.

Thanks again
James