For 65:
This patch looks rather dangerous to me. Who is responsible to create or destroy WindowClosed objects?
What is the value of the this pointer when the on close event is triggered?
What happens if the window is last created on the second monitor which is non-existent anymore!?
I've updated it :
https://sourceforge.net/p/codeblocks/tickets/65/For WindowClosed object, good question for creation/deletion. I've tried to remove Class definition here, but no success. From my undesrtanding
&WindowClosed::OnWindowClosed
is a member function pointer, no instance creation/destruction, static binding
pointer in
is also invalid and must not be used. It acts as a pure static function. May be I missed something ?
For multi monitor, I've tested it. I've added basic check that put window back to default position if it's not enought visible on at least one screen of system