[krita] [Bug 391511] Canvas is not updated when Node::setVisible() is called from python script

[Boudewijn Rempt]

https://bugs.kde.org/show_bug.cgi?id=391511

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Boudewijn Rempt  ---
Okay, then we can close this? I'll try to figure out how to improve the dox;
right now, the example for this is with cerateFillLayer

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 391511] Canvas is not updated when Node::setVisible() is called from python script

[Aurélien Da Campo]

https://bugs.kde.org/show_bug.cgi?id=391511

--- Comment #2 from Aurélien Da Campo  ---
Thanks a lot it makes a lot of sense.

So yes indeed that's not a bug in my sense. Just me being lazy to figure it out
or simply a lack of documentation regarding this specific thing.

I actually looked for Document/Node::updateXXX, Document/Node::invalidate() or
Document/Node::validate() but didn't find the Document::refreshXXX() one ;)

It works fine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 391511] Canvas is not updated when Node::setVisible() is called from python script

[Boudewijn Rempt]

https://bugs.kde.org/show_bug.cgi?id=391511

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
   Platform|Other   |MS Windows

--- Comment #1 from Boudewijn Rempt  ---
You should call doc.refreshProjection() after adding a node to update the view.
We made that a separate step because updating the projection after adding a
node can take a lot of time.

So, I'm not sure whether this really is a bug that should be fixed...

-- 
You are receiving this mail because:
You are watching all bug changes.