You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys,
I use TiDraggable and created a "snapping points" on iOS. That means, depending where you finish drag event, view automatically snaps to top, initial position or closes the parent view(I use it as a filter similar to Apple Maps.app).
When I moved my fully fuctional code from iOS to android, it wasn't working at all. Problem is, that iOS returns different value for width/height property than android(known difference).
So I discovered, that TiDraggable returns bad numbers as e.top in events and it needs to be divided by logical density factor to get results similar to iOS...
This is not really a bug, maybe a note to someone who is doing similar task as I do and have similar problem as I had. So maybe this note can help someone to quickly adopt code migrated from iOS to Android.
Thanks
The text was updated successfully, but these errors were encountered:
Hi guys,
I use TiDraggable and created a "snapping points" on iOS. That means, depending where you finish drag event, view automatically snaps to top, initial position or closes the parent view(I use it as a filter similar to Apple Maps.app).
When I moved my fully fuctional code from iOS to android, it wasn't working at all. Problem is, that iOS returns different value for width/height property than android(known difference).
So I discovered, that TiDraggable returns bad numbers as e.top in events and it needs to be divided by logical density factor to get results similar to iOS...
This is not really a bug, maybe a note to someone who is doing similar task as I do and have similar problem as I had. So maybe this note can help someone to quickly adopt code migrated from iOS to Android.
Thanks
The text was updated successfully, but these errors were encountered: