|
-
Aug 16th, 2000, 10:25 PM
#1
I don't know... maybe I'm getting senile in my old age (20 in less than a month!!) But here's my problem:
1) Add a TabStrip to a form
2) Set the placement to bottom and the style to Buttons
3) Add a command button with a MsgBox TabStrip1.ClientHeight
When the buttons are anywhere besides the top, the ClientHeight is always 120!!!
Whats up with that?
-
Aug 17th, 2000, 05:00 AM
#2
Frenzied Member
Stop using the TabStrip - it's crap!
Use the Microsoft Tabbed Dialog control (on the Components List) instead - it was once written by Sheridan Software ( I think ), it's been around since VB4 and it's far far superior to MS's effort.
'Buzby'
Visual Basic Developer
"I'm moving to Theory. Everything works there."
-
Aug 17th, 2000, 05:48 AM
#3
Hyperactive Member
I had a problem with this too, and now I realize it couldn't be more simpler!
ThanX Buzby.
-
Aug 17th, 2000, 12:34 PM
#4
I've already tried the SSTab control from Microsoft and it doesn't have some key features that only TabStrip has (HotTracking and Button Style are 2 of them).
So.. The question remains.... Has anyone else seen the ClientHeight bug when the TabStrip is set to the bottom while using the "button" style??
-
Aug 17th, 2000, 03:12 PM
#5
Monday Morning Lunatic
Yes - it does it on mine. What it's probably trying to do is get the height below the buttons, but there is only the bottom of the control's window. Either way, it's a bit nasty...
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Aug 19th, 2000, 03:19 AM
#6
AAAAHHH
Damnit. Microsoft sucks. Any ideas on a workaround for this pathetic bug??
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|