03-11-2008 11:03 PM - edited 03-11-2008 11:05 PM
03-11-2008 11:49 PM - edited 03-11-2008 11:49 PM
03-12-2008 02:18 AM
One more way to do it.
Look at attached Post
03-12-2008 02:27 AM
03-12-2008 04:46 AM
Hi Dev,
Is the Text.Document Bounds:Height property a private one in LV 8.5?
03-12-2008 08:32 AM
That's a good point. I've come across that problem in professionally built applications completely unrelated to LabVIEW. The user could wrap the scroll position with a case structure that is tied to an Unlock Boolean button. If they press the button, the case doesn't execute and they'd be free to scroll. When done, they press the button again to relock it and the scroll position code can execute again.
altenbach wrote:
One problem with the "scroll position" solutions is the fact that the user will have a hard time scrolling, e.g. if there is a need to look at older entries because the propertry node is constantly fighting with the user interaction. This can be very annoying!
03-13-2008 01:12 AM
03-13-2008 01:26 AM
03-13-2008 01:28 AM
Dev,
Sorry to say that many of your propertiers are not present in my LV 8.5, though it is an evaluation version. I ve checked in PDS also.
See the attached pic.
Are you using some NI's internal version of LV or is it 8.51 or 8.6 beta?
Moreover, your pic shows that you ve got Property of Property nodes & Locals also for a string control.
Maybe, you ve to explain me more of those secrets.
03-13-2008 01:38 AM - edited 03-13-2008 01:39 AM