Follow-up Comment #3, bug #16304 (project mypaint):
Actually bug #16824 and this one have the same cause: the entirety of
BrushManager.selected_brush_observers firing before the current brush's
settings are loaded from a separate string.
Complicated by Application.brush_selected_cb() updating the active drawing
brush's settings from whichever ManagedBrush.settings_str it's called with,
even if it's one from the palette (as here) or the default None one used wen
setting from a strokemap (as in bug #16842).
The subsequent calls to app.brush.load_from_string() therefore have an effect
on the current brush, but not on the GUI which has already been updated with
bogus information. And since the GUI settings are used by the Bigger and
Smaller commands, you see odd behaviour when a brush is picked from the
strokemap or someone changes input device.
Brushkeys don't suffer from this since the handlers for those use their own
non-persistent ManagedBrushes, one per key, that the code sets the
settings_str on directly before entering observer callback hell.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?16304>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
