Report post Posted December 14, 2014 I am using TM v: 1.9669 (purchased by a client last week) in a Flex 4.6/AS project and am seeing some odd behavior. I've spent the day trying to fix this but have had no success. The issue is that with an item selected, the TM "move" cursor appears outside the selection bounds, and it seems like there is a ghost shape or something the same size as the selection but offset from the center which is triggering it. That's clear, right? There's an image below to show what I mean. I added the red rectangle in Photoshop to indicate the ghost area which is triggering the TM move cursor. This area is active and the selection can be moved by clicking and dragging within the red rectangle. I've built a stripped down Flex project which shows this issue and attached the exported .fxp below (without the TransformManager lib, of course). I've tried every way from Tuesday to determine if this is my bug and am not seeing it. Is this a Flex bug, a TM bug? The selected item is a Flex Spark group which loads an swf. It is pretty bare bones, so I am baffled as to where this ghost shape is coming from. I've stripped out the loader AS code below <?xml version="1.0" encoding="utf-8"?> <s:Group xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" width="5" height="5" resize="resizeHandler(event)"> <s:SWFLoader id="eventBtn" width="{this.width - 5}" height="{this.height - 5}" x="{regX}" y="{regY}" verticalAlign="middle" horizontalAlign="center" complete="btn_completeHandler(event)" /> <s:Rect id="bitmapBorder" x="{regX}" y="{regY}" width="100%" height="100%" visible="true"> <s:stroke> <s:SolidColorStroke color="#ffffff" weight="2" /> </s:stroke> </s:Rect> </s:Group> TransformManagerBug.fxp.zip Share this post Link to post Share on other sites
Report post Posted December 15, 2014 This was my bug. I've posted the solution on StackOverflow Share this post Link to post Share on other sites
Report post Posted December 15, 2014 This was my bug. I posted a solution over at StackOverflow 1 Share this post Link to post Share on other sites
Report post Posted December 16, 2014 Excellent, thanks for letting us know. Glad you got it working okay. Share this post Link to post Share on other sites