Attribute priority

[Pookay]

@theod
I've some problems with the attribute priority when i save parameters with a j.cue. It doesn't save in order i want. Thats the order of saving, and after the : it's the priority i gave to the parameter. Maybe i do it wrong but i don't understand the logic.

reverse : 11
speed : 15
start : 21
end : 22
fade.in : 23
/pow : 42
fade.out : 24
/pow : 43
fade/enable : 14 (in a subpatch)
loop
/enable : 12
/link : 13 (in a subpatch)
/start : 31
/end : 32
xfade
/enable : 33
/time : 34
file (in a subpatch)
/path : 1
/number : 2
/name :3

[theod]

yes this is a known bug described here : #388
it is relative to a feature request for a new external called [j.node] to be able to set the priority of a node that doesn't handle any parameter (e.g. the file node).

[bltzr]

as this one duplicates #388, I'm closing it