bryankeller/BLKFlexibleHeightBar

Table View Headers — how to implement?

kylebshr opened this issue · 8 comments

I'm currently having my UITableView fill the view entirely, and setting the content inset to the max height of my flexible bar. This works great without headers, but when I have section headers on my tableview, they are pushed down due to the content inset. Is there a proper way to do this, or do I need to do something hacky? See the photos for details of what I mean.
Before scroll
After scroll — section header is out of place

Awesome looking app. I'm looking into this now.

Great, thank you! To be clear, these are the headers from a .Grouped style UITableView.

So I know what the issue is, but it's going to take me a few days to find the time to implement a good fix. I'll keep you posted.

Good to hear! No rush. I tried to use the scrollViewDidScroll method in the behavior definer to set the insets when it was scrolled, but this was unreliable.

If any of you have an idea for a good solution to this issue I would be terribly happy to see it :-) I could use it right now. Manipulating the insets in scrollViewDidScroll does not look good.

It's still on my agenda, but I'm really busy this month. If anyone wants to implement a fix, try to do so in BLKFlexibleHeightBarBehaviorDefiner - this is the base class that all others inherit from, so it would be nice if it can be fixed in one place. Pull requests are welcome =)

That being said, I'll look into this again as soon as I get the chance.

I don’t know too much Objective-C, but I have an idea. I’ll pull and give it a shot.

On Apr 13, 2015, at 2:40 PM, Bryan Keller notifications@github.com wrote:

It's still on my agenda, but I'm really busy this month. If anyone wants to implement a fix, try to do so in BLKFlexibleHeightBarBehaviorDefiner - this is the base class that all others inherit from, so it would be nice if it can be fixed in one place. Pull requests are welcome =)

That being said, I'll look into this again as soon as I get the chance.


Reply to this email directly or view it on GitHub #14 (comment).

Have a look at this and this if solves the issue #29