Match String function error

[grmc]

The match string function does not work when trying to match the Hexadecimal string C8 2B.

It will only return C8 as a match.

Download File:post-854-1102390914.vi

[Mark Balla]

The match string function does not work when trying to match the Hexadecimal string C8 2B.

It will only return C8 as a match.

2959[/snapback]

If you convert the search string from hex display to \code display you will see that 2B is a + sign.

If you look up the help on the match pattern and click on the special characters link you will see that a + is a special character. It also say that in order to search for a + it must be proceeded by a \ (5C hex)

[grmc]

If you convert the search string from hex display to \code display you will see that 2B is a + sign.

If you look up the help on the match pattern and click on the special characters link you will see that a + is a special character. It also say that in order to search for a + it must be proceeded by a \ (5C hex)

2960[/snapback]

Yes I am aware of that, but the fact remains that the Match String function does not differentiate between a hexadecimal input and a string input. One would expect that when looking for a hexidecimal string, the string would be matched exactly as it appears.

[Mark Balla]

Yes I am aware of that, but the fact remains that the Match String function does not differentiate between a hexadecimal input and a string input. One would expect that when looking for a hexidecimal string, the string would be matched exactly as it appears.

3002[/snapback]

Ok, We want to use the power of the search string primitive which is designed for normal strings but send it hex display values.

How about a hex to normal and a normal to hex converter.

If anyone has a more elegant way of converting strings I would be interested in seeing it.

Download File:post-584-1103005348.llb

[jpdrolet]

Yes I am aware of that, but the fact remains that the Match String function does not differentiate between a hexadecimal input and a string input. One would expect that when looking for a hexidecimal string, the string would be matched exactly as it appears.

3002[/snapback]

The wires on the diagram don't have any formatting information from the control which data comes from. That's perfectly alright because the actual content of a control is not affected by how data is displays. I wouldn't like if a number was modified by the number of digits of precision it is displayed on the control... The same applies to string display. There is no so called difference between hexadecimal and string input. That's the same data with different display format for the user's eye only.

However, if you want to use the string as it is displayed, you can use the Text.Text property:

This property is the string content as it is displayed in the control. This is the exact formatted content, including the space separator every 4 character.