JS serialization is confounding, also ref/val confusion

[schwa]

I notice almost none of the included JS effects ever save state beyond the slider settings. I can't figure out how to get presets to work at all for state information beyond the UI.

Here's a simple test effect that sets a single state variable. Set state, save it, hide it, then save the preset. Clear state and load the preset ... no state gets loaded. Why not?

Another very confusing thing is that if the comment is removed [in the (slider2 == 3) block] the state doesn't even get set -- x doesn't persist outside of that block. I think this means that within that block at least, x is just a reference to slider1. Is there a way to valuify x inside that block? Confusing!

Are these two weirdnesses related?

////
desc:serialization test

slider1:0<0,10,1>x
slider2:0<0,5,1{-,show state,hide state,save state,clear state}>action

@init

x = 0;

@serialize

file_var(0, x);

@slider

(slider2 == 1) ? (
slider1 = x;
slider2 = 0;
);

(slider2 == 2) ? (
slider1 = 0;
slider2 = 0;
);

(slider2 == 3) ? (
x = slider1;
// slider1 = 0;
slider2 = 0;
);

(slider2 == 4) ? (
x = 0;
slider1 = 0;
slider2 = 0;
);

[schwa]

Another thing -- the preset file size does not appear to depend on how much stuff gets serialized. Pretty much my @serialize code is just not getting called. Most likely I will hit myself in the head when somebody shows me what I'm misunderstanding.

[Justin]

unfortunately @serialize only currently works when saving/loading internal JS presets in the JS effect list or JS standalone (i.e. using S/L in its window)..

At some point in the REAPER 2.x series we will fix this...

-Justin

[schwa]

Thanks for the info. I added this to the Reaper JS wiki page http://www.cockos.com/wiki/index.php..._Documentation to save the next guy some cranial bruising.

[brainwreck]

bummer :^P

thanks again for the effort schwa.