This is a migrated thread and some comments may be shown as answers.

FX transfer - Buggy?

3 Answers 38 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Don
Top achievements
Rank 1
Don asked on 17 Apr 2013, 09:17 AM
I've had a very difficult time trying to get FX transfer (http://docs.kendoui.com/api/framework/fx/transfer) to simply move a div from one position to another.  It seems like to would be very straightforward.  However, it wasn't.  I tried to work backwards from the transfer demo (http://demos.kendoui.com/web/fx/transfer.html) and finally, after much trial and error, I was able to accomplish it (sort of).  

Please see this jsfiddle .  The trick to get it to work was to make the height/width of #Finish 1px less than #Start. However, I don't want to have to change the height/width.  I just want the div to move (I also discovered that I could get it to work with height/width of 110px if I added a border.  However, I don't want a border).  So, my question is, is this a bug?  Shouldn't I be able to use transfer to move a div without changing the height/width or adding a border?  If there is a way, please let me know.



3 Answers, 1 is accepted

Sort by
0
Accepted
Petyo
Telerik team
answered on 18 Apr 2013, 08:37 AM
Hello Don,

If you are just looking for moving a div around without changing its dimensions, you may simply animate its left/top css values or translatex/translatey transform values using CSS only. The transfer animation targets the  complex case of scaling and moving an element to another one, while maintaining the expected route.

Regards,
Petyo
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Don
Top achievements
Rank 1
answered on 30 Apr 2013, 05:40 AM
Thanks for the reply.  However, I would like to suggest that you guys make it so that either transfer works with just movement or scaling (i.e. not be restricted to both) or create a separate fx for moving elements, because  I believe that is a fairly popular effect.  I understand that I could use css translatex/y, but then I would need to test for browser compatibility.  Or, I could just use javascript .animate, but that is often choppy in mobile environments.  If I'm not mistaken, the benefit of kendo's fx is that they will take care of all that for us.

P.S.  If you should decide to follow either suggestion, I'd also like to add that it would be greatly helpful the fx
didn't "detached (the element) from its current position and re-attached in the body element" (source) if at all possible.  This can make coding some situations impossible (e.g. sometimes you need to use .position() of an elements with a relative positioned parent rather than .offset() when moving elements around).  Thanks.
0
Petyo
Telerik team
answered on 01 May 2013, 03:48 PM
Hello Don,

Thank you for your suggestion. As the mechanics of the two transitions share nothing in common, such transition would most likely be introduced as a separate one, should we decide to implement it.

In general, I would prefer to avoid the re-attachment limbo as it causes various inconveniences like the one you describe; unfortunately this is the only working approach in several complex layout cases, which were discovered during our edge case testing. 

Greetings,
Petyo
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
Tags
General Discussions
Asked by
Don
Top achievements
Rank 1
Answers by
Petyo
Telerik team
Don
Top achievements
Rank 1
Share this question
or