LabVIEW
BUG Workaround: SI notation "m" refuses to display "mm", change annotation to "m "
Hi simple,
@simple_logic wrote:
While on the subject of Si notations, maybe the helpful dev can add a power property. This way we can have proper conversion from m² to mm² and m³ to mm³
The proper power notation is m^2 (cm^2, mm^2, m^3…) - as described in the LabVIEW help…
From the tag, you seem to be using LabVIEW NXG. Do you see the same problem in classic LabVIEW?
This is really not something that we can judge by just reading an ambiguous paragraph, so please attach some code that demonstrates the behavior.
I assume that you are talking about a numeric indicator. What are the format settings? Units? What exactly are you entering, what do you get and what do you expect.
(Controls understand entered SI prefixes, for example 1k -> 1000, 1m -> 0.001, etc.)
@RavensFan wrote:
Do you know if units have been implemented in NXG?
They were a late addition to LabVIEW. Not many people use them. A few people swear they are useful, many others have found issues with the math surrounding controls and constants with units in them and avoid them. I would not be surprised if NI does not port units over to NXG, or will only do it at a much later date.
They were actually an ealy addition to LabVIEW! They are around since at least LabVIEW 4.0 or so over 25 years ago. I agree with the rest. The Units in LabVIEW were an interesting idea and worked reasonably well when they came out but there always existed a few bugs in respect to them. For some reason they did only receive minor work after the initial release and many of those little pesky bugs never ever got squashed.
In my perception there were two problems with the way Units work in LabVIEW. One is a fundamental one as even the SI system isn't always completely consistent so pressing that into a software algorithme is a nasty feat to do, although not as nasty as trying to make calender functions work!
And it seemed to me like the code involving Units was written by someone who had a pet peevee with Units and at some point he or she left the LabVIEW team and there was nobody else who even dared to touch the code anymore, just as many other areas in LabVIEW where the code base hasn't been touched even with asbestos gloves out of fear to burn their hands on! 😀 PArt of that may be also different code style. I suppose the original LabVIEW code is in terms of modern style rules a tricky thing to understand and its actual implementation was often dictated by the hardware constraints of those days where a few kB of extra memory here and there meant the difference between running on average user hardware or limiting the execution to pure high end super beasts of computers.
I would be extremely surprised if they even tried to take the Unit implementation from LabVIEW CG into NXG considering the many little troubles it is riddled with.
@RavensFan wrote:
I would not be surprised if NI does not port units over to NXG, or will only do it at a much later date.
IIRC, it's on the 'never going to happen in NXG' list...
Units have their use cases.
I actually don't use the units, but I do use the quantifiers of the units. When getting\setting GUI values from a file\DB by references, specifying a (any) unit as u, m, K, M, G has the effect of scaling the value from the file in the GUI. So it's easy to display a value in meters as mm, or grams as Kg.
Using units for this is a hack. I'd like to see a offset\multiplier property for numerics instead, just like the graph scales.
Search LabVIEW like a graph! 