@Christoph-Hart Network bookmarks are not working. All it does is showing the whole graph unfolded with minimum zoom.

Also, it would be nice to:

• Be able to recall not just the folded state but the viewport position as well. In short, the exact thing that was displayed when creating the bookmark
• Have a keyboard shortcut with numpad combination
• Have the sliders in the Parameter section of the Node List showing the values. And have the Node List to be resizable for improved slider precision. They are good allies, but they could be better.

Navigating the graphs can be cumbersome by nature even on wide comfortable monitors. I think that making the experience better is not to be taken lightly seeing the time one can spend in there

@duma The console is telling you (partly) why and where your code as issues

@duma I could just send the snippet corrected. But I feel like you might better understand the 2 little things yourself because you'll learn better this way.
I am not trying to get rude, but I gave you the solutions already:

@ustk said in xy pad help with modulator:

• NUM_TABS is 3 but you only have two panels

this means you need to set it to 2, not 3

@ustk said in xy pad help with modulator:

this should take an array as parameter as in this example:

g.fillEllipse([0, 0, SIZE, SIZE]); // <- 4 values in one array parameter instead of 4 separate values

this you can just copy paste, and your code should compile. If not, we'll see what you have then.

@duma patience... patience... if no-one is answering, maybe we are sleeping, eating a cake, or just working on our projects...

@duma as said above:

• this should take an array as parameter as in this example:

g.fillEllipse([0, 0, SIZE, SIZE]); // <- 4 values in one array parameter instead of 4 separate values

• NUM_TABS is 3 but you only have two panels

• not critical, but you might consider using radioGroup buttons instead of a knob for switching your tabs

• your code can gain being a bit more tidy, goods habit are paying on the long run

@d-healey Definitely... 've been caught by the same 2 days ago...

@duma Hi!

@duma Export -> Export as Hise snippet

Then paste here in between code tags (6th icon from the left)

@duma said in xy pad help with modulator:

g.fillEllipse(0, 0, SIZE, SIZE);

this should take an array as parameter:

g.fillEllipse([0, 0, SIZE, SIZE]); // <- one array parameter instead of 4 values

@duma Local misses the 'a'. And since you don't use this variable yet, comment out the line just to try if your panel reappears

@duma typo

-> getLocalBounds(0)

@pcs800 a label is the only ready made component to input text.
If you need an advanced widget you’d have to build it yourself I’m afraid
Definitely not an easy task but definitely doable with a panel and a keypress callback

@ulrik that one is quite a network!
There might have been a way to place all those in a C++ node with hardcoded arrays

In the end it was just a parameter type issue, this function accepting var type only (unlike when sending data from the UI)
So whatever you want to pass in, you first need to perform a type conversion.

@Papours You might also need to set the search path for src in your VS project so it knows where to look for dependencies. I know it's the case in XCode but I don't know VS...

@Papours would it make a difference if you use

#include <test_filter.h>

in the cpp instead of

#include "test_filter.h"

@Christoph-Hart This is still unsolved, I really need it to send data back to ui script

I don't understand because both sendDataToGlobalCable and setGlobalCableValue are existing in the global_cable_cpp_manager

By the way, is it allowed to send a juce::path as data so it lightens the UI script instead of building the path there?

@Orvillain nice! Do you stick it on release as well?
EDIT: getting a compilation error for release because of the snippet browser.

And now my assertions are working as well which is what I needed in the end

For the records if someone gets there, the scheme was set to hise debug but with a release build...

@griffinboy Thanks
In the end I've made a mistake, mixing a release build with a debug executable...
So I can get DBG to work