-
Notifications
You must be signed in to change notification settings - Fork 51
ControlSpecs are written to the global ControlSpec namespace #125
Comments
Hey buddy. I'm out of action for a few weeks getting a project out of the door. Feel free to tweak how you wish. I just copied these controlspec lines from another one of the default lua scripts. I dont fully understand what they are doing, so if you know better, go for it. |
I think Line 80 in 48a8618
|
@markwheeler ah, thanks. the ControlSpec ”globals” or ”class variables” are probably completely undocumented (this is stuff brought over 1:1 from SC). might need to rethink this a bit. |
partly related to monome/norns#425 |
@pq re: monome/norns#436 does ControlSpec global get restored to its default state with this method? |
late to the party; sorry!
as per our conversation over on monome/norns#559, nope. we'll need to restore it specially (maybe in |
in |
@tehn (you probably already get this, but, to clarify) the underlying problem is it's not a copy but the controlspec table that is used and overwritten (ie. |
I suggest to put the script specific controlspecs used in
kayan
(EDIT: and other scripts) in a script specific table rather than the core ControlSpec table.Ie. see this line:
dust/scripts/burn/kayan.lua
Line 55 in 48a8618
I've not tested this in practice but am quite sure that line changes the standard ControlSpec.AMP for any script using that default controlspec loaded after
kayan
.The text was updated successfully, but these errors were encountered: