The Sinclair QL Forum

improved the code a bit, but some blinking flash glitches appeared (i have no idea why)

...

***************************************************************************************
* keyScan
* Check keyboard row 1 (cursor keys, ESC, Enter and Space)
* return result in d1.b
* trashes d5 and d7 ...

and at http://www.dilwyn.me.uk/docs/manuals/qltm.pdf i'm seeing "18.13 Hardware Keys", "PC_IPCRD $18020 IPC read is the same", "PC_IPCWR $18003 IPC write" - does it mean that we can access ipc "directly" by poke/peek (i/o), and specially reading the keyrows, without using traps?

faster version, using pokelong and peeklong&() (poke_l and peek_l() ) instead of poke and peek

when trying to know better about a hardware, i normally use mame/mess sources as reference - https://raw.githubusercontent.com/mamedev/mame/master/src/mame/drivers/ql.cpp (some info about the keyboard seems used as ipc_port1_w there), but i have no idea which i/o port are, how to access them, and ...

how can we get keyrow values from assembly? it seems to be by only "peeking" i/o addresses, isn't it?
(btw, is there any i/o ports/memory arrangement documentation around that you could reccommend? unexpanded QL only, please...)

recoded it on SecondBasic
i only needed to replace with so Vasm would recognize it

might look like this

its a bit slow - i'm going to try something faster from secondbasic soon - perhaps i might try to code a simple game based on it later
(i have no idea how fine would it run on expanded ql)

it works! (at least on unexpanded ql... )