Search the Community
Showing results for tags 'constrain'.
Found 3 results
-
Hello, i have already asked this question in the following thread: http://forums.greensock.com/topic/6964-constrain-scaling-to-avoid-mirror-efects/ The solution was to set the minScaleX and minScaleY to 0 and that worked, but now I need to constrain the width and height of a transformItem, not the scale. So, i used the minWidth and minHeight properties of the item. At the beginning its seemed to work, however if I keep scaling beyond the min values, the item will eventually jump to negative scale values. I think its a bug but i don't know, any help will be greatly appreciated. Here a .fla that shows the problem: https://www.dropbox.com/s/wx6vtjho4vn0t9k/TransManager_MinWidthBug.fla Thank you. -
Hello, I'm doing some really cool things with the TransformManager, but once again I need some help. Is there a way to constrain scaling to positive values, so that mirror effects do not happen? To make myself clear, take a look a the images: 1. Original State - Ok Scaling: http://www.flickr.com/photos/90499524@N07/8273520758/in/photostream 2. Still Ok Scaling: http://www.flickr.com/photos/90499524@N07/8272455391/in/photostream 3. Not Ok Scaling: http://www.flickr.com/photos/90499524@N07/8273520798/in/photostream Thank you so much for your help.
-
I recently updated my Transformer files, and noticed a different behavior I don't see mentioned in the change log. I have a parent object, with the size of 100% width and height, going to the size of the user's browser. So it's around 1000x800 roughly. There are other objects (images) added within this parent, that the FlexTransformManager are added onto. We set the bounds to be (-2000,-2000,6000,6000). The reason for this is so the images can be scaled quite large, and parts of the image are allowed to be scaled and dragged 'off stage'. With the recent update (or one since 1.952), the Transformer will no allow the images to be scaled beyond the bounds of the parent object, even though the bounds are set to a larger number. Is this new intended functionality, or a way I can remove this new default feature? It seems the items are now ignoring the bounds I give them, and constraining to the size of the parent. Thanks,
