04-10-2013 01:35 PM
In the attached LabVIEW 2012 vi, I programatically set some tab pages tipstrips. If I hover my mouse over Page 1 or 2 or 3 the tip strip does not appear over the tab as I would expect (and as happens if I manually set a tip strip on a tab control). Instead, the tip strip appears up at the very top of the screen.
You can delete and create a new tab control and the situation stays the same. Additionally you can copy and paste the code into a new vi and the tipstrips still misbehave (though I noticed they started showing up on the left edge of the screen rather than the top).
Additional info: we tried this on LV 2012 and 2012 SP1 on 3 different machines. All machines were Win7-64 bit and (this may be relevant) they all had dual monitors.
This is casuing some frustration with our application, so, any suggestions for workarounds would be appreciated.
04-11-2013 06:44 PM
Using your VI, I was receiving the same strange results with tipstrips forced to the top of the screen. I tried reproducing this from scratch, but was unable to do so. I remade your code and was getting expected behavior. I have attached the VI that I made, which is nearly indentical to yours. I also copied and pasted your code into a new VI on my computer and that resolved the strange behavior.
My computer is a 32-bit Windows 7 with dual monitors as well. For some reason, the VI was corrupted and was exhibiting this strange behavior. Do you get this same strange behavior with my attached VI?
04-12-2013 07:58 AM
@Dan: Your example works fine on my machine. However, that doesn't resolve my issue. It seems that this "corruption" is probably the result of other front panel objects (I took my our main application front panel, coppied and pasted it in a blank vi, wrote the tab code, then chopped out every control until the tab control was left). On our main application front panel, I moved things around, then I added a new tab control (totally independent of the one that was there) and added fresh tipstrip code and it still exhibited the behavior.
I'm pretty sure this is a LabVIEW bug... In a private forum I wouldn't mind giving you/NI the front panel of our main application + tipstrip code so that you can see what I'm talking about and look into the bug.
04-15-2013 05:36 PM
Thomas,
I think our best bet will be for me to send you a private message with some instructions you can follow.