string to number shall take care for representation

[Andi_S]

I don't know if this is a bug or a feature ... but please see the pictures to understand what I mean:

Because I use the representation U8 I would expect a value of 0x3F and an offset of 2.

It seems that LV first converts the string to a number and then it converts it to the given representation. I think the reverse processing order would be much better.

Maybe there could be an option added (boolean input or context menue).

[AristosQueue (NI)]

The existing behavior is deliberate and will not be changed. If you need more discrete parsing, separate the string into separate units and then call the primitive.

The reason for the existing behavior is that some numeric types do not have a clearly distinguishable boundary for length (i.e. floating point) and others have characters (negative sign) that would make it ambiguous about whether they can be parsed or not. So the parsing behavior is fixed for "numeric" and then the representation is taken into account after.

[crossrulz]

You could use Scan From String with %02x as the format string.  Then it would only parse the first two characters into your U8.

[X.]

According to the Help:

"If the input string represents a number outside the range of the representation of number, number is set to the maximum value for that data type".

Number is the output (Value in your snapshot).

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.