can't insert text in a tabbed page

[oyester]

I have a tab-object within a tab-object on my front panel as shown below 

The problem is, when I click on a page of the inner tabbed object with the text insertion tool, I do not get the text-insertion  I-beam. By trial and error, I found that I can put a decoration on the tabbed page, insert text onto the decoration, then drag the text onto the tab object page. This is LabVIEW 8.6 by the way. Does anyone have any ideas what is going on?

[smercurio_fc]

What do you mean by clicking on the tab page with the text insertion tool? Is the VI running? Are any controls grouped? Can you upload your VI to see if someone else can replicate your problem? Presumably the only thing that's really needed to do this is the front panel, so you can probably delete all of the code, leaving only the terminals.

[Darin.K]

In LV8.6 I could insert text (ie. free label) in a nested tab.  What is interesting is that the insertion point is consistently about 50 pixels above the point where I clicked.  This was true for all tabs, not just nested ones.  With autogrow enabled, the top would grow when I clicked. 

In LV9 everything is fine.

[oyester]

I'm glad to see that something like my problem could be reproduced. Attached is the front panel of my program (the back panel is just a bunch of indicators). On the bias tab is another tab control object and I can't even see the I-beam when I use the text tool. 

[StephanieA]

Oyester,

I've taken a look at your front panel and I do not know what is causing that behavior you are seeing. When I opened your front panel, I was able to see the I-beam but was not able to insert text without using the work around you described.

I opened your front panel in LabVIEW 2009 and this behavior did not occur and I was able to insert text without any problems. If you do not have access to LV 2009, I would recommend using the work around you have found as it seems this behavior has been corrected in LabVIEW 2009.

Thank you for the feedback. I will ensure that it is documented on our end so we have a record of this behavior. 

[oyester]

Thanks. If I can't solve my problem, then the next  best thing is knowing that it isn't my fault. We do have LV2009 but we can't upgrade until we have at least two months slack time to fix whatever upgrade issues occur. It may be a while.