Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Good news! I was able to fix/workaround your problem in two different ways (see below).</p> <p>I would say this is certainly an OS bug. What you are doing causes the cell you have moved (using <code>moveRowAtIndexPath:</code>) to be placed above (in front of) the header cell in the z-order.</p> <p>I was able to repro the problem in OS 5 and 6, with cells that did and didn't have UITextFields, and with the tableView in and out of edit mode (in your video it is in edit mode, I noticed). It also happens even if you are using standard section headers.</p> <p><strong>Paul</strong>, you say in one of your comments:</p> <blockquote> <p>I solved it badly using a loader and "locking" the table while preforming a reloadData</p> </blockquote> <p>I am not sure what you mean by "using a loader and locking the table", but I did determine that calling <code>reloadData</code> after <code>moveRowAtIndexPath:</code> does fix the problem. Is that not something you want to do?</p> <pre><code>[self.tableView moveRowAtIndexPath:indexPath toIndexPath:newPath]; //[self.tableView reloadData]; // per reply by Umka, below, reloadSections works and is lighter than reloadData: [self reloadSections:[NSIndexSet indexSetWithIndex:indexPath.section] withRowAnimation:UITableViewRowAnimationNone]; </code></pre> <p>If you dont want to do that, here is another solution that feels a little hacky to me, but seems to work well (iOS 5+):</p> <pre><code>__weak UITableViewCell* blockCell = cell; // so we can refer to cell in the block below without a retain loop warning. ... cell.onTextEntered = ^(NSString* sText) { // move item in my model NSIndexPath *newPath = [NSIndexPath indexPathForRow:0 inSection:indexPath.section]; [self.itemNames removeObjectAtIndex:indexPath.row]; [self.itemNames insertObject:sText atIndex:0]; // Then you can move cell to back [self.tableView moveRowAtIndexPath:indexPath toIndexPath:newPath]; [self.tableView sendSubviewToBack:blockCell]; // a little hacky // OR per @Lombax, move header to front UIView *sectionView = [self.tableView headerViewForSection:indexPath.section]; [self.tableView bringSubviewToFront:sectionView]; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCell shows on top of section header
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMorgan
    1. USMorgan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCell shows on top of section header
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis sounds awesome and definitely worth a try. I am back at work on thursday and try it out first thing! To answer your question: No, that is most certainly not something I want to do Thnx
      singulars
      1. PO
      1. USPaul Peelen
    2. COI just tried your code, and it does solve a part of the problem... as soon as I leave editing mode it's all good... but while still in editing mode and scrolling it overlaps.
      singulars
      1. PO
      1. USPaul Peelen
    3. COSolved it by NOT setting the sectionHeaderView to front after sending the cell to the back. Just without the sending the cell back it works great. Thnx!
      singulars
      1. PO
      1. USPaul Peelen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload