btw, the latest trunk revision should give you a better mouse handling.
It seems as if the mouse click position has wrong coordinates in last trunk for custom controls.ah...i wonder if that's related to the support of borders.
...
It seems as if the coordinates are mirrored.
ah...i wonder if that's related to the support of borders.
any lightweight sample?
No, but it's maybe related to the mouse event handling.The most annoying part of Cocoa (AppKit) is their coordinate system, which goes from the bottom to the top. (just like any other).
I'm on the run that moment, but I can try to create an example later.the change for the border support was introduced in trunk. (The change is risky, no matter how to do it. I believe you're experiencing the side-effect)
That behavior was not there in the official release 2.04.
PS: I have tested a bit and the error seems to happen in LCLIntf.ScreenToClient(self.handle, p) while X and Y of the MouseDown event are correct.r61705
still exists different behaviour of running from IDE and the app bundle (form activate the form is not shown).the reason for this to happen is guessed (macOS compositing engine!), and the cure is unknown.
PS: I have tested a bit and the error seems to happen in LCLIntf.ScreenToClient(self.handle, p) while X and Y of the MouseDown event are correct.r61705
Hi
Looking at the behavior when bringtofront is called for a panel. It appears as though the Y ordinates have been flipped.
Is it possible an issue, because Cocoa screen ordinates start top,left and lazarus start bottom-left.