Why is OnMessage not planned? #319
-
Just curious, because I was thinking of doing something like a "close" window handler specifically for Discord to perform minimize instead, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hmm. Taking a closer look at this, I think I decided that status due to a misconception about its use cases. I previously understood OnMessage to be exclusively for receiving messages of GUI application written with AutoHotkey. Currently, besides the few boxes we already have implemented, there aren't any plans to support AutoHotkey's GUI functionality in the library (that's something I can expound on further, though that's a whole other topic), so I initially set this Now that I'm looking closer at this, it's clear to me that While I'm thinking through the implementation of the feature, it would be helpful for me if you could explain what use cases you might have for this. That way, I can test those use cases as I develop it. |
Beta Was this translation helpful? Give feedback.
Hmm. Taking a closer look at this, I think I decided that status due to a misconception about its use cases. I previously understood OnMessage to be exclusively for receiving messages of GUI application written with AutoHotkey. Currently, besides the few boxes we already have implemented, there aren't any plans to support AutoHotkey's GUI functionality in the library (that's something I can expound on further, though that's a whole other topic), so I initially set this
OnMessage
feature as not planned under that misconception.Now that I'm looking closer at this, it's clear to me that
OnMessage
has uses outside of AutoHotkey's GUI functionality. I believe this is something I can put on th…