New Script Editor

[ustk]

@d-healey said in New Script Editor:

Doesn't work for me, I get a compile error

Confirmed...

I've also seen that the Code Bookmarks

//! Comment with an exclamation mark

Don't appear anymore in the context menu

[Christoph Hart]

@ustk Can you try again? I think I've fixed the lag and now it should be as responsive as the old editor irregardless of the line break state.

[ustk]

@Christoph-Hart Worse than ever, all code is gone
But it's working somewhere in the background as my interface is running...

[d.healey]

@ustk Try latest commit

[ustk]

@d-healey Oh yes it just arrived...

[ustk]

@Christoph-Hart Well... That almost did it, new line and typing are definitely as they should now, but backspace lag is even worse

[d.healey]

@ustk Seems fine to me in a fresh project

[ustk]

@d-healey Yeah in the lorem ipsum from above too, but not in my 200 lines project... Line number might be the issue I don't know...
@Christoph-Hart BTW, openGL HAS to be enabled on mac, or scriptnode is not even usable as soon as you have a few nodes... anyway it doesn't change anything about the code editor, so I keep it enabled

[ustk]

Precision: the backspace lags only when deleting a char/space. It's fine when deleting a line.
In fact, everything that involves deleting a char (so pasting, back-tab...)

[Christoph Hart]

Please try again now, I've reworked a bunch of things including the backspace lag.

[Natan]

@Christoph-Hart Christoph
This One Failed To Build :/

• code editor: added horizontal scroll bar

Win 10 VS2017

[d.healey]

New strangeness with tabs

[Christoph Hart]

Does it help if you change this line to

#if JUCE_WINDOWS || JUCE_LINUX

I think I had to hack around to fix that on macOS but it might be the same as on Windows for you...

[d.healey]

@Christoph-Hart I'll try it now. Despite Mac being Unixy I find Debian UX often has more in common with Windows.

[d.healey]

Yes that worked. I'm finding now that the first tab on the line is 4 spaces and all tabs after are 3 spaces. Is it the same for you?

[Christoph Hart]

Erm, it's supposed to be like this. A tab goes to the next multiple of 4, so if you start from 0, then it will go to position 4. If you enter a * and press tab, you start from position 5 so it just fills up 3 spaces.

[d.healey]

@Christoph-Hart

[d.healey]

Comments changing colour when scrolling. Happens as soon as the /* goes off the screen.

[d.healey]

• Matching brackets/braces are only highlighted when selecting the second one of the pair.
• No code folding in included external files

[Christoph Hart]

@d-healey said in New Script Editor:

Comments changing colour when scrolling. Happens as soon as the /* goes off the screen.

and

No code folding in included external files

is fixed (it was actually the same problem since the syntax highlighting searches for the last line range start to avoid coloring comment blocks, so if the line ranges aren't created, it won't work).