administrators group

Christoph Hart

@Orvillain haha one more lane, bro! I haven't tested 8 pages but I can imagine that it runs against the same node dimension limitation as the parameters before.

Christoph Hart

Is there a way to update the scriptnode UI with the relevant new parameter

Not without hacks. The best way of thinking about this is a black box communication of parameters into the node. Now if you want to update a UI state that you display on the plugin interface, global cables (and their data callback) are the way to go, there you can easily pack everything up into a nice JSON and send it back to HISE Script (on a deferred thread!), but I wouldn't recommend going the extra mile of updating the internal scriptnode parameters only so that you can look at them in the network with the right value.

Christoph Hart

@ScreamingWaves I can't offer support for anything else than the latest Xcode because macOS regularly messes up stuff with updates to either macOS or Xcode so we have to agree on something and this is the rule.

Xcode 16 works.

Dominik Mayer

@Lindon
Yup, confirmed..

I will update the forum software in the next days trying to fix this.
As always there might be some hiccups and newly introduced glitches, so please bear with me :)

Best,
D

Christoph Hart

@Lindon yeah, the AI bot scraping is kind of maxing out the server capacity, not much we can do here except for upgrading the server when it gets too annoying.

Christoph Hart

@blackbneard You're almost there, the only thing you did wrong was using more function arguments than necesssary. setParameter() always requires a single argument that contains the parameter value and all the branching is done with the template constant like you assumed.

template <int P> void setParameter(double value)
{
    if(P == 0) thresh = (float)value;
    if(P == 1) attack = (float)value;
    if(P == 2) release = (float)value;
}

Christoph Hart

@Orvillain have you tried the new pagination feature? That allows you to subgroup parameters into pages. It looks like this is just an UI problem and having a node with 100 knobs will look very ugly anyways.

Christoph Hart

Aw poor @VirtualVirgin that was half an hour that you'll never get back, sorry for being not clear enough.

So basically what happens is that I'm taking the markdown files from GitHub to build the HISE docs website. The documentation generator takes some autogenerated code and merges it with the additional text from GitHub - this way it stays always up to date and the formatting is consistent.

Now the problem was at some point (and we discussed this at some HISE meetup) that the user engagement with the task of contributing to the HISE documentation is mostly hindered by the complicated system that people have to follow in order to write the docs so we came up with the solution that the HISE documentation generator just creates these empty markdown files for all undocumented API methods that have the proper file name / folder scheme so that they will show up later in the docs. From there, people can just edit the empty files to add more context, code examples or more thorough explanations than the one liner API help that is being extracted from the HISE source code.

So what looks like a bug to you - empty text files - is actually a feature that is supposed to lower the barrier for user contributions.

Christoph Hart

@Straticah nice one, looks great!

Christoph Hart

They are autogenerated and empty so that you can edit them and fill the gaps :)

administrators

Posts

Member List