Repressed Traumas

[richmond62]

Screenshot 2025-03-02 at 13.58.21.png (171.08 KiB) Viewed 2048 times

-
A good idea but possibly could do with some rewording.

Just a suggestion:

Suppressing IDE Messages is likely to prevent parts of the IDE working properly.
It's best to leave this alone if you are unsure.

This can be useful during development if you do not want key commands or
mouse clicks captured that would interfere with you ability to access development
features of the IDE.

-----
Personally, I have the Messages suppressed during about 50% of my development work.

[tperry2x]

There's another reason I added this. A lot of things within stacks and within the IDE are sending messages in [duration]. Turning off (suppressing) the messages, effectively stops some functions being sent and interpreted as they should be, so it's not all about mouse clicks and such.

So I've kind of been deliberately vague, as the alternative is a very long-winded explanation.

[richmond62]

One of the the reasons I tend to suppress messages is because I have a lorry-load of mouseEnter and mouseLeave messages that fire in images-as-buttons even in development mode.

keyDown and keyUp messages also seem to 'filter through' from objects at the wrong sort of moment while doing development.

[richmond62]

I DO like both your 'trap' on opening a stack from a file
-

Screenshot 2025-03-02 at 20.53.45.png (75.92 KiB) Viewed 2038 times

-
as well as your 'trap' on attempting to suppress messages.