Right now, whether you left, right or middle click a container space, the insert menu will pop up.
I think Middle Click can be safely relegated to always pan around the blueprint. It already pans when clicking on the empty canvas area (as do all other mouse buttons), but I think it would be a nice QoL feature for the Middle Click to always pan (coming here from Unreal's Blueprint editor). Predictive/expected behavior and all that.
@Christoph-Hart said in Script panel label keyboard entry?:
I found the most embarrassing code typo ever that caused an infinite loop and crash when using the parentComponent property
lmao
happens to the best of us
Thanks guys, got it working. The references need to be assigned in the network script and if the array is declared as global, AudioFile.loadFile can be executed in the interface script to change the loaded IR.
@Christoph-Hart Out of curiosity, how does accessing the nodes work? I'm aware of creating parameters and linking them to controls, that's how I set up all my networks. Is there any reason whatsoever one would ever need to access a node directly?
@d-healey Oh man, I already have like 3 requests open. 
Necroing this to update the information that these days you should use the soft_bypass node to wrap stuff you want to be able to bypass using a script.
@Casmat Not who you asked, but there's no right answer here, it depends on your use case.
Do you need to do multiband DSP processing? Use Linkwitz-riley to split your signal into bands (you can verify that it's mathematically correct when summing by comparing the input with the phase inverted sum, which should get you a perfect silence). Do you need an oldschool synth filter? Use the Moog.
Etc. Etc. I suggest some reading on DSP and filters. I'm sure most DSP books will cover this in one way or the other, but if you want to learn about filters specifically, give this a try https://www.native-instruments.com/fileadmin/ni_media/downloads/pdf/VAFilterDesign_2.1.0.pdf
This is a very dense work but you don't need to understand all the math stuff to get a grasp at the theory and looking at the charts. If you play along with the available filters and examine the results on a frequency analyzer, you'll get a good idea of what they do. Of course if you understand the math here then this might be an interesting rabbit hole to get lost in for a few days/weeks.
HISE's behavior oddly reminds me of the final months of my late grandpa. Before he suddenly passed of the dumbest little infeksh you could get because his immune system forgot that it had to turn on due to Alzheimer's, grandpa was talking all kinds of stuff but mostly repeating himself, and they mostly get it right in the movies.
Right now HISE:
If I forgot something, feel free to add 
Sort of embarrassing that I found the solution after posting in a random David Healey post from 6 years ago.
I won't delete this out of shame simply because it's the only topic with the "multi monitor support" and someone else might find it useful.
View -> Add a floating window.
So I'll turn this into a request where this same option is added to the little popup icon in the top left corner of the GUI.
@d-healey The panel can also save an array.
The linking is a good point.
@d-healey what do you call this on? The Convolution Reverb reference? Is it per audio file?
@virtuscapeaudio Why would you need this in HISE? Are you making a standalone app?
For any plugin, you can simply use the built-in tools in Studio One/Nuendo.
What are the advantages of using SliderPack vs. using a custom scripted panel (other than the obvious instant functionality)?
What could the panel implementation be missing? E.g. in the knob/slider comparison, the panel currently doesn't support midpoint which makes it problematic for DAW automation (I wrote about this in the other thread).
SliderPack doesn't seem to offer DAW automation funcitonality, though that could be added via the panel.
@virtuscapeaudio You can write it in C++ or perhaps even in Faust/Scriptnode.
The EQ in HISE is near limitless. What you need (essentially) is a filter and a delay for each channel, and a bunch of algorithms that dictate how each of these filters behave.
Keep in mind that you can only ever "ballpark" it, as everyone's head is different. I haven't done any algorithmic binaural panning so I can't tell you for sure about all that goes into one such algorithm, but plenty of papers have been written on HRTF and how it all works.
I'm sure you can find something on github as well.
@Christoph-Hart I am fine with that. Though you might have a point there, this might be a bit of a gimmicky idea, opening a page directly in the browser is likely a safer option for more consistent results/expreience.
Ah of course. Ideally I'd like to be maintaining one doc per plugin so I would host it... on github? Written in markdown? Then reference it on the webpage and use the docs system in the plugin to pull in the docs from the target repo?
Can it play MP4 files with sound?
@Christoph-Hart I'm thinking of having built-in full fledged docs instead of just widget info on hover, is WebView something that I can leverage here, to, say point at my own website where I have the docs? This could also let me painlessly update the docs that the user sees in the plugin. Are there limitations in terms of content playback, or is it the same as the system native browser (that would be Edge/Safari)?
@bendurso I yet to get around to trying out WebView in detail, how exactly did your implementation go if you don't mind sharing?
@d-healey said in All Control Callbacks Get Triggered On Init?:
Another solution is to put a button at the end of your component tree and put your code in its callback, this will be called after all the other components. Or instead of adding a dummy button, use the actual last component in your tree if suitable.
That's a good one. Kontakt has on persistence_changed which executes after on init, meaning that on init has to pass first, which does not happen if the track is muted in the DAW or the VEPro instance isn't connected. So my instruments there always load up with the "loading" image which says exactly that, and all the UI controls get their visibility set only in persistence_changed.
But if in HISE the controls get executed after the init callback passes, then simply adding a dummy control at the end is not a big deal. Much like the PersistentData thing, or the colorPalette, or my dummy DAW automation controls. or my dummy switcheroo volume sliders. Hey, we need a dummy component list!