sven.langkamp at gmail.com
Sun Apr 29 23:44:47 CEST 2007
On 4/29/07, Boudewijn Rempt <boud at valdyas.org> wrote:
> On Sunday 29 April 2007, Sven Langkamp wrote:
> > On 4/29/07, Casper Boemann <cbr at boemann.dk> wrote:
> > > indeed slangkamp had worked on it a couple of weeks back
> > >
> > > maybe he can tell you more
> > The explanation for this is:
> > Unlike 1.x the redo is called on every commands which is added to the
> > undo stack (due to change to qundostack).
> > Transactions are normally executed imidiately by Krita, so the redo
> > call from the undostack would cause a double redo. To prevent this i
> > put in a check to block the first redo call.
> > In this case the problem was that in a KisSelectedTransaction the
> > child transaction wasn't noticed about the first redo so it still
> > blocked. I commit a fix
> > I hope this clears everything up
> I may have messed up recently, then. On adding a layer, the layercommand's
> redo method was explicitly called, which messed up the layer model (because
> the layer got added twice, the second time failing because of an assert), so
> I removed the call to redo() -- was that right?
I think so. That was probably a call needed by the old system and
renamed it too fast instead of removing it.
More information about the kimageshop