OS Turn off keyboard input?

[mcgeezer]

Hi all,

In my game I bring the system back up so that I can load files using the OS, however if during that time someone happens to hit the keyboard - then loading stops until return is pressed.

Is it possible to stop keyboard input? Can someone give me some pointers as I'm not that hot with the OS side of things.

thanks,
Graeme

[a/b]

Install a handler for input.device with high enough priority (above intuition I guess, which is at 50) that will consume rawkey events (set class to NULL)?

[ross]

This can help:
http://eab.abime.net/showpost.php?p=...3&postcount=26

[Thomas Richter]

Frankly, this looks more to me as if you should check why it stops loading rather than looking for a workaround. There is nothing keyboard specific in the IO subsystem.

[meynaf]

If some text gets printed to the console, pressing a key will stop everything.

[Thomas Richter]

Actually, it will not "stop everything", it will halt the printing process until the console becomes available, but then the solution should rather be "do not print anything on the console" rather than "try questionable workaround".

[meynaf]

Of course it won't stop the whole system, it's not what i meant !
But anyway, if keypresses are transmitted to a background console, then the program has better not let them get there. Commands may be run inadvertently, and even if not, it's not very clean to have a cli with garbage in.

[paraj]

Originally Posted by ross

This can help:
http://eab.abime.net/showpost.php?p=...3&postcount=26

I'll give my recommendations though I've mostly tested it with KS3 . (Also seems to works fine with naughty stuff like peeking at ciaa->ciasdr to check for a key press, but don't rely on it)

[a/b]

This looks like it's only needed in debug/development version, e.g. you are printing out filenames of stuff you're loading.
And there is also:
if (intuibase->ib_ActiveWindow != my_window) do nothing
to make it less drastic, if it's applicable (that's what my input handlers typically do, but they are all part of 100% os friendly apps so...).

[paraj]

Originally Posted by a/b

This looks like it's only needed in debug/development version, e.g. you are printing out filenames of stuff you're loading.
And there is also:
if (intuibase->ib_ActiveWindow != my_window) do nothing
to make it less drastic, if it's applicable (that's what my input handlers typically do, but they are all part of 100% os friendly apps so...).

So you either kill the system or stay fully friendly? (not bait, just curious what you mean)

[mcgeezer]

Originally Posted by ross

This can help:
http://eab.abime.net/showpost.php?p=...3&postcount=26

As usual, this has worked perfectly well for my needs.

[a/b]

Originally Posted by paraj

So you either kill the system or stay fully friendly? (not bait, just curious what you mean)

Yeah, I don't like mixing it unless it's something relatively simple. Why? To keep it short, A500 + extreme min-maxing + I code because I can/want, not because I need = how it is :P.

[patrik]

If the screen is opened through the system and made active, the input events should not fall through to the shell where it was launched.