Composed Widgets limitations

LiveCode Builder is a language for extending LiveCode's capabilities, creating new object types as Widgets, and libraries that access lower-level APIs in OSes, applications, and DLLs.

Moderators: LCMark, LCfraser

PaulDaMacMan
Posts: 324
Joined: Wed Apr 24, 2013 4:53 pm
Contact:

Re: Composed Widgets limitations

Post by PaulDaMacMan » Wed Sep 09, 2020 6:15 am

mwieder wrote:
Tue Sep 08, 2020 10:03 pm
Not sure about that.
Shouldn't there be a mouseEnter() after the mouseLeave() at line 341?
Otherwise it looks like the event_mfocus() just returns True and we're done.
Lines 364-366 look like they're doing the right thing, but only if the mouse isn't already down.
I'd add a

Code: Select all

mouseEnter(m_mouse_focus);
after line 341 (with curly braces of course for the conditional) to fix it.

Disclaimer: this is my first time looking into this section of code, so I could be way off base.
It sure would be great if this got fixed and I could do this thing as a composed widget. I just spent a bunch of hours tweaking the positions of 127 Paths! The scaling / position calculations are odd (7 white keys, 5 black keys) and so doesn't divide equally / evenly, each path must be individually tweaked to look right doing this as one huge widget... almost done that part now though, looks good even at large size on a high DPI display.
My LCB Repos: https://github.com/PaulMcClernan/

Post Reply

Return to “LiveCode Builder”