Re: Composed Widgets limitations
Posted: Wed Sep 09, 2020 6:15 am
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.mwieder wrote: ↑Tue Sep 08, 2020 10:03 pmNot 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 aafter line 341 (with curly braces of course for the conditional) to fix it.Code: Select all
mouseEnter(m_mouse_focus);
Disclaimer: this is my first time looking into this section of code, so I could be way off base.