Key hook issue

[pruss]

Question: Am I the only one annoyed by the fact that most utilities (including my own: e.g., myKbd) that hook into the hard keys behave differently from the OS's hard key assignments? The OS's hard key assignments are overrideable by applications that use the hard keys for their own purposes. But most, maybe all, utilities that hook into the hard keys do not allow applications to override the utility's hard key settings, which is bad.

(Note to developers: One way to make overrideable key hooks is to patch SysHandleEvent().)

[dmitrygr]

(Note to developers: One way to make overrideable key hooks is to patch SysHandleEvent().)

That method also gets the worst idea ever award.
Too many Patches in the OS and 3-rd party apps already do this.

This call and SysAppStart both get patched so much, that they require monstrous stack sizes to run, causing random failures when stack space is low.

[pruss]

That method also gets the worst idea ever award.
Too many Patches in the OS and 3-rd party apps already do this.

This call and SysAppStart both get patched so much, that they require monstrous stack sizes to run, causing random failures when stack space is low.

Is there another way of hooking into hard keys in a way that apps can override?

[pruss]

To fix the stack size issue, Igor Nestorov suggests using RALCallWithNewStack().

[dmitrygr]

an even worse idea :)

[pruss]

an even worse idea :)

Why is that?

[Supertrucker]

@Pruss:

So are you suggesting, and in my application it's doable, to include a sort of application "exclusion" list, as a viable override? Or would you suggest some sort of da or something to disable for a particular application? After reading this thread I started thinking about DBLP and began wondering if I should allow users the ability to disable via an exclusions list...