Getting Int from CMD not working

[srm]

Tried:
Write ' {CMD}' to log
Set integer [myValue] value to the converted value of {TXTNUM:"{CMD}"}
Write ' {INT:myValue}' to log

Use nested tokens checked.
Version 1.6.1 in use.

The first blue string prints out the correct results (test 1)
Then the set integer generates an error: Integer token could not be converted : {TXTNUM:"{CMD}"}
Which results in the second blue string saying "Not set"

[Pfeil]

Don't have a v1.6.1 install to test with, but this works fine in beta v1.6.1.4.

[srm]

Tried with 1.6.1.4 beta...still doesn't work.

In the instruction "set an integer value", should the value: {TXTNUM:”{CMD}”}
be placed in the slot "another variable" or in "convert text/token"?

[Pfeil]

"Convert Text/Token".

However, note that

Code: [Select]

”and

Code: [Select]

"Are completely different characters, only the latter will work.

[srm]

Copied your symbol and it works.
So, which is which?
I only have one set of double quotes on my keyboard.

[Pfeil]

{TXTNUM:"{CMD}"}

Is correct(ASCII 34).

{TXTNUM:”{CMD}”}

Is not(ASCII 148).

[srm]

Ahhhh!
Just retyped it for the zillionth time.
Works.
Don't know where the error crept in, but I'm glad you were able to correct my mistake.
Thank you!

[Gary]

I'm thinking what happened is when you copied it from whatever I emailed, the quotes were copied in incorrectly (web-based browsers will do that a lot).

Good catch, Pfeil!