Differ 1..0 from Num1..Num0 in ShortcutToText?
lazarus / 31-LCL

----------------------------------------------------------------------
AlexTP · 2015-03-29 11:21

Afaik, some Delphi differs this, ie, it has result of ShortcutToText
as "Num1".."Num0" for num-keys.
Why, because it gives more variants of assigning user keys: app can
store to ini more keys after ShortcutToText.
Why not, maybe some app reacts to keys via
if ShortcutToText(str)='1'
, for this app better to have 1..0 for numkeys.

Variant of Num1..Num0 better? (I can make patch)

----------------------------------------------------------------------
typo · 2015-03-29 11:34

I think you should keep Delphi compatibility.

----------------------------------------------------------------------
taazz · 2015-03-29 12:05

Quote from: Alextp on March 29, 2015, 01:21:52 pmAfaik, some Delphi
differs this, ie, it has result of ShortcutToText as "Num1".."Num0"
for num-keys.
Why, because it gives more variants of assigning user keys: app can
store to ini more keys after ShortcutToText.
Why not, maybe some app reacts to keys via
if ShortcutToText(str)='1'
, for this app better to have 1..0 for numkeys.

Variant of Num1..Num0 better? (I can make patch)
num1 is in the numeric keypad while 1 is on the top of your keyboard
just below your Fx keys so yes make sure that both can be used not
only one of them or worst both the same time.

----------------------------------------------------------------------
eny · 2015-03-29 12:40

Quote from: Alextp on March 29, 2015, 01:21:52 pmVariant of Num1..Num0
better? (I can make patch)
Don't bother making a patch.
The purpose of Lazarus is to be (-come) a 100% Delphi clone.
Heaven forbid if you suggest an improvement.

----------------------------------------------------------------------
AlexTP · 2015-03-29 12:42

Patch needed for delphi-variant (yet result is always "1..0")