Like I wrote... a particular problem I have with original input.device, is that I cannot click on links in IBrowse using USB mouse, as if IBrowse doesn't get the "mouse-button release" event properly. I also recall problems with other programs (DOpus Magellan among them), but I don't recall exactly how the problems manifest themselves in the various programs. Because with input.device v50, these problems are not there.
Ok, I understand. Maybe. What I do not understand...
Why Chris did not do that is unclear to me.
So it looks like you don't really understand what input.device v50 "cludges" to make things work.
USB is a complex mess, with at least two protocols just for the mouse (bootmouse and hid) and ditto for keyboard, and lots of products in the market that break these protocols in various creative ways. Chris was very clear that using v50 input.device from MorphOS was only a half-way and quick solution for him, and that the entire input system for AmigaOS should have to be rewritten.
Thus, at this point, this looks like an implementation defect at DOpus
DOpus, IBrowse, various other MUI software and whatever else that misbehaves with original input.device and Poseidon - you are now the one speculating ... educated speculation, but speculation nevertheless.
For DOpus it is easy enough to look for PeekQualifier in the code... I am not convinced that it is used in parts of the code relevant to where I experience trouble...
https://github.com/mheyer32/dopus5allamigas/search?q=PeekQualifier&unscoped_q=PeekQualifierYou also wrote...
All I can say is that I took precautions to address the problem, and I did my best to provide a solution.
yet...
The input device of 3.1.4 is the same as that of 3.1, and the only new thing it added was NSD. It does not provide any better solution than 3.1, but as of 3.1, there was already a correct way of doing it, namely create synthetic keyboard events yourself for keyboard repeat.
This is confusing. Unless the precaution was to not change anything, and to define "the problem" as non-existent.
Anyways - the best advice - as of now - for anyone using Poseidon with USB keyboard and/or mouse - is to load input.device v50 using LoadModule.