[Solved] Peculiar bug when editing a button

[petermad]

This only affects the 64bit version of TC - but all the way back to TC 8.0 (x64)

1. Open a button in the button bar, preferably one that has the "Parameters" field filled out.
2. Delete the current "Command" and type xc
3. The "Parameters" and the "Start path" gets deleted and inactivated - just like if a cm_ or em_ command is chosen via the button with the magnifying glass.
4. Type one more character - the "Parameters" and the "Start path" gets reactivated (but are still blank).
5. It also happens if I paste xc from the Clipboard - so it is not the keystrokes xc that does it - it is the string xc.

[Horst.Epp]

Confirmed

[Gral]

Confirmed - only x64 version, 32 bit not affected.
Also: "xa" "xb" "xc" "xd" "xe" "xf" works the same way and you can add more a,b,c,d,e,f - "Parameters" and "Start path" still not active - you must add letter behind f to reactivate

[gdpr deleted 6]

Confirmed.
And it is not just "xc" or similar triggering this effect.

As it looks like, TC 64-bit tries to parse the command string as an integer number.
Seems the wrong input validation code has been wired up/reused incorrectly...


Any hex number of up to 16 digits (= 64-bit value) with a "x" prefix and an optional +/- sign triggers the effect.

Decimal integer numbers with an optional +/- sign will trigger the effect, as long as the value fits into 64 bits (as a signed 64-bit integer type, value range [-9223372036854775808, +9223372036854775807]).

Binary numbers with a "%" prefix are joining the fun as well (assuming they fit into 64-bit, i guess).

And octals. What would be a party without the octals? Just use the "&" prefix for octals, and there you go. (Again, 64-bit limit seems to apply).

Is there any common numeral system i forgot?

[Hacker]

elgonzo,

Is there any common numeral system i forgot?

Roman.

Roman

[gdpr deleted 6]

Roman.

Roman

[petermad]

As it looks like, TC 64-bit tries to parse the command string as an integer number.

That makes sence, since you are allowed to enter the number of any cm_command ins stead of the command name, and that explains why the "Parameters" and "Start path" fields are disabled like when you enter and cm_command - actually as soon as you have entered cm_ or em_

The best would be if TC only considered decimal numbers between 100 and 8999 as internal commands.

[gdpr deleted 6]

Your explanation made me check the 32-bit version again. Unsurprisingly, it exhibits a similar and closer to the intended but unfortunately undocumented behavior (or the documentation for this is well hidden). The 32-bit version only successfully parses decimal signed 32-bit integers. Neither hex, binary nor octal numbers are parsed (at least not with the prefixes x/%/&).

[ghisler(Author)]

Interesting, I didn't know that the Lazarus val() command would recognize such strings as hexadecimal. Numeric values are indeed supported, and both the decimal and hexadecimal (with $ at the start) variations are allowed.

[petermad]

03.09.20 Fixed: Button bar: Hex strings in the form "xc" were detected as internal numeric commands by mistake (64)

Confirmed fixed in TC 10 b1a