StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14009098
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-23T06:21:16.760
FavoriteCount
0
LastActivityDate
2012-12-23T06:21:16.760
LastEditDate
LastEditorUserId
0
OwnerUserId
1338055
ParentId
10406516
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
We had success resolving a similar (but not identical) issue using the <code>change</code> option of the the <code>sortable</code> function. Our problem was that we had some "tall" LI elements in the two column list, and when those tall elements were in the first column, other items would pile up in the second column adjacent to the tall elements since all the LI elements were <code>float: left</code>. This would make for very strange interaction when sorting. To get around the issue, you can apply <code>clear: both</code> to all the LI elements in the first column (all the odd elements), however things get screwy in the middle of a sort because there is an extra LI element in the list with absolute positioning (the one being dragged), and it throws off the even and odd selectors. The solution was to use the <code>change</code> callback that is invoked every time the DOM changes during sorting. You can then use jquery to accurately figure out which are the LI elements that are actually in the first column and apply <code>clear: both</code> to those elements. <pre><code> function setClearsOnFirstColumn() { var colNum = 0; $(".myList").find( "li:not(.ui-sortable-helper)" ).each( function() { var thisLiEl = $(this); if( colNum == 0 ) thisLiEl.css( "clear", "both" ); else thisLiEl.css( "clear", "none" ); colNum ++; if( colNum == 2 ) colNum = 0; } ); } $(".myList").sortable( { change: setClearsOnFirstColumn, stop: setClearsOnFirstColumn } ); </code></pre> The <code>not</code> part of the selector serves to ignore the LI element being dragged (identified by its <code>.ui-sortable-helper</code> class) when determining which are the LI elements in the first column. (Could also shorten this by using even and odd jquery selectors - it is not done that way here only because the snippet was adapted from a more general case to support more than two columns in the list.) Note you also need to call <code>setClearsOnFirstColumn</code> after the list is initially rendered.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCSS for two column jQuery UI Sortable List grid that handles elements of different sizes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBrave Dave
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. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.