Jump to content
GreenSock

ptaranto

The move cursor only appears on handlers [SOLVED]

Recommended Posts

The TransformManager is working OK in my application, but the move cursor do not appear when the mouse is over on the selected item, only on the square handlers.

 

The application is in Brazilian Portuguese, but you can take a snapshot from your webcam or load a local image, then you adjust your image to crop and adjust the cropped image to fit in a face and add a mustache and a goatee. Finally you will be able to save your picture (this last part is not finish yet, but it saves the image from whole app)

 

http://www.pedrotaranto.com.br/projects ... dorizador/

 

How can I solve this problem?

Link to comment
Share on other sites

just an additional information

 

my itens are masked, but I have tried without mask but got no sucess

Link to comment
Share on other sites

It looks like you probably have something in front of the target object that is preventing a ROLL_OVER event from getting triggered. Might that be the case?

Link to comment
Share on other sites

unfortunately its not the case, I have add every object on the stage to ignore list

 

also tried to test TransformManager from the document class with no success

 

in both cases, I noticed that I have to force selection by using selectItem() method

Link to comment
Share on other sites

Adding items to the ignoredObjects list is really about preventing them from causing DESELECTION, so it doesn't actually alter the stacking order or the way MouseEvents are triggered (or not triggered) in Flash. So if you have an object over the top of the item you want to select, Flash will still prevent mouse interaction with the item below. You'd need to set mouseEnabled to false on the interfering items (that's unrelated to TransformManager). Make sense?

Link to comment
Share on other sites

OK, just noticed that I am transforming a Bitmap class that isn't a InteractiveObject, so it will never trigger the MouseEvent's

 

Don't know if is the case to restrict the addItem($targetObject:DisplayObject, ..) to addItem($targetObject:InteractiveObject, ...) or have a built in DisplayObjectContainer to handle these cases, the same problem could occur when the basics DisplayObjects (like Video, Shape, ...) are added to TransformManager.

Link to comment
Share on other sites

Or even fill the edge with alpha parameter, at least in these non interactive DisplayObjects.

Link to comment
Share on other sites

restrict the addItem($targetObject:DisplayObject, ..) to addItem($targetObject:InteractiveObject, ...)

 

I totally see your logic there, but the problem is that it would prevent use cases that should be perfectly legitimate. You're assuming that the only use for TransformManager is for user interaction based transformations, but there are customers who want to control everything through code and do some customized stuff that doesn't require the targetObjects to be InteractiveObjects. See what I mean? The down side is that occasionally folks will make the mistake you did (and sorry, it didn't even dawn on me to ask you about that), but the up side is that it's not locking developers into only being able to manage InteractiveObjects. I'll put a note in the documentation, though. Thanks for pointing it out.

Link to comment
Share on other sites

restrict the addItem($targetObject:DisplayObject, ..) to addItem($targetObject:InteractiveObject, ...)

 

I totally see your logic there, but the problem is that it would prevent use cases that should be perfectly legitimate. You're assuming that the only use for TransformManager is for user interaction based transformations, but there are customers who want to control everything through code and do some customized stuff that doesn't require the targetObjects to be InteractiveObjects. See what I mean? The down side is that occasionally folks will make the mistake you did (and sorry, it didn't even dawn on me to ask you about that), but the up side is that it's not locking developers into only being able to manage InteractiveObjects. I'll put a note in the documentation, though. Thanks for pointing it out.

 

I completely agree with you, in that same app I have both interaction and non-interaction transformations on the selected item.

 

Just added my Bitmap to a Sprite and set the frame movieclip on top of the image to mouseEnabled=false as you said and it did the trick.

 

A note in the documentation should be enough.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×