locoDog
Just noticed a new [?] thing
...deck="mixer2"
I like it, I understand the purpose.
Is there anything else new like this in 2026?
It's a bit of an odd one, it is script but it isn't an action, it's mostly made for skins in a HW tied kind of way but it's not an element.
I know there doesn't need to be a song and dance about a deck specifier but the briefest of mentions would help, I just happened to be poking round default:pro and realised this was something new.
...deck="mixer2"
I like it, I understand the purpose.
Is there anything else new like this in 2026?
It's a bit of an odd one, it is script but it isn't an action, it's mostly made for skins in a HW tied kind of way but it's not an element.
I know there doesn't need to be a song and dance about a deck specifier but the briefest of mentions would help, I just happened to be poking round default:pro and realised this was something new.
geposted 11 hours ago
PhantomDeejay
I don't think it's that new TBH.
It's just an internal shortcut to the deck that's currently assigned at the second mixer channel.
It just looks at mixer_order (1234 or 3124) and reports the correct deck.
I may be wrong, but I think it has been in existence for quite some time
It's just an internal shortcut to the deck that's currently assigned at the second mixer channel.
It just looks at mixer_order (1234 or 3124) and reports the correct deck.
I may be wrong, but I think it has been in existence for quite some time
geposted 10 hours ago
locoDog
Ah quite some time..., just shows how 'out of date' my forever WIP skin is XD
I'm just refactoring default:pro to; possibly do future me a favour/learn something/be a bit less useless skinning, so I guess this is my 'catch up' course.
I'm trying to make a wave resize edit a shorter job [favour to future me], plus leaning lightly into define inheritance - see how much I can strip out while still keeping it readable. [hopefully more readable]
If I don't get bored, I might even comment it up.
A question springs to mind, can I define a constant to use globally? It's hard to think up a simple example, maybe... an x position
I guess I could make the whole skin a define and have my const as a placeholder, but that's kind of the reverse of how I'm thinking, maybe whole skin in a panel...
I get the feeling I don't quite get placeholders, I get passing values up from placement to define, even passing thru several defines and I get doing maths on placeholders in the define but maybe there's more to them.
I'm just refactoring default:pro to; possibly do future me a favour/learn something/be a bit less useless skinning, so I guess this is my 'catch up' course.
I'm trying to make a wave resize edit a shorter job [favour to future me], plus leaning lightly into define inheritance - see how much I can strip out while still keeping it readable. [hopefully more readable]
If I don't get bored, I might even comment it up.
A question springs to mind, can I define a constant to use globally? It's hard to think up a simple example, maybe... an x position
I guess I could make the whole skin a define and have my const as a placeholder, but that's kind of the reverse of how I'm thinking, maybe whole skin in a panel...
I get the feeling I don't quite get placeholders, I get passing values up from placement to define, even passing thru several defines and I get doing maths on placeholders in the define but maybe there's more to them.
geposted 9 hours ago