The setDirty() call should happen somewhere at the higher level. I guess there was some code for it. I'll check later today.

Ok

I have pushed the fix with a minor change: setDirty() should always be called after the change has been done, not before that. Otherwise the patch was correct. Looks like I dropped the update part when refactoring this code to the strokes framework :)

Ok thanks. It almost drew me crazy.

actually the setdirty call wasnt working outside the lambda command. So i was a bit confused about calling it a from a higher level.

In D18790#407680, @ashwind wrote:

actually the setdirty call wasnt working outside the lambda command. So i was a bit confused about calling it a from a higher level.

Yes, because lambda is called from the context of the worker thread asynchronously. Much later, that the command itself is created.

Usually, we delegate doing updates to the KisProcessingApplicator, or some undo commands. See rootNode parameter of KisProcessingApplicator and KisKeyframeChannel::requestUpdate(). The latter one is supposed to be used in the undo commands of animation-related code, but it looks like it is not applicable here...

Yeah I actually got that far yesterday. Stepping through the code, but wasnt sure if that is actually the thing.

Thanks :))