@aaronventure nope

@Soundavid Cool, would be nice if you can make a pull-request

@d-healey yes, several of them. Oddly enough, only one of them produced the error...

Edit: I just did a test, I actually don't need it in my project.

@d-healey Got it, I'll try it, thanks for the guidance🥓

The CI for the fix seems to have got stuck https://github.com/christophhart/HISE/actions/runs/12342377762/job/34442128570

@ustk said in HISE keeps recreating files I've deleted - or from different projects/snippets:

@d-healey Well I don't remember when it first happened, but I'll try your fix asap!

Did you try it? I'm seeing my files being overwritten by other projects still.

@Christoph-Hart Fixed, PR -> https://github.com/christophhart/HISE/pull/640

yes that's a known issue. Unfortunately solving it means that the code tokenizer would have to scan the entire file to grab the correct colours which comes with a huge performance hit on large files. It's obviously possible to solve that, but not super trivial.

@orange I am getting weird behavior when using the Engine.addToModuleState() function.

I feel like its related to the multichannel issue and it always assumes 2 channels are used. I hit a roadblock here. Maybe @Christoph-Hart can help.

@d-healey Great job, David. Thanks.

That Pull Requests tab looks a bit depressing, though - lots of good stuff there.

@ustk said in Warning - Snippet Browser overwriting the current project:

This really, really needs to be a top priority fix

Yup - https://forum.hise.audio/topic/11130/hise-keeps-recreating-files-i-ve-deleted-or-from-different-projects-snippets/4

Hi @skyscapeparadise!

Try compiling Hise without Loris. Here the example repo works fine.

(btw experimenting with that tool, a bit overwhelming)

@Consint Done, and I made a PR.

@HISEnberg usualy there should be no script network xml because this workflow does not save the node since thats the root of the error.

Did you try it?

Haha it was a Christmas present last year along with the clone nodes etc.

@HISEnberg 3f5719e3-a59f-4ab5-baff-381867cf6bc3-image.png

@VirtualVirgin said in ScriptButton.setZLevel not working?:

so I am supposing that is how they would appear in a build?):

I would think so but I've never done anything like this so there's only one way to find out.

@Straticah you could record one sample per octave, so you'll have just a few more samples to handle but they won't be over-stretched.

Also affects the MPE floating tile - and CSS doesn't appear to apply to that one so no workaround there and I want to avoid the CSS system for now anyway.