You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys, quick question for what I suspect is a perfectly understood situation:
I've created a fiddle https://jsfiddle.net/sibbaldl/f6q3agtf/1/ that demonstrates a simple situation whereby, if a canvas is initialised with "stateful:false" the "object:modified" event won't fire when moving the red square around and releasing the mouse button. The event will fire if stateful:true.
It took me a while to realise the cause of this in my code, because even with stateful set to false other events such as scale,rotate,move will fire.
Just wanted to know if this is expected behaviour.
I checked stateful situation.
It looks like it has been left uncompleted.
stateproperties are lot, but the only check we have on "hasStateChanged" is on "finalizeCurrentTransform"
We can fire object:modified anyway there, but at this point statefull will become useless because it will collect stateproperties before every transform, but it will never check them.
Also stateproperties include lot of properties ( fill, stroke, opacity... ) and those do not have correlation with transforms.
(cross posting from google groups)
Hi guys, quick question for what I suspect is a perfectly understood situation:
I've created a fiddle https://jsfiddle.net/sibbaldl/f6q3agtf/1/ that demonstrates a simple situation whereby, if a canvas is initialised with "stateful:false" the "object:modified" event won't fire when moving the red square around and releasing the mouse button. The event will fire if stateful:true.
It took me a while to realise the cause of this in my code, because even with stateful set to false other events such as scale,rotate,move will fire.
Just wanted to know if this is expected behaviour.
Cheers!
Lee
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: