Where can I find Laf functions?
-
is there a place where the Laf functions are written out?
I'm not sure how to trace them.My autocomplete for these has been broken for quite a while, and I have no idea what all the
.registerFunctionThingies are called!
eg: waveformLAF.registerFunction("drawThumbnailPath") -
@griffinboy Yep, there's an array in this file: /hi_scripting/scripting/api/ScriptingGraphics.cpp
It's on line ~2510 so I just open it up and search for one I remember!
-
-
G griffinboy marked this topic as a question on
-
G griffinboy has marked this topic as solved on
-
Thanks!
Sorry for my heavy use of the forum of late -
@griffinboy why are you sorry?
-
Lots of people are making posts, I don't want to accidently bury other peoples questions
I know that you guys are happy to help, and I appreciate it.
But I've always felt that the best way is to attack a problem fully to the extent of my ability before asking for help. -
@griffinboy Well it happens, I always look through the forum, the docs, the github docs (way better search than on the docs page) and google with the site: hise forum target, but even then sometimes I'll ask something and David or someone else will pop by and drop a link to the docs.
If every post you made was asking about something that can be easily found in the docs, then I'm sure eventually someone would make a comment about that.
But generally, you're fine. I understand it can be an anxiety thing, I have close people who have dealt with similar stuff all their life, and while it can never go away, it does get easier when you remind yourself of the reasonable take on the whole thing. Which, granted, someone often has to give you first, so in case that's what's up, here's mine.
If you, for just a moment, disregard the whole gift-to-humanity FOSS side of the entire project and look at it from the business side, your posts are good data. You yourself are just one data point, but if everyone else started asking repetitive questions, that could indicate a documentation or some other problem.
You can see this, for example, in the introduction of the export pre-flight checklist that happened a few weeks ago. If you go through the forum, at one point a couple of months ago you'll see a lot of similar posts started appearing on a nearly daily basis: compilation fails, export fails, and most of them caused by the users not actually reading the very first readme right on the github page.
Someone made a video about plugin creation with HISE on youtube, it got some traffic and HISE got an influx of new users. A lot of them just went to the hise.dev webpage, downloaded the binary and attempted to VCR through the whole thing by putting together something in the WYSIWYG editor and clicking export. When it didn't work, the first thing they did was come to the forum.
This gives you a lot of clues about how curious hobbyists think and work, and if your business decision is that there's still potential future developers there (or you're just annoyed with the daily export error posts), you now have data to work off of and make changes.
It's a good deal. Chris provides a place to talk, in return he gets QA and customer support.
You're asking good questions. The talk we had about the dynamic continuous event modulation yesterday was a good talk. These are new features in HISE, and it's good to test the general audience's understanding of these by bringing it up, which, as you saw in my snippet, requires a decent understanding of HISE in order to implement properly. People will surely benefit from it. If even one person does, it's worth it. I am where I am in life because of selfless contributions of countless people of many forums and those who created, maintained and moderated them, allowing me to search, browse and read days, months or years after these talks took place and benefit from the information.
Even this topic, silly as it may seem in hindsight, is framed very well and is a very SEO friendly question. A few weeks from now, whether someone attempts to search it here, search it on google, or it gets swallowed by some LLM and someone asks there, i'll easily be the thing that comes up first.
So your questions are good. You're not being a jerk, you're not forcing political themes or sexualizing other forum members. You're talking about HISE and instrument development practices and workflows. It's all on topic, and you're even actively contributing, like with the C++ tutorial. So all's good. Keep talking, that's what the forum is for.
-
Thanks for your thoughts : )
