Open GoogleCodeExporter opened 9 years ago
Dear all,
I already solved it for my special purposes.
I just store the actual mutator variable values (e.g. itemCount_, etc.) into a
separated list (or variable in general), change the mutator variable (e.g.
itemCount_) as required, call mutationToDom() and reverse the process
previously performed. I put all the old values stored in the list back into
place. Only after that domToMutation() is called and the block is mutated as
expected.
Since the problem is solved there is no need to change anything.
BUT it would be nice to prevent uncaught expections just because an already
none existent input can't be deleted.
Original comment by borntob...@googlemail.com
on 19 Dec 2012 at 10:08
Original issue reported on code.google.com by
borntob...@googlemail.com
on 19 Dec 2012 at 9:43