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 » So many things missing !! Collapse All
Subject Author Date
Akash Kava Sep 3, 2004 - 11:01 AM

1) Events of CExtTabPageContainerWnd :
   How to get notification about which page got active recently, likewise if i want to hide and show certain toolbars according to the page viewed in this class.


2) CExtTabFlatWnd :
   This control doesnt work on CFormView, we can see, we can not select any Tab, neither there is way to receive any events.
   This control’s First Tab becomes invisible when we click 2nd Tab only first time in CView, from next time onwards it works.

3) CExHookSink:
    Class is missing in documentation

4) Suggestion:
    New Class CExPagedView which can be used in MFC with document/view architecture. CExPagedView must be able to create and hold, switch multiple Views derived from CView. Also it must have OnPageSelected function which can be overridden to get notification of current selected View.

5) Too Big Examples:
    To understand CExtTabPageContainerWnd, I had to read Page example almost 10 times to find out where control is created. Ideal example would be One Control with 2 child controls, here you have created N number of controls which takes so long to analyze.

6) Is it good trick to earn money?
    Is it your policy to force users to come back to you for support? not provide proper and complete documentation? If that is the case, I would have searched number of code websites, get one one code from there and integrated it if I had to spend time to go through each and every forums etc. I thought I will get nicely MSDN sort of documentation which would contain everything!!!

Technical Support Sep 3, 2004 - 1:03 PM

  • Events of CExtTabPageContainerWnd :
    How to get notification about which page got active recently, likewise if i want to hide and show certain toolbars according to the page viewed in this class?

    The CExtTabPageContainerWnd does not provide this notification directly. But you can use your own tab control inside tab page container and catch the tab selection event. This tab control should be derived from the CExtTabsWndImpl < CExtTabWnd > type. The instance of newly created tab control is returned from the CExtTabPageContainerWnd::OnTabWndGetTabImpl virtual method. By overriding the CExtTabWnd::OnTabWndSelectionChange virtual method in your tab control, you may catch the tab selection event and even prevent some tabs from being selected.
  • CExtTabFlatWnd :
    This control doesnt work on CFormView, we can see, we can not select any Tab, neither there is way to receive any events.
    This control’s First Tab becomes invisible when we click 2nd Tab only first time in CView, from next time onwards it works.


    We cannot confirm this. Please send us your test project.
  • CExHookSink:
    Class is missing in documentation

    This class is for internal use only. But it is not to difficult to understand how it works. Sometimes you need to watch and/or handle the messages from several windows in some class even before these windows recieve them. You may derive your class from CExtHookSink and override the OnHookWndMsg virtual method that should return true if you process the message manually. The SetupWndHookSink methods initializes/removes the hook to/from the specified window.
  • Suggestion:
    New Class CExPagedView which can be used in MFC with document/view architecture. CExPagedView must be able to create and hold, switch multiple Views derived from CView. Also it must have OnPageSelected function which can be overridden to get notification of current selected View.

    We added this into our TO-DO list.
  • Too Big Examples:
    To understand CExtTabPageContainerWnd, I had to read Page example almost 10 times to find out where control is created. Ideal example would be One Control with 2 child controls, here you have created N number of controls which takes so long to analyze.

    Maybe you are right. Untill this we tried to keep only valuable samples.
  • Is it good trick to earn money?
    Is it your policy to force users to come back to you for support? not provide proper and complete documentation? If that is the case, I would have searched number of code websites, get one one code from there and integrated it if I had to spend time to go through each and every forums etc. I thought I will get nicely MSDN sort of documentation which would contain everything!!!


    The documentation is something special that allways requires too much time, much more than we really have.