Skip to main content

insertSubview:belowSubview: in UITableViews



I have a UITableView with UITableViewCell s that are swipable. When a cell is swiped, I want a view to be visible (revealed) underneath that cell. Here's the code that I have:







UITableViewCell *cell = [self.tableView cellForRowAtIndexPath:indexPath];



_cellBack = [[UIView alloc] initWithFrame:CGRectMake(0, cell.frame.origin.y, cell.frame.size.width, cell.frame.size.height)];

_cellBack.backgroundColor = [UIColor whiteColor];

[self.tableView insertSubview:_cellBack belowSubview:cell];



for (int i = 0; i < [self.tableView subviews].count; i++) {

UIView *v = [[self.tableView subviews] objectAtIndex:i];



if ([v isEqual:_cellBack]) {

NSLog(@"cellBack %d", i);

}

if ([v isEqual:cell]) {

NSLog(@"cell %d", i);

}

}







In the for loop, I check to see if the views' indexes are as I expect, and indeed they are; _cellBack has an index that is one less than cell 's index.





When I replace the insertSubview:belowSubview: call with insertSubview:aboveSubview: , it works fine (albeit with the white UIView showing up above the swiped cell), so it's not a matter of not allocating _cellBack properly. I've also tried insertSubview:atIndex: and that didn't work either..





What could be causing this?





Thanks!


Comments

  1. UITableView's already have the ability to put things behind cells. It's the backgroundView of the cell. Why don't you try that instead so you would do the following:

    cell.selectedBackgroundView = _cellBack;

    ReplyDelete
  2. So it turns out that, if I add it to another view, the code works as expected.

    Here's where I added it:

    _cellBack = [[UIView alloc] initWithFrame:CGRectMake(0, cell.contentView.frame.origin.y, cell.frame.size.width, cell.frame.size.height)];
    _cellBack.backgroundColor = [UIColor whiteColor];

    [cell insertSubview:_cellBack belowSubview:cell.contentView];


    I'm still not sure why the code in the question doesn't work. The SideSwipeTableView from this github account has code similar to what I had before and it works fine.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex