I guess maybe I should use Programaticaly rather than dynamically. The entire issue lies in the change event. If I rely on it then I end up in a continous loop or rather just a loop, meaning if I change the Vscale via my component by scaling it, I have to change the Vslider.value, which ends up throwing the "change" event, which tells my component to update. So each side is stepping on the toes of each other overwriting the changes when scaling on component side nothing happens when I try to scale as Vslider keeps setting the value back.
My work around for now is to not update the slider until the component zoom is done. Had to give up realtime update to the Vslider. Vslider is updated now only on mouseup not on mousemove. --- In flexcoders@yahoogroups.com, "flexaustin" <flexaus...@...> wrote: > > I seem to be having issues altering the vslider via code. I am using > the change event thrown by the Vslider to dispatch my own event like so > > this.dispatchEvent( event ); > > So anytime someone changes the Vslider value it throws an event and my > components scales in size. > > But my component has the ability to change its own size using mouse + > keyboard controls. So when this happens I then need to tell the > Vslider to change its value to match the components new size. So I do > that via function like so > > mySlider.value = newVal; > > This seems to work nine times out of ten, but if my Vslider is a 4.5 > (my Vslider can go btwn .25 and 5) then I scale the component to 5 > then click on the Vslider to scale down to .25 the change event isn't > ever thrown via the Vslider though the slider thumb moves to where I > clicked on the Vslider. >
