StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8324016
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2011-11-30T09:54:28.190
FavoriteCount
0
LastActivityDate
2018-01-16T09:51:46.047
LastEditDate
2018-01-16T09:51:46.047
LastEditorUserId
865175
OwnerUserId
1055278
ParentId
5887305
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
You can subclass UIView and override hitTest:withEvent: in a way to pass touch events to a view that you specify (_backView): <pre><code>- (UIView *)hitTest:(CGPoint)point withEvent:(UIEvent *)event { UIView *view = [super hitTest:point withEvent:event]; if (view == self) { view = _backView; } return view; } </code></pre> If the touch event was to be handled by this view it would be passed to "_backView" (that can be an IBOutlet so that it can be set using interface builder) ; and if it was to be handled by any child view just return that child (the result of <code>[super hitTest:point withEvent:event]</code>;) This solution is fine as long as you know what view you need to pass the events to; besides don't know if it has problems since we are returning a view (_backView) that is not a subview of the current UIView !! but it worked fine in my case. A better solution might be the one mentioned in <a href="https://stackoverflow.com/questions/3427619/disable-touches-on-uiview-background-so-that-buttons-on-lower-views-are-clickabl">Disable touches on UIView background so that buttons on lower views are clickable</a> There its mentioned to use <code>-pointInside:withEvent:</code> ; compared to previous solution its better in the way that you don't need to specify a '_backView' to receive the events (the event is simply passed to the next view in chain)! drawback might be that we need to perform <code>-pointInside:withEvent:</code> on all subviews (might be of negligible overhead though)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUIView -- "user interaction enabled" false on parent but true on child?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USIulian Onofrei
UserOwnerUserId
1. USAli
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COthanks for the approach here and the "Disable touches.." link. the approach described there seems pretty clean.
 singulars
 PostPostId
 PO
 UserUserId
 USorion elenzil

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.