Changing tablet threading direction is very slow

[Shelagh-Lewins]

When you change the threading direction of a tablet by clicking the / or \ below the threading diagram, the entire pattern preview reloads and the weaving chart is recalculated. This means that changing a number of tablets takes a long time and sometimes the changes are lost altogether.

One idea for improving this is to wait until the user pauses before updating all the data. There may also be other under-the-hood improvements possible such as only updating the affected tablet.

[CableGuy67]

I know this isn't optimal but one (sorta kludgy) way to manage this would be to allow the user to "pause" updates to allow for multiple changes to be made. After all the modifications are made the user would hit the same button again to "resume". The only problem with this is that the app will have to track all the state changes then apply them in order. I fear this may dip deeply into the way the app responds to changes though.