jivory

I found one method. In my component, outside the TransformManager that will edit the TransformItems, if the objects in there receive a mouse event, I simply $e.stopImmediatePropagation(); and $e.preventDefault(); which prevents the TransformManager from deselecting the items. If anyone has any other (better) suggestions I'd love to hear them! Thanks

Hey guys, I have the TransformManager in an application, that will edit text fields. My idea, is to have text, selectable by the TransformManager. Then within another component, alter the text object, with a font drop down, colors, text, etc. My issue I'm seeing, is once the text TransformItem is selected, then any other item clicked on, it deselects the text TransformItem. Does anyone have any thoughts or ideas how I would accomplish this? I've thought, I could store the item in an object, and just make the edits, and they could change the text, without the text TransformItem actually being selected, which is fine, it doesn't necessarily need to be selected the whole time, I just need a pointer so it knows what item to change. The visual problem with this, is the handles are removed from the item, showing it is no longer selected, so it could be confusing on which item is being altered. Any suggestion on how I might either keep the item selected with the TransformManager, while clicking other items and not deselecting the item, or show that the item is still 'selected' even when the TransformManager releases it? Thanks

I've noticed this same thing. At first I thought it was something with our app and the TransformManager, but then I noticed it on Yahoo's financial page as well, doing the same thing. The cursor moves oddly and seems to ease. It's definitely something to do with Flash Player / browser, as I've seen it in other places as well. I've only noticed it in Chrome, as FF has never shown me this issue.

Perfect, just like it's intended! Thanks again for an awesome product and great support on these issues! Always appreciated.

I couldn't see how to attach the project, but here's the MXML of a simple project I just made. <?xml version="1.0" encoding="utf-8"?> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600" creationComplete="complete()"> <fx:Declarations> <!-- Place non-visual elements (e.g., services, value objects) here --> </fx:Declarations> <fx:Script> <![CDATA[ import com.greensock.transform.FlexTransformManager [Embed(source="blacky.png")] [bindable] private var img:Class; private var tm:FlexTransformManager; private function complete():void{ tm = new FlexTransformManager(); tm.width = 500; tm.height = 500; tm.bounds = new Rectangle(-2000,-2000,6000,6000); tm.addItem(myImg); addElement(tm); } ]]> </fx:Script> <s:Image id="myImg" width="100" height="100" source="{img}"/> </s:Application> As you can see, the FlexTransformManager is set to 500x500, but the bounds are way beyond that. Which would allow the TransformItems to be scaled and moved offscreen outside this 500x500 area, but it remains constrained within. And just to confirm: FlexTransformManager - VERSION: 1.9663 TransformItem - VERSION: 1.9667 TransformManager - VERSION: 1.9668 Just to make sure I'm using the most recent versions Thanks!

I downloaded the latest version, but it still has the same behavior of constraining to the parent's size and not the bounds given. I notice the FlexTransformManager.as has a modified date of 9/15 but the version still says VERSION: 1.9663 as well, so maybe it's not updated?

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,

If that's the case, I figure out another way to accomplish what I need. Thanks

Hey everyone, I am wanting to create a duplicate of the FlexTransformManager that I already have. Have it include all the same objects, size, rotation, etc. That way I can then work with that transformer independently without modifying the original. I tried: var transformerDuplicate:FlexTransformManager = new FlexTransformManager(); transformerDuplicate = myTransformer; addChild(transformerDuplicate); and all this seems to do it overwrite the original transformer. Does anyone know how I can create a duplicate, add it to my stage and be able to work with it from there? Thanks

Very good! Updated to 1.952 and the issue is fixed. We assumed it was some rounding issues in Flash (which we've seen before). Great work fixing it, and always appreciative of the quick and responsive support! Thanks again for such a great tool that is vital to our application.

Attached is a simple FLA I put together, sorry for the confusing description of how to recreate the issue Anyway, we updated to 1.95 this morning and the issue remains so I made this. I have a SCALE event tracing out the rotation, scaleX, and scaleY. When you rotate the image to 90 deg, the scaleY gets flipped to negative. If you carefully rotate to 89 deg, or even 91 deg the values output positive and expected, but right at 90 deg, the issue occurs. You'll notice the image stays the same, which is why it's difficult to notice an issue until you trace out the values and use them later (which we are doing for an output) and therefor our image come out flipped on the horizontal axis. We are adding the TransformEvent.SCALE to the TransformItem. Is this correct or should it be on the TransformManager instead? Just making sure we're putting it together correctly and could be a cause of the issue I also put together a quick Flex example and tested and the outcome is the same. We are using the TransformManager within a Flex application, and so I built this example in Flash to make sure the issue existed in both environments. Any help or advice will be greatly appreciated. Thanks

Hey all, We're using the TransformManager v 1.921. We've been using it in an application for almost a year now, and just barely noticed an issue. We have an image, rotate it 90 deg and begin scaling down on the vertical axis (original horizontal scaleX). It doesn't happen every time, but when we scale it down a bit, almost to 0 sometimes, and then reverse and scale it back up, it flips the horizontal scale value to negative (original vertical scaleY). We trace out the rotation, width, height, scaleX, and scaleY and that's how we notice it change. The image inside the TransformItem stays the same however. So visually to the user, the image stays the same. We are outputting the values and image in a final product from this, and since the value has changed, the image in the final output is flipped mirrored. We're not sure how many people read the values or even use those values for something later, so we're hopeful someone has noticed this issue and how to resolve it and that it is not just us. Thanks

Ah nice, thanks again

That works. Tracing the items toargetObject instead gives me the full rotation. Not sure why the item itself is throwing different values, but that solves my issue, thanks

I'm having an issue with rotation values the flex transform manager is giving me. I add an item to the manager, and in a TransformEvent.ROTATE event, I'm tracing out the item's rotation, $e.items[0].rotation. When the object has a positive scale on both x and y, it gives me a full 360 degree value. 0 -- 90/91 -- 180/-180 -- -90/-89 -- 0. 0 to 180 and back to 0. If I scale the item negative, either x or y, then rotate it gives me different rotation values. 0 -- 90/-90 -- 0/-1 -- -90/-89 -- 0. 0 to 90, to 0, to 90, then back to 0. So it says 0 and 180 degrees are both 0. Is this correct? The object rotates great, but the values it's telling me don't seem right. I built an HSlider to help rotate the object and it is giving me wrong values so the slider does not work properly. Anyone seen this issue or how to resolve it? Thanks