Develop branch build status
-
Another highlighting glitch. I can't select the closing curly brace with the mouse when line breaks are disabled, re-enabling line breaks solves the issue.
-
No horizontal scrollbar when line exceeds editor width and line breaks are disabled.
-
Tab spacing is inconsistent.
This might be a linux only problem - I remember fixing tab intention on macOS (I think the new line characters messed it up somehow). Can you reproduce this on windows? (I can't).
No horizontal scrollbar when line exceeds editor width and line breaks are disabled.
Yeah, I haven't added one yet, I'm too lazy.
The rest of the editor things should be fixed.
-
A double click on an entry in the APICollection now does not add a new line in the editor with the selected entry.
Is this only the case for me?
-
@MikeB same here
-
@MikeB same here
-
@Christoph-Hart said in Develop branch build status:
Tab spacing is inconsistent.
This might be a linux only problem - I remember fixing tab intention on macOS (I think the new line characters messed it up somehow). Can you reproduce this on windows? (I can't).
No horizontal scrollbar when line exceeds editor width and line breaks are disabled.
Yeah, I haven't added one yet, I'm too lazy.
The rest of the editor things should be fixed.
Thanks, you've been busy!
I'll investigate the tab spacing further.
Is this only the case for me?
Me too
-
@Christoph-Hart said in Develop branch build status:
The rest of the editor things should be fixed.
The drag highlight thing is almost there, but I can't select the first character
Console still doesn't auto-scroll to end (Linux only maybe?).
I noticed another quirk. When writing a function name, for example
Console.print()
When you add the opening parenthesis it adds the closing one automatically, this is good, but if you hit delete after the opening parenthesis, to delete the closing one, it deletes both of them. -
If other individual features could be switched on and off via the context menu (View Option), that would be helpful.
Here on the Mac, the editor is often laggy.
With the option mentioned, one could also determine
the reason for this and then switch off the function temp. -
Problem with rebuilding the interface, only noticed it in the most recent commit but may have been there before. This is sometimes causing crashes when adding new components.
In this example I've added a panel and given it a paint routine that just fills it with blue.
Update: Actually I can trigger the crash consistently, it's triggered when clicking back in the code editor from the interface designer after adding a new control. Haven't been able to isolate it in a new project yet though, only in the project I'm working on, will keep trying to isolate it. The debugger takes me to line 414 of
CodeEditorApiBase.h
but I'm not sure what I'm looking for. -
Ok the crash is reproducable and it's weird.
- New project.
- Add a panel to the UI.
- Add a reference to the panel to your script.
- Set the panel's mouse callback to an empty function (you don't need to enable mouse callbacks in the property editor)
- Hit F5 and notice in the component list
(...)
appears next to the panel's name - In the interface designer click the button to rebuild the UI and notice
(...)
goes away from the panel's name - Click in the script editor and kabooom!
@Christoph-Hart Let me know if you want to do a debug session on this one if you can't recreate it
-
@d-healey oh this is what I got today too! In my case, it was when removing from the interface a panel that has been declared and painted through a timer...
I also had the blue colour thing, in my case I just had a wrong colour code value and discovered that Hise replaces it with this marvellous blue
-
@d-healey Thanks for the step list, should be fixed now.
-
@Christoph-Hart latest commit, all written code is gone, no NoteOn or NoteOff callbacks etc...
-
yes I noticed that too, should be fixed now.
Meanwhile I've introduced a new glitch when you add a new line at the end of the code, but I'm too annoyed to fix this. Classic case of one fix, 5 new bugs...
-
@Christoph-Hart said in Develop branch build status:
but I'm too annoyed to fix this. Classic case of one fix, 5 new bugs...
You've been busy. Take a break!
-
@Christoph-Hart @d-healey
This morning 6 o'clock (Berlin-Standard-Time)
downloaded the latest version and compiled it.
MacOS - Without errors.Worked with it for 4 hours - occasional crashes.
e.g. when I put the cursor into the editor.The error is still there
if you type an open brace and return you get this:if{ if if
-
Another small problem is the constant opening of the autofill window. It prevents you from making corrections and if you are not careful and click too fast you suddenly have some code inserted.
Can't you do this like before by pressing the ESC key or at least switch the autofill on and off via SchortCut?
-
Can't you do this like before by pressing the ESC key or at least switch the autofill on and off via SchortCut?
Yes good idea, it's added to the context menu.
if you type an open brace and return you get this:
It's fixed now.
Worked with it for 4 hours - occasional crashes.
e.g. when I put the cursor into the editor.Can you pinpoint it to something reproducible? I suspect it's the generation of the debugging objects in the background that's causing the crashes (like the one David reported with the blue panel).
-
@Christoph-Hart said in Develop branch build status:
Can't you do this like before by pressing the ESC key or at least switch the autofill on and off via SchortCut?
Yes good idea, it's added to the context menu.
if you type an open brace and return you get this:
It's fixed now.
Sunday - Quick support - Super Thank you very much
Worked with it for 4 hours - occasional crashes.
e.g. when I put the cursor into the editor.Can you pinpoint it to something reproducible? I suspect it's the generation of the debugging objects in the background that's causing the crashes (like the one David reported with the blue panel).
Happens again and again when working on the LAFs.
But I can't really narrow it down yet.
I ran the stopwatch today because I suspected that it always happens when the file is saved automatically - but a correction is made at exactly the same time.
My assumption came from the fact that sometimes the last autosave file cannot be opened. So HISE obviously didn't finish saving.Will report further