As Nicholas says, restrictive in what way?
Without the tabs of the TabControl, you'll have to provide your own UI
for switching "tabs". But it's not difficult.
I just answered a very similar question:
http://groups.google.com/group/microsoft.public.dotnet.languages.csha...
I
can't guarantee that there's nothing better around than using the .NET
forms API, but it is very flexible. If you're having trouble, it's
more likely that you just haven't learned it well enough than that
there's some fundamental problem.
Yes, when you want to deviate from the standard behavior, you have to
write some extra code. But in my experience it doesn't usually take
much extra code, and that's completely expected in any sort of
framework anyway. Customization is always going to require at least
_some_ extra code; it's not practical for a framework to implement
every possible variation on its behavior.
In your own case, switching between your "tabs" will be as simple as
using the Control.Show() and Control.Hide() methods. How the user will
control depends on your own desire, but even if you want it to be
managed by keyboard shortcuts, that's not difficult. You'll just want
to add an appropriate key handler override to your form (which method
to override will depend on which keys you want to use for controlling
the tabs).
Pete
