I am looking for a way to link an expression rigged layer to a null and keeping it’s absolute values so there won’t be a shift when I parent it to a null.
this is what’s happening:
this is the beginning of a bar chart template I am creating.
the bar has this expression:
t1 = key(1).time;
t2 = key(2).time;
v1 = 1413;
v2 = linear(effect(“Slider Control”)(“Slider”),100,0,1413,885);
it’s set on the Y position. now I can change the slider and the animation will act according to 0-100. I want to duplicate this bar and spread them on the X axis. it will be with other layers so I need to parent them so I can move them together. when I do, unless my Null is set to the exact same value as the Bar, there will be a shift. I can either set my null to 0, or parent it and then set it manually back into place. I am looking for something more elegant. to parent it with the right code and not have it to offset.
what’s the magic combination here please? I can’t seem to make toworld work here.
it seems that offseting the shape layer group position in space 260 pixels “fixes” it and now parent and unparent has no shift. still can’t make sense of it because I was thinking default location should produce the most neutral state. maybe it because the shape start position is outside the comps dimensions?
Hi, What do you think? Is there a way to avoid this jump due to relative coordinates? I can’t find a related thread about it and to/from World goes over my head… maybe if I see the code, I can understand the principle like with some more complex expressions ideas.
[Roei Tzoref]“Hi, What do you think? Is there a way to avoid this jump due to relative coordinates? I can’t find a related thread about it and to/from World goes over my head… maybe if I see the code, I can understand the principle like with some more complex expressions ideas.”
Let’s step back to the beginning. You seem to want a mix of absolute and relative positioning. Why?
When I build bar charts, I go all-out and control just about everything with expressions. Here’s a very simple example of the kind of approach I usually take:
Thanks Walter. I will study this rig. in a first impression it looks quite robust and not that simple.
I guess I want to “fix” things in more straightforward manner (in my eyes) if that’s at all possible. take a look at just a simple example, is there a code that can overcome it? or do you have to build your rig in advanced knowing this limitation cannot be fixed in a straightforward way (or you could also so say “the way I want it to work”)