12-07-2012 03:54 AM - edited 12-07-2012 03:59 AM
Hello everybody,
By right clicking on a numeric control I cannot change the minimum and maximum range. (it is always returning to 0 after typing 25 for example at the maximum value, the numeric is UINT16).
This is happening on every vi in my project, even if I create a new empty one.
BUT, it is not happening when I close labview, re open labview and open an empty vi (not in the project). This way, I can change the maximim property of a numeric, as usual.
Is there a project property that forbid to change numeric property, in all vi in the project ?
I am missing something ?
Thanks for your help.
ps : I use labview 8.6.
Solved! Go to Solution.
12-07-2012 08:44 AM
This was a "feature" of LabVIEW 8.6.0 and should have been fixed with 8.6.1 as far as I remember.
Christian
12-07-2012 10:45 AM
Actually, I am using labview 8.6.1....
What is the trick to avoid this ? The only way is to progamatically set the min and max ????
Thanks for your help
12-10-2012 03:57 AM
So if you try to change the range of an allready existing numeric control in a VI of a certain project, it does not work?
If you create a new numeric within this VI and then change the range, does this work?
Christian
12-11-2012 09:31 AM
I made additionnal tests.
If I put a new numeric1 DBL on the FP on a vi in my project, I can change the max property to 5.1 for example.
If I put a new numeric2 DBL on the FP, and I change the max property to 6.1, the max property 6.1 is automatically set also on numeric1.
If I put a new numeric3 UINT on the FP, the default value to max property is also 6.1, that is strange for a UINT.
It seems that what is happening is dependant of what is the first numeric I put in the FP.
The beahaviour I was previously describing what because I first put a command in the FP that was a typedef of a cluster containing different numerics.
I really don't understand what is happening, because I rthink it is not the first time I use min max property, and I never had such a problem as far as I remember.
Thanks for your help.
12-11-2012 12:32 PM - edited 12-11-2012 12:34 PM
12-13-2012 05:56 AM
This patch perfectly solves the problem.
Thanks.