@Christoph-Hart said in Designing / changing hise output vst basic setting panels / elements?:

This. It's more powerful this way than a simple JSON system.

Yet, I cannot trigger any buttons on the plugin´s "Install Samples" using the if(obj.text == "Install Samples") inside the laf.registerFunction("drawToggleButton", function(g, obj)function. Is that considered a drawDialogButton ?

This one:

Screen Shot 2020-11-16 at 23.49.12.png
Here I would like to:

customize the look and line-breaks of the text line and also remove/hide the "install samples" button and customize the positioning of "Choose Samples folder". is the text in the image accessible? Is it a panel or an alert window? or alternatively entirely remove/suppress the entire panel with a flag in HISE settings, the HISE_SAMPLE_DIALOG_SHOW_...=0 and then put the "Choose samples location" in my own settings panel on the UI. Is that possible? Or is that C++?

@dejans @Christoph-Hart i have similiar issue on mac

❌ Undefined symbols for architecture x86_64 > Symbol: hise::FrontendHandler::getExpansionKey() > Referenced from: hise::CustomKeyboard::setUseCustomGraphics(bool) in lto.o ❌ ld: symbol(s) not found for architecture x86_64 ❌ clang: error: linker command failed with exit code 1 (use -v to see invocation) ** BUILD FAILED **

My Hise also colse itself with this errors

Thread 0 Crashed:: JUCE Message Thread Dispatch queue: com.apple.main-thread 0 com.hartinstruments.HISEStandalone 0x000000010f72c708 juce::CodeEditorComponent::paint(juce::Graphics&) + 840 1 com.hartinstruments.HISEStandalone 0x000000010f6c5392 juce::Component::paintComponentAndChildren(juce::Graphics&) + 210 2 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 3 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 4 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 5 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 6 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 7 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 8 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 9 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 10 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 11 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 12 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 13 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 14 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 15 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 16 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 17 com.hartinstruments.HISEStandalone 0x000000010f6c5791 juce::Component::paintComponentAndChildren(juce::Graphics&) + 1233 18 com.hartinstruments.HISEStandalone 0x000000010f6d5983 juce::ComponentPeer::handlePaint(juce::LowLevelGraphicsContext&) + 323 19 com.hartinstruments.HISEStandalone 0x000000010f6cf2f2 juce::JuceNSViewClass::drawRect(objc_object*, objc_selector*, CGRect) + 498

@Christoph-Hart

Okay, so var it is.

@Christoph-Hart you were right about the scale factor. 0.5 looked a lot sharper!
One last issue... I've notice that chaning the 'scale' for images on HISE does not appear to make any difference to their size on the UI. It's fine for filmstrips but not for images.

Changing the scale to 0.5 (as shown in the screenshot below) does not affect the size of the related image.
The only way to change the size is to use the image resizer using a mouse.

alt text

@lalalandsynth cool, i will give it a try. Thnx!

I think i fixed it.

Paste this in terminal

defaults write com.apple.dt.Xcode DVTDisableMainThreadChecker 1

You can really easily draw text to a panel. Can't you just pull in a file and print whatever text you retrieve to a panel or multiple panels?

@lalalandsynth great thanks for that - 👍

--was actually hoping for a way to the scriptnode compressor reduction values...

Can't be done without C++ and vodka, give up now.

@D-Williams23

Where should I start let's say if I want to get the drag & drop functionality?

Learn JUCE.

Yes it's successful now thank you! @Christoph-Hart

Still having this issue, if I make a parameter in the Scriptnode Synth it just doesn't appear, can't reference it in a script or connect it to a slider. Same exact code works for ScriptFX. 😞

@Christoph-Hart Cheers, I'll look into the gain staging and see if it helps.
Thanks

Screen Shot 2020-11-10 at 10.50.44 AM.png

Looks fine to me I think 🤔

@Christoph-Hart

It's definitely a weird one. I'll have to ask him how he saved them and see if he can re make them.

I have 5 other people also making folders at the moment but they didn't send theirs yet so I wanted to check first so every body didn't do the same thing.

I'll report back when I find out whats happened...

Finally fixed it! Turned out (as it normally is..) to be a very easy fix. Hise didn't like having the source code on an external HDD. All is good now, thanks to all that helped.

I mean that the build directory is different. Plugins are built in Binaries/Builds/MacOSX/build/<config> while apps go into Binaries/Compiled

In the WWDC, Apple declared that to get the software to run on Apple Silicon (new ARM cpu based systems), developers will need to recompile their existing Intel-based source code for the new architecture. However in short term, of course there will be a transition from intel to arm cpus.

You should read this article: https://www.pro-tools-expert.com/production-expert-1/2020/6/25/apple-silicon-a-developer-helps-to-unpack-what-we-know

By the way, Apple announced an ARM based Mac Mini for developers a couple of months ago (Developer Transition Kit). So the developers can test their software on the new system from now. It has beta versions of macOS Big Sur and XCode.

https://www.theverge.com/2020/6/22/21299275/apple-mac-mini-developer-transition-kit-silicon-chip-wwdc-2020#:~:text=The mini will run on,launch starting later this year.