@Chazrox wth lol

@cassettedeath Try wrapping the snippet with ``` on both sides like this:

Screenshot 2025-03-06 at 8.26.55 PM.png

@d-healey said in Printing Viewport view positions?:

@VirtualVirgin The viewport's changed callback isn't called when moving the scrollbars. It's called when the viewport is in list mode and you select an item in the list, or when you call .changed()

I just tried attaching a broadcaster to the the property, but that doesn't work either - smells like a bug there @Christoph-Hart

The only things I can suggest trying are a mouse broadcaster or using a timer to poll for changes.

Thanks, I think I'll just leave it alone for now.
I was hoping to use it somehow as a workaround to get scroll wheel events since the panel mouseCallback does not have this data.
And that I was hoping to use as a workaround for the fact that the Viewport obscures the scrollbars when the content inside is lager than 2 dimensions.
So I think for the time being I will have to stick either a panel with scrollbars (and no scroll wheel) or a viewport with scroll wheel and no scroll bars.
Otherwise I guess I would have to learn how to edit the HISE source code, but that seems like a steep learning curve for me at the moment.

@clevername27 said in Basic Questions on ScriptAudioWaveforms…?:

I'm wondering if something may be timing out. I have like 700 Components in my tree

Easy to test. Make a blank project and add a waveform controls and loop player.

@clevername27 said in Basic Questions on ScriptAudioWaveforms…?:

Poorly worded on my part. I'm looking please to start and stop the loop player. Something like: AudioLoopPlayer.start() and AudioLoopPlayer.stop().

The loop player is triggered by MIDI note on and off I think, so Synth.playNote maybe - I'm just guessing.

@Sampletekk Yes

@iamlamprey I appreciate your response. I do not believe there is a such a thing as an "edge case". An API either works, or it doesn't.

@tomekslesicki Engine.quit()

@ospfeigrp Was that the final answer on this one?

@prehm there's been a few posts floating around on the topic of panels lately. Hypothetically the panel can store both UI and control data. In practice, for control data, it is best to use another component and reflect UI changes in the panel. So in your case, maybe try using a hidden knob for your four-button state, and using mousecallbacks and a paint routine on the panel to interact with and change the state of the knob.

You could bypass the knob altogether, I sometimes find issues with it when trying load presets or initialize the project. Really depends on what you are trying to do though.

Link Preview Image saveInPreset not working for panel data?

@VirtualVirgin You could do it like this which might make it seem like it makes more sense const panelObj = Panel1.getValue(); Console.print(panelObj.test1);

favicon

Forum (forum.hise.audio)

Link Preview Image Is panel.data persistent?

I thought it was, but this snippet seems to show otherwise. HiseSnippet 984.3ocsVstaaaCElxwpq1asXEnO.B5WJaFAVdtNdscXcwIY0aKIF0YA6eELTGGSDIRAR5rYTzm08Jr2fsC0k...

favicon

Forum (forum.hise.audio)

Thanks so much, that's very helpful, I appreciate it!

@d-healey said in Dynamic creation of components?:

@VirtualVirgin At the moment I think the only dynamic components you can add are child panels. Christoph is working on a dynamic container but I don't think it's ready yet.

Thank you :)

I looked into the child panels and made this snippet:

HiseSnippet 1736.3oc2X0saaaCElJIpq1qEqEX6tcgfuXvooMw1M8mztgk+ayV9wnNqKAAAEzRz1bQlzihNIBE4l8BrWh8fzGo8FrcNTxVR1xIoYq6h4aL34+yG44nCYckzkEDHUDqh6G1iQrticiPgtyZcnbAYq0IVuvdeVflKZ63EJnc4tNtc39dN8nBluiqhQ0bovQqBQYzRm.5oLGOplRVMrGMHf4Qrrl9Un8rJLCw76O+9Uo9TgKKgDg7VI2ksMuKWmPs9x+H22eSpGaed2TRu3xa4JEqI8k8gXeZ6JjdT2SnsY6RQwlxl7ZZPGh0CrccWbI1yaU6YUpsD6IdK1rV0JzZUVZomwnOohaykXzZsZ5VgXcqM73ZopglpYADqYVU5E1ni7LQjCdKOf2zmgKpRZ.dNh7lReOLEQpj0Pno9.PMf.VodBDOcDD+k16v83Com.02yvvIQiz.n0TYCuoyDdUSGdUREd4DRVoBoYhBo6a2vUw6oS3fwymaukPyTsnv9T5PIRVxT+wcrWSBRHzy2kdBaSErXnFkqVoRkG57zJUl8kEKVD1sBzN6.oJF20MGd9NmAp2loWS1smT.KJWJiTk.0iTdEOOCkU6q0vItIocVwRTuQ+lZE0UecrQNxlXn5LU.O.0Zc3T9kmJ4HKZnhKrfiBJqjJlitCKcIUPrWvxHTmsYh15NfCxwTnydK0uOq7rn3FZqnTzv48MZ8xh7VNkyZoYK99hEVXgXuGc5v32xPbcADZYwu4CX.JvE52H6CcAXka0W3hU7kaarzoTkCEhNcGd.FNaKco9qJ6K7BJi67EJVnMZinR0xQ+ELuOucGcaEKDEo87sfh72vb0koQqGWgl9P8cDSOE8rHgenSsgxuozr4eJSvUkvycIBuO6bf0b.Uz7WLatI4Nx9Ar0n99MAGkjkLvfZSlhPoY07t9b2SXdyVr.PtfoEXJfDwwBW.ItwQ4bR5+OP5iRCoSHSuRbcxHqGbFUICGCZMtiK7AryYfAcFea.MtOhcQEVlBC.VyzcwTtNTmsg5KiOhTyePoWuwKrRaY7aNfTkLKJ4LmynBoXmxAXXPqhDycTrKdT0iyW5UfrxriCML.XJUehxAy5P8A1dgNryg.OBG8iKxM.XVCd.55zFGS9W4KaR8qKC3HJdfI6GQuCuZ8NLO8947zK6g4ipc73585qgdO93nhL.Vv9mREuMW3zKNbbZIUF5s3JnUZJTqXAnSGaRnC7Iq7S+bYf4Wk7C+Jws.hYcdpL5.37wPKLbSOLkDGNj5YCccz5NCWm472XGpoddiTzTrfQRrfrboygx1yQponEBzBGg1YbOcGf9YiPuCCa0.L5LBCMzU.HOrnHC6I1xyrYbkM8LRLzxUSIZreMBcYMFYhXQLsFQSy7vldTQaeVYpCzgah13rNbMKlqoY4XpCZG26LWCnftZC4MRi0GWIkkMcVSxynFrEvVd3g8d8C5fCYiGtMCZSw1HHqKe7f4GY9.zNQdI9q9i1NMmdu+mzO8Z1pzL+TWI..sTxtiAGebfQjkF.GXsRltOQrgoa6Vmpvo5l.jk2HUHlgMiJyMcEb3Ne6HS1AzlatKeTBvYCchTrqTy1SDY5hWTzYTVsZkKOb9Tkz2moxkMd8J0koXYQ+tMYpG5bJBhwe4dgGD8kIAWmrGf28KZJlr3Lf.Gg6cC3rWyeAJe.pQIeorRW5EinNfDuL+c1fA6rIVEAtGr.lIvcbxdwI6Iewoz2qyMZd9TBJEaA44d8XhIcaOR7k.vKYECafnZyUrt6fqXggLgCWj5qryIYHF3kX801+Pi8188iCJGc7EDxOsEpv.2.5CQQOlRywDzZc3zqKK5lcErWmEbhV1CtT7v6k.20cRA0WXmodlbd5anGldg4qCCIr7uubzmEFR4C+1xYb4smjKumc1owS6ysVNL8BXLR4YCFlL.UcMbhw.muw40PMphH6Q+UD9rlJa3A51yT7lJfFMUIo38YSdSKm4bSGwG9QFw+yhya8wc3JINqGlJN+P6kOcPUf0z3QtsD0g1YLMhjjweuf6YuizquOUm84KvG4IlAz6HyaFfuKf.lNKL8i.8u1aZbcCw6aWmqc6jeLNUNwHTh8oHFieIn6ZuQqVP2pj.bF6MO3Syy9PhF8p8NTshCmCr2se2FvnItv2anB7qU.MXyFU0rtBtFQfFLgmYweA+hYVEWaEyr5.ljtTWk7ctQs9v2Z51FJPLILuKWA3nLr1o5f1bI3bWtG+cttYM0XJV6lp3iuoJt3MUwmbSU7o2TEe1MUwme0JhuL4J80xtQkMDxN02v7MHKqMDT3Dn4zJ4uA3bJKSD

It creates and destroys the child panels dynamically from the buttons:
Screen Recording 2025-03-04 at 3.41.25 PM.gif

The child panels are not saved in the component list and will not be remembered on compile,
so I created a method of restoring the panels by using persistent data in another panel.
At this point it just recreates the amount of panels that were there last time, but I would like to be able to recall and restore more complex data from the panels.
A drawback here is that the child panels do not accept "Component.setPropertiesFromJSON" because the child components do not have a name.

@d-healey I want to set the pitch randomly for each note, but I think I've got it 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.

b8625da2-eefd-4895-b95c-73dce3b334df-image.png

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

@VirtualVirgin said in How many times is the onControl callback supposed to be triggered on compile?:

The "Component List"?

Yea

@d-healey said in How to programmatically change table viewport component values?:

Any way to have the buttons off by default

This is possible when setting the table row data

local listData = []; for (x in data) { local obj = { CheckButton: 0, // Here I can set the button state Name: x.name }; listData.push(obj); } viewport.setTableRowData(listData);

Haha dirty indeed. But it works!

I don't know why but the mouseDownX and mouseDownY values I get when clicking on the panel are always huge. So I'm using an X that's higher than my object width to trigger that? Idk man... haha

if (event.mouseDownX > 26) { //click on panel //first click shows menu, second hides menu } if (!event.hover && !event.mouseDownX) { //click off of panel that also hides menu }

@CatABC this looks about right....

@d-healey I seeeee! I'll start doing it like this. I've been using if statements alot because im comfortable but I can see that I may be complicating things in some situations. Thanks Dave.

@Chazrox its an AudioWaveform component, not using FloatingTile option to be precise.

@d-healey Done!