Improve updates of outlining nodes

Hi Tobias,

It's hard to say what's going on without seeing it happen and being able to debug it.  If you'd like us to take a look, please make a new simple sample project that shows the issue e-mail it to our support address, referencing this post.  Rename the .zip file extension so it doesn't get spam blocked.  Thanks!

Well I currently don't have the time for a sample project, but the key facts are, that the outlining node covers the whole function, not only the body. So the first offset is the 'M' in "MyFunc".
The outlining node does not start with the '{' because we want the expand/collapse button to be in the same line as the header.

The second thing is, that I cannot update each outlining node whenever I get new parse data. This is just way to slow. We have to deal with generated code in our editor that has more than 300k LOC in a single file (~18MB). So I only delete the outlining node if they have been removed completely.

I think I could workaround the issue, if I delete the whole node as soon as the first offset is deleted, but I figured your update mechanismn should cover those operations (or at least the replace operation).

Hi Tobias,

I'm not sure how you are doing outlining, if it's manual or automatic.  But if it's more manual, it sounds like there might not be anything we can do here since in the scenario you mentioned, typing to replace MyFunc will cause our incremental update logic for the outlining tree to move the outlining node's start offset to the next character, which is the '(' and then the "Foo" that is typed is effectively inserted prior to that node.  The node doesn't expand to include it.  That is intended by design.  It's really up to whatever is creating the nodes to know and alter the node such that it would cover the "Foo".  With automatic outlining, we do the same incremental update logic and then the automatic outlining which comes in later (generally from work done on a worker thread from parsing) on will tweak things as needed, by sliding the outlining node's start back to cover "Foo".

Okay. Maybe I can tweak the update scenario. I get all the correct offset from my compiler, but I only add or remove nodes, because I figured the automatic updates cover most cases. Plus updating outlining can get extremely slow for 20k nodes.