Update Prompt Frame Start/Finish - Responsiveness

[sashaagafonoff]

I haven't tried to debug it, but it feels like there's a callout to some other function whenever I change a frame number of a prompt (which sadly is more frequent than I'd care to admit).

So, let's say I'm changing start from 5440 to 5380 (in a 10K frame document): after I've selected the "5440", i will type 53 and then parseq will actually pause between the 8 and 0 to do some updating (i'm going to bet on the timeline visualisation), so there's a lag.

It probably doesn't matter so much for single changes, and a "workaround" is to paste the value in, but I just got my prompt positions wrong for 12 of 18 prompts, so that's 24 changes (was almost worth editing the parseq directly).

NOTE: I've noticed a similar lag on changes/selecting prompt text as well... which may be related.

here's an example document (new project):
sample 10K frame parseq doc with 18 prompts

I monitored hardware during changes, and it's only bumping CPU (10-11%) and RAM (44-46%) up slightly in Chrome.

[rewbs]

Thanks for the report, this is definitely worth improving. The debouncing when typing in prompt fields (text and position) isn't working as well as I'd hoped. As a result we're doing too many round-trips, resulting in many doc saves and re-renders.

Related: #25 .