Fine, 'textchanged' solves your problem.
But the bug revealed by this thread still remains.
So just to 'round up' (also with regards to HTML5) this discussion
with a working method for getting keyCodes and characterCodes.
One could also use javascript for that, see here, also for a good
explanat
: AW: Is there a mapping table for all rawKeyUp Codes? No solution
yet with LC 8
Tiemo wrote:
> Can I rely on this workaround to get the correct chars, which have
> been entered on "all" systems?
TMHO:
No. As a workaround to get the "char input" this isn't reliab
Tiemo wrote:
> Can I rely on this workaround to get the correct chars, which
> have been entered on "all" systems?
TMHO:
No. As a workaround to get the "char input" this isn't reliable on
_any_ system or hardware configuration. You only *guess* with that:
IF the user uses a 'usual' keyboard layout
Tiemo wrote:
> You say Apple changed the keyboard mapping.
NO, I said, Apple changed his keyboard mapping _method_.
That's why developers had to change the lookup method for the mapping.
Anyway, 'the keysdown' and 'rawkeydown/up' should return the _hardware_ code
[keydown/up may return, basically
B
Gesendet: Dienstag, 6. Dezember 2016 08:45
An: 'How to use LiveCode'
Betreff: AW: Is there a mapping table for all rawKeyUp Codes? No solution
yet with LC 8
Thanks Hermann and Paul for clarifying this to me. I didn't noticed the
difference to *the keysdown*
You say Apple changed the
gliche Nachricht-
Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag
von hh
Gesendet: Montag, 5. Dezember 2016 23:27
An: use-livecode@lists.runrev.com
Betreff: Re: Is there a mapping table for all rawKeyUp Codes? No solution
yet with LC 8
Hi all. Yes that's the poi
Hi all. Yes that's the point:
*The keysDown* return the correct (hardware) keyCode.
Tiemo is right, there is a bug introduced around LC 8. From the dictionary:
"The keycodes returned by the keysDown function are the same as those
passed as parameters with the rawKeyDown and rawKeyUp messages."
T
derstood, what you meant to workaround this issue.
>
> Tiemo
>
>
> -Ursprüngliche Nachricht-
> Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag
> von hh
> Gesendet: Montag, 5. Dezember 2016 14:55
> An: use-livecode@lists.runrev.com
> Betreff: Re:
zember 2016 19:28
An: How to use LiveCode
Betreff: Re: AW: Is there a mapping table for all rawKeyUp Codes? No solution
yet with LC 8
Why are you stuck with LiveCode 8?
1. My Indy licence lets me go on downloading commercial versions until it
expires (sometime in 2018).
2. If this is not possibl
Um . . .
On 12/5/16 1:58 pm, Tiemo Hollmann TB wrote:
Since the keyup handler is broken,
I am not entirely sure what you mean by this . . . I am currently
running LiveCode 8.1.1 on
Mac OS 10.7.5 and have a boring little stack with 2 fields, "ff" & "gg",
and this in the cardScript:
onrawKey
Why are you stuck with LiveCode 8?
1. My Indy licence lets me go on downloading commercial versions until
it expires (sometime in 2018).
2. If this is not possible, you can, at least, download the Community
version of later builds and
fiddle around to see what happens there.
Richmond.
On 1
14:55
An: use-livecode@lists.runrev.com
Betreff: Re: AW: Is there a mapping table for all rawKeyUp Codes? No solution
yet with LC 8
The '58-example' is obviously a script error:
the message box has always display bugs, you may better use a field for the
display.
If I understand right,
The '58-example' is obviously a script error:
the message box has always display bugs, you may better use a field
for the display.
If I understand right, then you want now
the keyCode (an event, depending on _hardware_)
and NOT
the characterCode (a number representation of the char).
Some Mac apps
Since the keyup handler is broken, I am still trying to build a table for
mapping the rawkeyup key to a char. When testing a prototype it seemed to be
easy, but now there are some pitfalls I don't get over. On Mac OS X 10.11,
German system, German keyboard I get with some different char the same
14 matches
Mail list logo
