Dionysis Lorentzos
Dionysis Lorentzos
Hi @boylenssen . I plan this to be part of the v2. I have not started working on it yet. I prioritize first the card directions and then this feature....
What do you mean by x and y scrolling? Related to what? The screen, the pointer down touch event?
OutOfMemory is usually a sign of memory leak. The problem is that picasso looks like it creates an infinite loop when interfering with async tasks (infinite calls of requestLayout). Sorry...
Not really. I would be glad to review a pull request however if someone digs into that.
Good question. I cannot think at this point with the current architecture to do so.
Thanks for the stack trace. What's your version please? Also do you multi-touch the screen when the app crashes?
Thanks. Failing because of #18
Indeed that's happening also with the example. Would you like to try this trick? http://stackoverflow.com/questions/9730249/canvas-antialiasing-with-hardware-acceleration-android-api-11-and-later If you find a solution I would be glad to merge it.
How about creating a custom adapter or extending a android-ready one. Then inside the getView() method of your Adapter create the listener that make the changes e.g. in your case...
Hey @Martinch0 and thanks for reporting this. onScroll was implemented via pull request and I didn't have the time since then to optimize and test as much I would liked...