Jump to content
GreenSock

Search In
  • More options...
Find results that contain...
Find results in...

tcoz

Members
  • Posts

    9
  • Joined

  • Last visited

tcoz's Achievements

0

Reputation

  1. Looking for a tested best practice (I'm on a very tight deadline, so hacking around with untried suggestions really isn't an option) to move the currently selected item all the way to the back of the Z order in the transform manager.
  2. Looking for a tested best practice (I'm on a very tight deadline, so hacking around with untried suggestions really isn't an option) to move the currently selected item all the way to the back of the Z order in the transform manager.
  3. The client has been working heard on repro steps for this, and has narrowed it down to, "if you put an object on the board, and rotate it34x clockwise (so start rotating, never release the mouse, and rotate the object again and again), it will eventually stop rotating, and you won't be able to rotate anything else." I've tried it, and it seems he's right; if you just keep rotating an object over, and over, and over, 20+ times, sooner or later it will stop rotating. I haven't set up a test for isolation yet, but figured I'd forward on the additional data.
  4. I have this issue being reported by my client. I'm not able to repro it myself, but evidently it's one of those "only happens once in a while for no particular reason" thing. Client states that if you put multiple objects on the transform manager board, and rotate them again and again (10 times or so), eventually they seem to lose their ability to rotate. If you've ever heard anything like that, please let me know. I'll attempt to get more specifics and isolate the issue if I can, but if you've got any preliminary thoughts, please post 'em here.
  5. Unfortunately, this code doesn't fix the problem entirely. The text field wrapper that allow it to be moved/scaled (which I now assume is the third displayobject being added) gets deprecated, so you can't move/scale the text field. This however, does appear to be a usable workaround. Leave the code of the transform manager alone (though it seems there is an issue with it somewhere), and just set up your objects like this, notice that I have wrapped the TextArea in a canvas, and have used the width/height/x/y in the canvas, ommitting the x/y from the TextArea (though still keeping the width/height). When I do the below, the provided FlexTransformManagerSample now appears to work in all regards, though note that any scaling restrictions will now need to be passed to the canvas, not the TextArea.
  6. The issue appears to be that the transform manager adds a series of IUI objects apart from the request to add the text component itself. It adds a total of 3 objects; the original request, another one (which I gather you use to probably solve some scaling issues), and then a third; it is this third object that causes the debugger to balk with an index out of range error. Interestingly, when not run in debug, the app proceeds, no doubt without adding the third object; this needs to be handled evidently. Preliminarily, this code fixes it. You just check to make sure that the index is available before you add the object, if it isn't, just return null. Although I haven't gone all the way throught it, the stack must check for that null value and short circuit the operation, so the error is handled and the app can continue to run cleanly. I don't know if this will effect the app otherwise, but at this point it seems to be working. At the FlexTransformManager class, at line 255, edit the function like so: override public function addChildAt($child:DisplayObject, $index:int):DisplayObject { var mc : DisplayObject; if ( $index < super.getChildren ( ).length ) { mc = super.addChildAt($child, $index); autoAddChild($child); } return mc; }
  7. I'll keep posting my findings: I was attempting to run this in debug; for the heck of it, I ran it in non-debug, and it works as expected. This is of course is an issue; have to be able to run the app cleanly in debug. Note that this is an issue in the sample as well (imported directly without any manipulation into Flex Builder 3 using the 3.1 sdk). I'm working with the FlexTransformManager class now to see if I can fix, from what I can see though, this is likely a bug in the class.
  8. There's nothing else going on, again if I just swap the TextArea for an image, or anything else that's a standard IUIComponent, it works fine. The issue appears to be that these are not IUIComponents. I'm using Flex 3.1. This issue is pretty serious, the client provided me with the license and sort of expected it to "just work".
  9. Hey there, I'm trying to run the sample. (FYI I'm an experienced Flex dev, so I have a feeling I'll feel dumb when you answer this...) I run it, and I get this stack trace (truncated to relevant gs class). This is true of mx Text, TexArea, etc. However, other images, canvases, etc. are fine, and I can even add a textarea or text to that canvas. But I can not add a TextArea, as is, without getting the index error. I'm fully aware of the hierarchy and requirements of the display list, but this is the code from the sample, so I'm assuming it should work. Any insight? RangeError: Error #2006: The supplied index is out of bounds. at flash.display::DisplayObjectContainer/addChildAt() at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::$addChildAt()[E] at mx.core::Container/addChildAt()[E] at gs.transform::FlexTransformManager/addChildAt()[/Applications/MAMP/htdocs/workspace_flex/DessyMoodBoard/src/gs/transform/FlexTransformManager.as]
×