Comments on: Flex Component: PanScrollingCanvas

By: Amar

Amar — Tue, 27 Apr 2010 13:58:48 +0000

Did you got any solution for the above error. Please post the answer once you got the solution

By: Amar

Amar — Wed, 21 Apr 2010 13:24:50 +0000

Sorry to say this.. Am checking with latest versions of Safari, Chrome, and Firefox, using the latest Flash plugin. Still same error in all.
Thanks

By: didier

didier — Tue, 20 Apr 2010 19:02:13 +0000

Unfortunately, I cannot replicate the problem you are describing. Things are working fine in the latest versions of Safari, Chrome, and Firefox, using the latest Flash plugin. Not sure about IE. Maybe you can check your browser/plugin. Thanks.

By: Amar

Amar — Tue, 20 Apr 2010 17:02:18 +0000

I didn’t any change in your code. Your demo(above) have same prob. How can i correct it. Where i want to change.
Am trying this stage.addEventListener(Event.MOUSE_LEAVE, handleMouseLeave, false, 0, true); Still same prob…

By: didier

didier — Tue, 20 Apr 2010 15:56:28 +0000

Thanks for your comment. Do you experience that behavior from my example or yours? If you move the mouse quickly across your application, especially outside of it, the MouseEvent.ROLL_OVER or MouseEvent.ROLL_OUT might not be captured properly. It's just how Flex works... when the mouse leaves the bounding box of the application too quickly. Not sure if this is the same issue, but in order to compensate for this, you can look at the code of my example. There is a line: stage.addEventListener(Event.MOUSE_LEAVE, handleMouseLeave, false, 0, true); which handles the case when the mouse leaves the app. The client component has to handle that case. That could be something you may want to consider. Now if your canvas is blank, it might also be the way you are implementing its content. I don't directly see how this relates to the implementation of the component itself--as it extends a regular canvas. I'd probably need to see what you did in order to clarify the issue, should it still occur.

By: Amar

Amar — Tue, 20 Apr 2010 15:07:49 +0000

Your Component is very nice . Am trying this component. i found One bug.. If you are crossing your component quickly the map and buttons are not displayed. The Component is totally blank..Can You have any solution for this..
Thanks in Advance

By: didier

didier — Tue, 15 Dec 2009 19:15:05 +0000

Have you tried to use a timer to set your scroll positions? You can adjust the time so that it gives an ease out towards the center of your container just after the app loads… HTH.
Now the mouse position will always dictate the scroll positions. That’s the idea of the component. Maybe this is not what you need for your application.

By: h.

h. — Tue, 15 Dec 2009 12:25:03 +0000

Well, spent some hours trying to center the view on load, but no success. I can set the *ScrollPosition property but the mouse position makes it to scroll back again. The goal is to be able to go to all directions after the page is loaded. Your demo starts in upper left corner too – any hint how to center the view on startup? Many thanks

By: didier

didier — Sat, 12 Dec 2009 18:51:35 +0000

I agree with you that exposing the visibility of the buttons at the API level would be a useful feature. However, this component is not something I sell or directly support. It reflects some user experience exploration I was doing with Flex, maps, and goal-based animations at some point in time. The code is there for others to maybe inspire or pursue the exploration thereof. There’s a handful of even more useful features that should be added to make it a normal production component. Thanks for your interest!
Re: the horizontal(vertical)ScrollPosition, this might be due to the fact that the innerCanvas is not fully rendered yet on creationComplete. It’s more by design. A workaround might be to call invalidateDisplayList() in the setters in a callLater fashion, in order to delay the scroll positions to the next frame. Not sure this will work, though. Great catch

By: h.

h. — Fri, 11 Dec 2009 20:37:30 +0000

Thanks for your fast replay. I made exactly the same hack you suggest . However, direct support of this feature would be very useful and it’s simply weird that it’s not there… One more thing. Initial setup of horizontal(vertical)ScrollPosition as attribute of the component in mxml is “ignored”. Setting it in creationComplete event handler doesn’t work too. Doing it in runtime (e.g. in some event handler) works fine. Is that by design? Any workaround?