Integration with observable list view about phoenix HOT 6 CLOSED

@jamescategory thanks for all the details. I'll try to find out a fix for you asap.
|(• ◡•)| peace

from phoenix.

@shliama Thanks a lot! looking forward to see a solution to this. btw, I just noticed I have forgotten to attach the screenshot :) here we go:
https://www.dropbox.com/s/07mg7iy9fedcrnx/Screenshot_2015-02-17-10-32-59_1.jpg?dl=0

from phoenix.

Hi, sorry for the huge delay, but I haven't had enough time recently.

So, I've looked at the StickyHeaderListView sample, and reproduced the same issue from your screenshot.
Unfrortunately, it seems there is no easy workaround for this issue. As you can see, those two redundant white spaces are in fact 1st and 2nd "fake" list items that are covered with headers.
And the headers are just views that are above the ListView.

Well, if you really want to combine these two libraries, my advice is to include my library as module (not via gradle, you'll need to change library code), and play with methods that set initial position of the refresh layout (you shouldn't add top margin).
In the PullToRefreshView class, you will see that for default offset I'm using in methods to move/animate the refresh view is (mTarget.getTop()) that's just top point of the list view, so maybe you might try to add there height of those two fake list items. Also those two fake list items must be transparent - so they don't cover refresh view.
Plus, while list view is refreshing, scrolling it up will hide the header, this issue must be fixed somehow too.

from phoenix.

@jamescategory hi! do you achieve it ？

from phoenix.

@shliama thanks a lot of the detailed guide. I messed around a lot with it but I couldn't make it work properly. I was under pressure to meet a deadline so I had to give up. Perhaps in the future I revisit the problem gain. But again, thank you very much for your help :)

from phoenix.

@jamescategory you're welcome :)
Unfortunately it's hard to create a library that is compatible with other libraries on the internet. We all use some hacks and workarounds to achieve custom / non-native look and feel of our components, therefore it's not a surprise that they may conflict with each-other ¯_(ツ)_/¯

from phoenix.