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 » Another tabbed bars problem Collapse All
Subject Author Date
Offer Har Nov 15, 2006 - 7:45 PM

Hi,

I have a bar that in case of a fatal error in it should not be switched to another tab. How can i disable to tab switching from the code?

Thanks.

Technical Support Nov 16, 2006 - 10:25 AM

You can override the following internal virtual methods of the CExtControlBar class to prevent one control bar from being docked to another one:

    virtual bool _CanDockToTabbedContainers(
        CExtControlBar * pDestBar
        ) const;
    virtual bool _CanDockLTRB(
        CExtControlBar * pDestBar
        ) const;



Offer Har Nov 16, 2006 - 10:31 AM

That’s not what i meant.
This is the scenario:

1) I have Bar1 & Bar2
2) Bar1 & Bar2 are tabbed.
3) Bar1 is the topmost one.
4) User presses a check-box in Bar1
5) As long as this check-box is checked, Bar1 should be on top, and moving to Bar2 (by pressing its bar) should be disabled.
6) If the user un-check the check-box in Bar1, he can move freely to Bar2

Hope it is clear now...

Technical Support Nov 23, 2006 - 11:59 AM

The disabled window state of control bars is not supported in Prof-UIS (nor in MFC). So it is not possible to prevent selection of a control bar unless it is destroyed or hidden.

Offer Har Nov 23, 2006 - 12:05 PM

Dear Support,
When i have a tabbed control, i can prevent the tab switching from happening. This is what i seek.
If you cannot disable the control, at least give me a method to prevent the tab-switching to another dialog, like i can do in a tab control.

Offer Har Nov 29, 2006 - 10:29 PM

Any idea how to solve this problem?

Technical Support Nov 30, 2006 - 11:15 AM

This feature is not supported in Prof-UIS and it is not too easy to implement it. Besides you would have to think over some cases like a supposedly disabled control bar should be somehow disabled when the uses simply closes (hides) up all the other enabled control bars. We would put this feature in the category "custom software development".