
Horrendous SStab problems
Quote:
>I have had nothing but MEGA PAINS with the SSTab
>(tabctl32.ocx). It is version 4.1 something (latest). This appears
>to be one of the most poorly written pieces of software I have
>ever seen. It is so very bug ridden I want to pull my hair out.
I'm just starting a project using SSTab so I did some tests with 10
Tabs, 5 Tabs per page, and I didn't see these problems. I have V4.01
162,064 23 May '96. I'll include Michael Chernenko's comments.
Quote:
>1. When you disable a tab by clicking on a option button outside
>the tab, labels disappear on the tab you are looking at, as well
>as anything inside a standard VB frame (on the tab). If you refresh the tab
>by choosing another one, then going back to the one you were on,
>it will appear correct.
>2. When you are viewing a tab, and you disable it from an option
>button off the tab control, it still lets you view it but it's title tab
>is greyed and you lose about 50% of the controls on that tab,
>they just hide themselves.
>Michael Chernenko says:
>2. Controls on a tab in the foreground with TabEnabled set to False are
>accessible!!!!
I don't get any disappearing labels or frame content, but does this
really matter? Why would one want to view a disabled Tab? One would
would not expect a previously disabled Tab to be selectable (viewable),
and it seems reasonable that action to disable the foreground Tab would
also include action to switch to another tab. Videosoft's Tab Control
behaves in a similar manner with controls on a disabled foreground tab
being accessible.
Quote:
>4. There appears to be no way to bring a certain tab to the front.
An offtab option (actually a menu command) SSTab1.Tab = n always
brought tab n to the front
Quote:
>Michael Chernenko says:
>1. If you attempt at disabling all the tabs with setting their
>TabEnabled(n)=False, the last one will remain enabled, and you end up in
>disabling the whole Tab with the above described effects.
Disabled all 10 and and they *all* disabled.
Quote:
>Michael Chernenko says:
>3. The Click event for the control "extended" with the PreviousTab parameter is
>an example of the most "useful" option: the Tab first switches to the tab
>clicked, and triggers the event afterwards. If you attempt at resetting the Tab
>to the PreviousTab value, the screen blinks like crazy, because actually two
>clicks are triggered: to the new tab and back to the old one. Fantastic design!
Only two? Assuming in the Click event you have SSTab1.Tab = PreviousTab
then this generates the click event, and as there is only one Click
event for all tabs one would expect it to go crazy. It's a cascading
event.
Quote:
>4. With multitab Tabs, resetting the TabEnabled also results in nervous shaking
>of the control - looks just ugly!
Again, didn't see this.
If anything, SSTab (so far) behaves better than Videosoft's Tab Control
using elastic containers. I gave up on that after failing to work out
why a form resize gave twelve "consecutive" paints of a Picture Box on a
tab. No doubt there is a big SSTab pit somewhere there to fall into.
--------------------------------------------
Richard Mason, Stevenage, UK
--------------------------------------------