English Amiga Board - View Single Post

a/b · 24 January 2022, 18:08

Yeah, I understand that. They get removed when the app is running (it's using cx for event handling, I typically use either IDCMP or input.device so can't tell more about this first hand, and how to avoid it.. exe is ~1MB), but this could be generalized for an arbitrary app?
I did a test earlier with a prio=100 handler that sets subclass of those events to 0 and it doesn't work: events are perpetually generated (as you pointed out) and mouse becomes unusable.
However, wouldn't it be sufficient to use class+subclass+code+x+y combo (rawmouse, 0, nobutton, +/-4095, 0, all legit values) to correctly identify them with 99.9% repeating, and avoid a "problematic" private subclass that cx handler apparently doesn't like (it only allows documented subclasses: $00-$03 for class=NEWPOINTERPOS)?
Either way, I don't have a horse in this race, just an opinion about choosing between 2 evils.

24 January 2022, 18:08	#348
a/b Registered User Join Date: Jun 2016 Location: europe Posts: 1,043	Yeah, I understand that. They get removed when the app is running (it's using cx for event handling, I typically use either IDCMP or input.device so can't tell more about this first hand, and how to avoid it.. exe is ~1MB), but this could be generalized for an arbitrary app? I did a test earlier with a prio=100 handler that sets subclass of those events to 0 and it doesn't work: events are perpetually generated (as you pointed out) and mouse becomes unusable. However, wouldn't it be sufficient to use class+subclass+code+x+y combo (rawmouse, 0, nobutton, +/-4095, 0, all legit values) to correctly identify them with 99.9% repeating, and avoid a "problematic" private subclass that cx handler apparently doesn't like (it only allows documented subclasses: $00-$03 for class=NEWPOINTERPOS)? Either way, I don't have a horse in this race, just an opinion about choosing between 2 evils.