Threading (plus random question)

[Monte Goulding]

> On 9 Sep 2016, at 5:38 AM, Richard Gaskin <ambassador at fourthworld.com> wrote:
> 
> Speaking of:  I dislike being overwhelmed with too many Prefs settings as much as teams hate the technical debt they impose, but  -
> 
> I wonder if it makes sense to add some sort of option to stop the real-time reformatting so I can type at my natural speed without waiting for LC to finish figuring out how it thinks my typing should be altered.
> 
> It's not that I type that fast, but the SE works *really* hard trying to second-guess what I'm doing.


I think it’ the colorization that is causing you pain here rather than the script editor actually doing anything significant.

This shouldn’t need to be a preference we just need to work out how to do it better. I’m trying to sort out multiline comment colorization and formatting when I get a chance on rainy weekends etc and I’ve ended up realising there that we need to let the user type and track the dirty line range then have a callback that does the colorization which we cancel and send again as they type to avoid doing any significant work while they are typing. It’s particularly an issue with multiline comments because they can change the colorisation of large areas. Type /* at the top of a 10000 line script and you don’t really want the entire thing colorized if you just want to type return return */. I don’t think users will mind very much if things aren’t correctly colorized for a few milliseconds while they type fast.

Anyway, it’s bit of a long term when I have time project to sort that out so I’m happy for ideas.

Cheers

Monte