LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Text Cursor appears NOT where I click

LabVIEW 8.6.1f1

 

This problem MIGHT have started when I applied the "f1" update - I'm not sure.

 

I place a TAB control on a blank VI.

 

I click inside it with the TEXT tool.

 

The text box opens not where I click, but some distance above it.

 

Today the distance is about an inch, some days it's different.

 

It will even grow the tab control if I click within an inch of the top.

 

The cursor otherwise works fine - If there's an object in the TAB control, i can click on it and operate normally.

 

I can click OUTSIDE the tab control and it's OK.

 

 

Hmmm - the error distance is related to where on the screen the TAB control is.

 

If the TAB control is at the y=0 mark on the panel, the error distance is about 150 pixels.

 

If the TAB control is at the y=150 point, the error is 20 pixels

 

If the TAB control is WAY down on the page, the error is actually in the other direction, and the text box opens BELOW where I click.

 

It's like playing Whack-a-mole.

 

Any ideas? 

 

 

Here's a pic:  I clicked where the cursor is shown, and you can see the text box. 

 

Message Edited by CoastalMaineBird on 06-18-2009 07:53 AM
Message Edited by CoastalMaineBird on 06-18-2009 07:55 AM
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 1 of 5
(1,530 Views)

Here's the pic:

 



Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 2 of 5
(1,520 Views)

OK, the error does NOT depend on where the TAB control is on the page, it depends on where the page is scrolled to.

 

IOW, if I scroll the whole page up or down, the error distance changes. 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 3 of 5
(1,518 Views)

I reported this issue as soon as I saw it. I think the CAR# was "124962".

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 5
(1,513 Views)
Ben is correct.  This issue has been reported to R&D (#124962) for further investigation.
Regards,

Jon S.
National Instruments
LabVIEW NXG Product Owner
Message 5 of 5
(1,463 Views)