General
what is the propagation scope of aliases ...?
Started by julien on .
Sign in or create an account to join the conversation.
Hi there,
as there is no documentation about aliases, I don't really know about their scope.
I created a slider in a container in page 1, and I created an alias of this slider in another page 2.
It seems the value propagation doesn't work
Any ideas? infos ? docs ...?
as there is no documentation about aliases, I don't really know about their scope.
I created a slider in a container in page 1, and I created an alias of this slider in another page 2.
It seems the value propagation doesn't work
Any ideas? infos ? docs ...?
Hmmm weird! Thats the purpose of it actually - that they behave identically.....
Softcore wrote:Hmmm weird! Thats the purpose of it actually - that they behave identically.....
and it doesn't.
maybe I missed something to do, but without docs .. :p
Well actually there is no tmuch to miss....Say, you got a fader, you create an alias of it...then when you touch any of the two, the other one will follow...
Are you testing on the desktop editor or on the actual iPad Lemur (the desktop editor from times to times, fails to update the screen correctly)
Are you testing on the desktop editor or on the actual iPad Lemur (the desktop editor from times to times, fails to update the screen correctly)
Ok just tried our of curiosity (thinking that maybe something broke in an update)....
Windows PC - desktop editor
Blank project -> insert fader -> create alias for the fader -> enter "live mode" (press "E" key for Windows) -> move one fader with the mouse -> the other one follows....
also ....resize one fader -> the other one is resized too
Not what you are getting?
Windows PC - desktop editor
Blank project -> insert fader -> create alias for the fader -> enter "live mode" (press "E" key for Windows) -> move one fader with the mouse -> the other one follows....
also ....resize one fader -> the other one is resized too
Not what you are getting?
Are you looking for something along the lines of an OOP based programming object? That is to say you create a container full of elements that interact with one another and wish to use this as a template to reproduce more objects of the same type? I think this is what modules are for.
If you want to make 2 objects that function exactly the same (communicate with the same variables etc), but have them look diffrent, you will need to code each one individually (or copy and paste), and be sure to update additions in scripts and so forth manually between the two. (Royal pain in the ass, I know)...
If you're into some really heavy stuff, you can keep all of the logic in a hidden container and just link to it via getexpression and setexpression from the actual visible objects (faders etc)...
If you want to make 2 objects that function exactly the same (communicate with the same variables etc), but have them look diffrent, you will need to code each one individually (or copy and paste), and be sure to update additions in scripts and so forth manually between the two. (Royal pain in the ass, I know)...
If you're into some really heavy stuff, you can keep all of the logic in a hidden container and just link to it via getexpression and setexpression from the actual visible objects (faders etc)...