Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The behavior you're describing sounds like a job for <code>UITableViewCellAccessoryDetailDisclosureButton</code>, actually. If you're going to be pushing another view onto the stack but don't want to do that when the user selects the cell proper, use a detail disclosure button to maximize your consistency with existing UI convention. It's hard to say without more information.</p> <p>As for doing the work necessary to detect touches in a sub-region, that may be more trouble than it's worth. True, adding subviews to a cell incurs a compositing cost but if you're only talking about one button, and a button whose background you can set to opaque, you'll probably be just fine. The alternative is reinventing the wheel to recreate button behavior in a subregion of the cell and that doesn't sound like functionality that will be much fun to maintain as the SDK matures.</p> <p>That said, adding views to a cell doesn't incur a compositing cost per se, it's drawing those views that's the trouble. So if you really wanted to go nuts on the optimization, you could create a pre-rendered cell background image that includes the appearance of a button you want and then place a custom, image-free, see-through UIButton instance right over top of it. Nothing to draw, so no additional compositing cost. Worth a shot.</p> <p>You didn't come here for a premature optimization speech, so I won't bother with one, but I say just do the cell with a normal button for now, make sure you like how the functionality feels to use then optimize toward the end if you're looking at performance that you're not happy with.</p>
    singulars
    1. This table or related slice is empty.
    1. POOverriding selectable area of UITableViewCell?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDanilo Campos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have a very umm, detailed data index, and sometimes it's not practical to navigate in the normal iPhone fashion ie: Big > Medium > Small > Detail View. In my case the specific button in the detail view (a UITableView with custom cells) when you would press the button, you'd see the details of the selected object, followed by lets say the 20 objects before and after it at the bottom of the data hierarchy. Does that make sense? The detail disclosure button isn't as intuitive as I'd like it to be.
      singulars
      1. PO
      1. USMike A
    2. COYou know your UI and you know which rules you need to break for your specific circumstances, so try it, make sure it feels right, then refine from there. Have users who have no idea what you're building try it out. Detail disclosure can be unintuitive for even its normal uses, I've found from support emails. So convention is a guidepost, not a straitjacket. If the detail disclosure won't do it, try out the pre-baked cell background with a see-through UIButton. Shouldn't hurt your performance and it won't be a pain to build or maintain.
      singulars
      1. PO
      1. USDanilo Campos
    3. COVery good idea Danilo, thanks.
      singulars
      1. PO
      1. USMike A
 

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