help?

[Layzer2]

if you got a moment atom or dasfaker.

i cant seem to get the tab switching to work,

can you look over the demo – tabs.panel code and see whats wrong?

i stripped all the layer stuff out of the demo… just to make it easier to work with.

then upload a working version so i can learn.

thanks!

btw, the tabs dont switch even in the unmodified demo tab and layers file…
i get some "expected number, got nil instead" error when it tries to load.

[atom]

Well i can’t really see anything on the attached panel (layer problems?) anyway, drop the lua path and use the modulator link path. It’s less faulty and no LUA needs to be involved, always try to solve stuff without the need to code, that’s my rule. I go to LUA only if all else fails. The combo that changes tabs uses that method, look at it’s properties.

[Layzer2]

well slap me silly….. v.787 doesnt understand uitabscurrenttab property….time to update. grrr.
shows up as ??uitabscurrenttab in the properties pane…that was my clue.

thanks again atom.

[atom]

Yeah i added that to get rid of the LUA part of tab switching.

[Layzer2]

meh… still needed lua. I have to switch multiple uitabs with one modulator. because the knobs are spread out that get shifted.
cant do it with linking cos you can only link to one uitab with one modulator.

used the example below to acomplish what i needed to with groups and LUA i found elsewhere and a bit of tweaking

[atom]

The modulator link relationship is many-to-one it can’t be one-to-many (you can link multiple modulators to the same target modulator property). If it’s something else you need then you need LUA. I was thinking about making one-to-many but haven’t figured it out how to exactly implement it.

[Author]

Posts