MaxGUIs base problem is, and I think this is out of question as the win32maxgui mod shows this quite clearly, that it bases on BlitzPlus code. This itself isn't bad but the fact is that this already is based around procedural, winapi like behavior instead of the modern approach used by most other languages with event handlers and the like ...
This would need a major redesign which I'm not sure if it makes sense. Because over short or long, this module will vanish and be replaced by a .NET based one. This theoretically would then be crossplattform as well and that with far less problems than the current one.
From your example, it seems like you are going the Visual Basic way, right?
Hope you let it open for users to go the "C#" way with event handling functions that can be attached to function pointers because in the end, the VB way is "fixed" as well and to me not much better than the WinAPI constant switching way.
This would need a major redesign which I'm not sure if it makes sense. Because over short or long, this module will vanish and be replaced by a .NET based one. This theoretically would then be crossplattform as well and that with far less problems than the current one.
From your example, it seems like you are going the Visual Basic way, right?
Hope you let it open for users to go the "C#" way with event handling functions that can be attached to function pointers because in the end, the VB way is "fixed" as well and to me not much better than the WinAPI constant switching way.