Bug #322

@priority attribute does not seem to prioritize in order

Added by Ricardo del Pozo over 2 years ago. Updated over 2 years ago.

Status:Closed Start date:2009-09-21
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:- Spent time: -
Target version:0.5
Branch: OS:

Description

Using the "@priority" attribute does not seem to initialize the module in prioritized sequence.

History

Updated by Pascal Baltazar over 2 years ago

could you please be more precise ?
when does that happen ?
presets ? cueScript/cueManager ? using "get current state as text"
thanks

Updated by Ricardo del Pozo over 2 years ago

It happens when you load the module, or initialize the patch. If you get current state as text, you still get it in alphabetical order and not in prioritized order as specified as an attribute in the jcom.parameter object.

More helpful?

Updated by Pascal Baltazar over 2 years ago

just to make it clear, do you mean that initialization is or is not performed in the priority order ?
if you choose is not, then did you update your preset file ?

Updated by Ricardo del Pozo over 2 years ago

It is not, and yes I did update the preset file.

Updated by Pascal Baltazar over 2 years ago

well... I'm surprised !
it works here...
here's what I get when initializing jmod.mapperContinuous, which is definitely not by alphabetical order... and corresponds to the priority order

as shown below :

dumped from the module at init :

print: /in/module/derivative 0
print: /in/module/name /input
print: /mode 0
print: /in/module/instance 0
print: /function linear
print: /function/symmetry 0
print: /out/module/name /input
print: /function/parameter2 0.
print: /out/module/instance 0
print: /function/parameter1 0.
print: /out/module/parameter /audio/gain
print: /in/module/parameter /audio/amplitude.1
print: /clipmode both
print: /edit edit
print: /in/direct 0.
print: /in/max 1.
print: /in/min 0.
print: /in/module/derivative 0
print: /in/module/listindex 1
print: /out/max 127.
print: /out/min 0.
print: /ramp 20
print: /slide/down 0.
print: /slide/up 0.
print: /view/color/border 0.62 0. 0.36 1.
print: /view/color/contentBackground 0
print: /view/color/toolbarBackground 0
print: /view/color/toolbarText 0
print: /view/freeze 0
print: /view/size 600 70

retrieved in jmod.cueManager
/mapper.2/in/module/name /input
/mapper.2/mode 0
/mapper.2/in/module/instance 0
/mapper.2/function linear
/mapper.2/function/symmetry 0
/mapper.2/out/module/name /input
/mapper.2/function/parameter2 0.000000
/mapper.2/out/module/instance 0
/mapper.2/function/parameter1 0.000000
/mapper.2/out/module/parameter /audio/gain
/mapper.2/in/module/parameter /audio/amplitude.1
/mapper.2/clipmode both
/mapper.2/edit edit
/mapper.2/in/direct 0
/mapper.2/in/max 1.000000
/mapper.2/in/min 0.000000
/mapper.2/in/module/derivative 0
/mapper.2/in/module/listindex 1
/mapper.2/out/max 127.000000
/mapper.2/out/min 0.000000
/mapper.2/ramp 20
/mapper.2/slide/down 0.000000
/mapper.2/slide/up 0.000000
/mapper.2/view/color/border 0.620000 0.000000 0.360000 1.000000
/mapper.2/view/color/contentBackground 0
/mapper.2/view/color/toolbarBackground 0
/mapper.2/view/color/toolbarText 0
/mapper.2/view/freeze 0
/mapper.2/view/size 600 70

Updated by Pascal Baltazar over 2 years ago

could you please send me/us your patch ?
so I/we can try to figure out what's wrong....

Updated by Ricardo del Pozo over 2 years ago

It seems that I'v been wrong and that it works fine now. So sorry for the misunderstanding.

Updated by Pascal Baltazar over 2 years ago

  • Status changed from New to Closed

as reported in Richardo's last comment, this bug is closed

Also available in: Atom PDF