Skip Action to become part of history

[imaneumma]

Hi,

Is there any way to skip an action/actions on an object to become part of fabic-history stack?
e.g
If a number of items are allowed to be added in the canvas but a default object should not be affected by undo/redo. It should remain there and undo/redo should work only for the actions on rest of the items

[DigitalFlux]

I use offHistory() and onHistory() for this. I recently found that an app I'm writing was thrashing memory because fabric-history was saving every object added during the loading of a canvas from file (oof!), and I was able to get loading times down from approx. 8 seconds to about 300ms. Being able to turn it off during loading made a huge difference.