The definitive feature request & bug fix roadmap
-
BUG FROM LAST COMMIT
@Christoph-Hart Updated to last commit and got an error for timer objects:
Interface:! ReceiveRecording.js (7): Unknown function 'stopTimer' {SW50ZXJmYWNlfFJlY2VpdmVSZWNvcmRpbmcuanN8MTM5fDd8MjM=}
Context:
const var timer = Engine.createTimerObject(); timer.setTimerCallback(function() { this.stopTimer(); // Throws an error and even crashes Hise after a moment }); timer.startTimer(2000);
but
timer.stopTimer();
works inside the CB. Strangely, it was also working before the last commit... -
@DanH said in The definitive feature request & bug fix roadmap:
BUG?
AudioWaveform now has a nice green box around it in Develop Branch that can't be changed / removed
@d-healey said in The definitive feature request & bug fix roadmap:
@DanH I think that will disappear once you compile. It's the same for tables.
Nope, The Green Box (Around The Audiowaveform)
Still Shows Up And Won't Hides On Compiled Plugin.AudioWaveform Connected To Sampler
-
@Natan Workflow until the BugFix
Put it in a panel and give it the position (-1, -1, panel.width +1, panel.height +1)
So the frame disappears behind the panel -
This post is deleted! -
@MikeB No Need For That, I Hacked The Entire Border On Source Code, To Make It Minimal, Waiting For A Bug To Get Fixed For PopUp's, After That Going To Make My Own Changes To The Source Code :)
My Version :) Minimal | Flat | Elegant | Eye Catchy
Sampler, Has No Dragging Start/End Points,
@Christoph-Hart So I Believe This Can Be A Request To Having The Choice To Selecting Border(true) Border(False) -
FeatureRequest:
An Option To Enabling / Disabling The Borders Around The AudioWaveformSampler Has Nothing To Do With It!!! So Why Not?
-
This post is deleted! -
I'm sure it is already hard for Christoph to follow all the requests we do, so I personally think it might be a good thing for all of us to follow this rule:
@Christoph-Hart said in The definitive feature request & bug fix roadmap:
Hi everybody,
... Any discussion about a certain bug / feature should be a dedicated thread (you can add a link to the discussion thread in the post).
-
Really enjoying the new autocomplete features.
One question. Using the F8 key we can assign a type to function parameters. Is there a reason you didn't choose to allow the type to be assigned directly in the parenthesis?
i.e.
inline function myCallback(ScriptButton component)
? -
Function parameters can‘t have a type specifier in Javascript so this would break many language idioms.
-
Both the console and the script editor seem to be using the code editor font size in preferences as the default font size and this is making the console font much larger than the code editor font.
-
@d-healey And Another Thing That I Noticed Is That Right Clicking On Console, To Cleaning Up The Reports Is Laggy.
Some Times Works, Sometimes Need 3/4/5 Clicks To Get The Pop Up To Clean The Console. -
@Natan on my Mac it works as usual!
Are you on Windows? -
Feature request Global setting to disable line breaks in the new script editor.
-
@d-healey said in The definitive feature request & bug fix roadmap:
Feature request Global setting to disable line breaks in the new script editor.
??!
-
@MikeB Yes but when you open a new project you have to do it again. I want to turn it off for every project.
-
@d-healey I understand
-
SCRIPTNODE BUGS
-
Connecting a container parameter to another container parameter doesn't work (but the cable is created)
-
Generally, duplicating chains or wrapping nodes into a new chain not only loses cable connections but makes a mess among the ones that subsist...
-
container.chain is still not taking the bypass into account
-
Reopening a project shows strange connections in the edit parameter window:
-
-
Alright, I'm gonna close that now. @ustk can you make a dedicated thread for these scriptnode issues (with an example snippet that demonstrates the latest problems).