Greetings,
How do you add tabs to a frame? I realize this should somehow be obvious; but after fifteen minutes of wasting time, I need some direction.
Thank you,
Jim
Printable View
Greetings,
How do you add tabs to a frame? I realize this should somehow be obvious; but after fifteen minutes of wasting time, I need some direction.
Thank you,
Jim
..add frames to a tabControl!
You don't. You use the Microsoft Tabbed Dialog control.
OK, how do I get the Tabbed Dialog Control to be available?Quote:
Originally posted by MartinLiss
You don't. You use the Microsoft Tabbed Dialog control.
In the VB IDE menu select
Project|Components
and select it from the list.
Are you trying to make me feel stupid???????????!!!!!!!!Quote:
Originally posted by MartinLiss
In the VB IDE menu select
Project|Components
and select it from the list.
Well it worked.
Thanks,
Jim
In development, how can I specifically put in objects for one tab and then put in objects for the other tab. I put a frame with some items on the first tab. Now I want to put some items specifically for the other tab. Nothing is happening when i click on the 2nd tab, in development. How do I need to approach this? I've been searching the tabstrip prperties for clues. Hmmm?
At design time draw the controls on tab1, then click tab2 and draw the controls on tab2. They don't need to be done in that order, but they do have to be drawn on the tab (or copy/pasted).
I agree; but that's the problem. In design, when I click on tab2, it just stays on tab1.Quote:
Originally posted by MartinLiss
At design time draw the controls on tab1, then click tab2 and draw the controls on tab2. They don't need to be done in that order, but they do have to be drawn on the tab (or copy/pasted).
Are you sure that the object you got is
Microsoft Tabbed Dialog Control (TABCTL32.OCX)???
You want to use the MS Tabbed dialog control - not the tab strip found in the MS Common Controls.
Here is a form with the tabbed dialog control
So I should use the SheridanSopftware tab? That's the kind you sent, as indicated in the About in properties for the tab?
No don't use the Sheridan control. There is one called the Microsoft Tabbed Dialog Control. Just add it to your form and you should be able to click the tabs at design time and draw items on different tabs.
At least on my PC the Microsoft Tabbed Dialog control is a Seridan control. It's name is tabctl32.ocx.
Just a portion of it was developed by Sheridan Soft for Microsoft.Quote:
Originally posted by JimMuglia
So I should use the SheridanSopftware tab? That's the kind you sent, as indicated in the About in properties for the tab?
I didn't know it was a Sheridan Control. I don't use it, I tend to just use the tabstrip that comes with the windows common controls. It's a little more code, but I just got used to using it.
So would our clients have to have it installed as a 3rd party component?Quote:
Originally posted by andreys
Just a portion of it was developed by Sheridan Soft for Microsoft.
Jim, after choosing the MS Tabbed Dialog from Components, just select the SSTab from the toolbox.
When you build your distribution files the installer will include whatever your clients need.
So is that true with most components ingeneral. Say I use Company X's widget control. Would my clients have to get a license or any ocx files from Company X? Or does the install take care of each and every of those isues?Quote:
Originally posted by MartinLiss
Jim, after choosing the MS Tabbed Dialog from Components, just select the SSTab from the toolbox.
When you build your distribution files the installer will include whatever your clients need.
When you purchase a control (or someone gives you a control that they wrote - in other words it's a legal copy) you have the right to distribute it in an application unless for some strange reason the maker specifically prohibits it.
Thank you for that clarification.Quote:
Originally posted by MartinLiss
When you purchase a control (or someone gives you a control that they wrote - in other words it's a legal copy) you have the right to distribute it in an application unless for some strange reason the maker specifically prohibits it.