Table Curve Scrolling is Broken

[Casey Kolb]

Hi all – I'm fully updated on the new_layout branch and noticed that mouse scrolling no longer works on Table components. Normally, it changes the curve of the segment when you scroll on the table. Is this a setting somewhere or did this just get busted somewhere in a commit?

On another note, last year we added a custom callback to HISE for when a user interacts with a table component, but tables have been completely refactored in the newer branches, so we're not sure how to add this back.

@Christoph-Hart Could you possibly fix the curve scrolling and add a setTableValueChangedFunction() which is called whenever a user adds a point, moves a point, or changes the curve on a table? It was a pretty easy add for us before, but with the refactored table C++, it's a little confusing. Thanks!

[d.healey]

Scrolling was replaced with right-click and drag.

[Casey Kolb]

@d-healey Funky! Ok, got it. That's working. Just need that callback function now :)

[Christoph Hart]

Do you need to distinguish between point add / remove / drag or do you just want to update stuff whenever something changed?

[Casey Kolb]

@Christoph-Hart Just whenever something has changed. I think distinguishing between add, remove, and drag might be overkill.

[Casey Kolb]

@Casey-Kolb said in Table Curve Scrolling is Broken:

@Christoph-Hart Just whenever something has changed. I think distinguishing between add, remove, and drag might be overkill.

Oh shoot, also just realizing we had added getNumPoints() getPointX(index) getPointY(index) and getPointCurve(index) so that we can analyze the table data. Maybe that's already possible? Not sure if we need to add those back now too. That's how we draw the orbits from the table though and convert them into a format for the orbit system.

[d.healey]

@Casey-Kolb said in Table Curve Scrolling is Broken:

I think distinguishing between add, remove, and drag might be overkill.

I think it could be useful.

getNumPoints() getPointX(index) getPointY(index) and getPointCurve(index)

These sound very useful too, especially the getNumPoints() I remember someone asking for this before.