Hello all,
the example in this link does not work.
http://livedocs.adobe.com/flex/3/langref/mx/effects/Move.html
The exact error message is:
Severity and DescriptionPathResourceLocation
Creation Time Id
Type was not found or was not a compile-time
was able to reproduce your error by naming the application 'move' instead)
Chet.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of hworke
Sent: Tuesday, December 02, 2008 8:05 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] move effect Flex live doc example does
, December 02, 2008 8:05 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] move effect Flex live doc example does not work
Hello all,
the example in this link does not work.
http://livedocs.adobe.com/flex/3/langref/mx/effects/Move.html
The exact error message is:
Severity
Irrespective of screen resolution the components can be moved from outside
of the flex application.
mx:Move id=moveIn xFrom={-can.width} yFrom=0 duration=1000/
mx:Move id=moveOut /
mx:Button click=can.visible=can.visible?*false*:*true*/
mx:Canvas id=can width=400 height=400 visible=false
here... try this out.. mebbe this is something u required.
the stuff u required just intrigued me.. so .. jus made one..
Although, I hate the basic flash fx api's... i would rather use the tweener
class for movements.. but ..i jus didn't want you to see another bunch of
code make this simple for
How can I specify any Flex component to move out of the screen if i do
not know the screen resoluction of the end user beforehand?
Is there some Move value like '-1' that indicates to move out of any
size screen?
Thanks
@yahoogroups.com
Subject: [flexcoders] Move effect
Date: Wed, 16 Jan 2008 22:18:23 -
How can I specify any Flex component to move out of the screen if i do
not know the screen resoluction of the end user beforehand?
Is there some Move value like '-1' that indicates to move out of any
size screen
I've got a HBox with number(about 10) of images (375x200). For some
reason the images are flickering. It's really anoying.
I'm changing they x-property and let the moveEffect handle the rest,
for some reason it really looks weird.
mx:HBox id=preview_container2
Ely over at QuietlyScheming.com just created a SuperImage component
which I believe fixes the issue you're experiencing.
http://www.quietlyscheming.com/blog/2007/01/23/some-thoughts-on-doubt-on-flex-as-the-best-option-orhow-i-made-my-flex-images-stop-dancing/
Cheers,
Brian
On 2/1/07,
9 matches
Mail list logo
