@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 All included files should be available from the little drop down at the top of the script editor in which they are included.

ahh ok I see thank you! been meaning to subscribe to your patreon gonna do that now

@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 All included files should be available from the little drop down at the top of the script editor in which they are included.

ahh ok I see thank you! been meaning to subscribe to your patreon gonna do that now

@thrice801 said in Issue with working with global scripts/recompiling after fixing errors:

@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 said in Issue with working with global scripts/recompiling after fixing errors:

where when I go to fix the error in the global script

Are you editing it within HISE?

When you hit compile in HISE it saves the scripts.

Are the scripts added to your project using include statements or are they linked to MIDI processors as external scripts?

@d-healey Wait, I spoke too soon. I forgot, I was editing via atom, because the hise explorer has my local project files in the tree, and the global script is not referenced there. How would I edit those scripts via the hise editor in the event that I'm not supposed to be editing them with an external editor?

include statements, i.e.

include("{GLOBAL_SCRIPT_FOLDER}helpers.js");
include("ui.js");

I also just realized, when I try to click on that "ui" file to open it in the code editor (that one is located in the local project scripts folder), it throws a message saying "that file is not included in the current script processor, would you like to add it to your project", and then it copies an include statement to my clipboard, but it just keeps doing that everytime I try to open it. So I must be misunderstanding something or doing something wrong here.

@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 said in Issue with working with global scripts/recompiling after fixing errors:

where when I go to fix the error in the global script

Are you editing it within HISE?

When you hit compile in HISE it saves the scripts.

Are the scripts added to your project using include statements or are they linked to MIDI processors as external scripts?

@d-healey Wait, I spoke too soon. I forgot, I was editing via atom, because the hise explorer has my local project files in the tree, and the global script is not referenced there. How would I edit those scripts via the hise editor in the event that I'm not supposed to be editing them with an external editor?

@thrice801 said in Issue with working with global scripts/recompiling after fixing errors:

@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 What do you mean by global script?

Do you mean external scripts in the global scripts directory?

Ya I do sorry.

ah ok that could be it, no I was editing the global scripts via atom. I'll try using the editor to edit them and see if I get same result.

@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 What do you mean by global script?

Do you mean external scripts in the global scripts directory?

Ya I do sorry.

@d-healey makes more sense now thanks!

I am working on a hise project, and using global scripts. When I make a code change to the global script, then hit compile; if there were any errors trying to compile, it will get caught in this recursive situation, where when I go to fix the error in the global script and hit compile again, my code in the global script will automatically be reverted back to the erroneous state it was in. (it overwrites the code I just fixed in the global script.) - is there some way to prevent this behavior or something I'm missing?

ah thanks! was looking for answers earlier and skimmed through it but skipped the callbacks at the beginning.

-- ah ok, so the main module UI stuff I see in hise, is just hise editor specific UI stuff then?

Also one more question, how do I insert the actual AudioLoopPlayer into the main ui? Do I need to create a panel (or floating tile) and insert it somehow in the onInit, because I don't see how to do it via the UI.

Hi, have some basic things I'm still trying to figure out.

I have a AudioLoopPlayer which I am trying to click a button, and have it set a file on the AudioLoopPlayer, that part is working now. I will attach a screenshot for reference below, but questions are:

1. When I play the loaded file back by clicking on my keyboard, I get a horrible 8bit ish screeching noise rather than the actual sample I loaded. any idea why that would be? (update, HISE crashed so I reloaded it, and it's now playing back fine. but any idea what would have caused that? I am also seeing like 70-80% CPU usage by hise, even while idle as I type this, is that normal?) (update 2, I removed some code in my onInit, that was looping through Synths doing something like Synth.getIdBy when trying to (or something I don't remember exactly, guessing that was the issue?))

2. I don't use xcode much, but I built HISE through xcode - everytime I want to run it, I open up xcode and click "Start the active scheme" - Is this the correct thing to be doing? I am getting quite a few crashes (seemingly randomly, or maybe from my computer sleeping or something, IDK), but, when it does that, xcode catches the error, and I have to click stop and play again to restart it. I'm assuming even if I was running a compiled binary version of it or whatever, HISE would have crashed, but ya is this the correct way to be running HISE after building?

3. I see you can use CSS to some degree to style components. Are you able to style parts of individual controls and things, and if so, is there a reference as to what the structure of each control looks like for the sake of styling? can you do things like #some-control-id Slider (like target slider like an html element, and or child parts of the slider, knob or whatever, to style the individual parts)

4. Regarding q3 above, can you style the default controls on the modules and things? Like, can I style my AudioLoopPlayer differently than the default styles? (and again, is there documentation referencing the structure of the elements if so)

5. in the screenshot, I still don't understand the lifecycle functions, except onInit - are they linked together, (can onControl for example, reference variables defined in the onInit script). And also, I tried putting code into onControl and onController thinking that any time any control was clicked in my ui, it would fire at least one of those callbacks, but that didn't seem to happen. how are those used?

Any help much appreciated in advance!