10-19-2012 08:50 AM
hi i've the following problem. if u can find out please try the same
the cursor selection is unpredictable!!
Renn
LV 12.0f1 (64 bit)
10-19-2012 10:07 AM
Hi Renn
Thanks for your post, I've tried the same and can't get the issue you described, it may be because I'm using 32 bit LabVIEW. I'll try test this on a 64 bit machine and let you know if I get the issue. Also when did this issue start, and has it worked fine before? It may something else interfering.
Thanks
Dan
10-19-2012 10:12 AM - edited 10-19-2012 10:12 AM
Thanks Dan
installed f3 Patch and its working!
but, i wonder this is not mentioned here: http://digital.ni.com/public.nsf/allkb/2F8112CC78A524FC86257A93006EA241
RENN
10-19-2012 10:25 AM - edited 10-19-2012 10:25 AM
Hi Renn
Great to hear your issue has been solved. As for why it's not listed it may be because it's quite an obscure issue not listed as a major update. Alternativly solving one of the other issues listed in the patch may have had a knock of effect and fixed the issue you were having.
Thanks
Dan
10-19-2012 11:53 AM
good.
thanks Dan
10-22-2012 07:37 AM - edited 10-22-2012 07:38 AM
Hi Dan,
i have selected Cursor 0
then i clicked near 7, then using the navigation button (on the right side), i've increased the Y value. Cursor 0 is selected but, the Y value of Cursor 2 is incremented.
Many Customers are having problem with this. Please help.
Thanks
RENN
10-22-2012 09:17 AM
Can Anyone help me with this?
10-22-2012 11:33 AM
Hi Renn
Sorry for my late reply. I’ve downloaded your code and seen the issue you’re having. I'll confer with some colleagues about this but it sounds like a corrective action request that will need to be passed to R&D. I’ll update you as I find out more.
Thanks
Dan
10-22-2012 12:35 PM
Thanks Dan.
i wonder, this exists in most LV versions. checked LV8.0, 2010 and 2012
10-24-2012 08:20 AM
Hi Renn
I’ve been able to get the same issue you’re having from my own code and not just by copying yours. This means it’s a bug in LabVIEW and will be passed higher up. Sadly this might not be a quick fix but I will post a link up here to let you know the status of this bug once it gets filed.
Thanks
Dan