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 Tech Support » Exclude a control bar from being profiled. Collapse All
Subject Author Date
Marcus Gebler Jan 31, 2006 - 8:45 AM

Is it possible to exclude a control bar from being profiled ( CExtControlBar::ProfileBarStateSerialize )?


Is it possible to dock the control bars within a mdi client window and to profile them ( CExtControlBar::ProfileBarStateSerialize ) without the ugly flickering (offscreen docking and profiling) ?


With best regards
 
 Marcus

Marcus Gebler Jan 31, 2006 - 1:10 PM

1. When will this version be available?


2. Sorry, I meant of course the MDI child frame window. In my case I am creating a new MDI Window by calling the CreateNewChild method. Then a xml-file, which also includes information about the control-bars that have to be docked, is parsed and the control bars are created (but not docked at this moment). The xml-file also includes the profile-data (redirected via CArchive + CMemFile), which is propagated by calling the CExtControlBar::ProfileBarStateSerialize method. This loading-procedure leads to a lot of resizing and positioning of the docked control bars - and looks like "flickering". Is it possible to move the MDI child frame window "off screen" - do all this loading stuff - and finally move the window to its ultimate position - or is there a better solution?


3. How will the upcoming "Prof-UIS ribbon control" work? Concatenating dialog bars?


4. Will there be a "Office 2005" - PaintManager theme ?


Best regards
  Marcus

Technical Support Feb 1, 2006 - 11:05 AM

1. We plan to add this feature within two months.

2. There is nothing special about the described design. If the bars in your MDI child frame window produce some flickering, then the same code in the main frame window should produce the same effects. Please ensure the following: you have created, restored or initially docked all the bars and only then performed the UI initialization. Invocations of COM API before initializing the control bars may let your MDI child frame window appear on the screen earlier than it should.

3. Although the Ribbon window in Office 12 is a solid control, we have to implement it as a container because someone will certainly need to insert dialog pages into it.

4. We guess you mean Office 12 by "Office 2005". This theme can be implemented as a new skin. Of course, we need to support the smooth aero behavior based on fade-in / fade-out effects.

Technical Support Jan 31, 2006 - 12:06 PM

At present the serialization of control bars is based on using the CArchive class and it is impossible to exclude a particular bar from being serialized. But we are working on an alternative state serialization sub system, which is based on tree like named parameters and XML. It allows you to exclude some bars and does not require all the control bars to have been created when it starts restoring the state.

Please tell what you mean by "dock the control bars withing a mdi client window"? Control bars can be docked inside the frame window only. The frame window can be an SDI main frame window (the CFrameWnd class), MDI main frame (the CMDIFrameWnd class) or MDI child frame window (the CMDIChildWnd class). Control bars cannot be docked in the MDI client window.