StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9220653
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-09T23:35:24
FavoriteCount
0
LastActivityDate
2012-02-10T16:34:56.457
LastEditDate
2012-02-10T16:34:56.457
LastEditorUserId
1196801
OwnerUserId
1196801
ParentId
5409097
PostTypeId
2
Score
9
ViewCount
0
LastEditorDisplayName
text
Body
Here's a problem with Layke's solution (which otherwise does work) found by pre-production testing for a commercial website. Case 1: <ul> <li>Create & populate a tree.</li> <li>Click on a node to select.</li> <li>Execute refreshTree as in Layke's solution.</li> <li>Click on a node, get error "this.labelNode is undefined".</li> </ul> Now start again, case 2: <ul> <li>Create & populate a tree.</li> <li>Click on a node to select.</li> <li>Ctrl-click on the previously selected node. </li> <li>Execute refreshTree as in Layke's solution.</li> <li>Click on a node, no error.</li> </ul> The stored selection references to the first selection are being used to undo the selection attributes (background color, etc.) when the second selection is made. Unfortunately, the referred-to objects are now in the bit-bucket. The modified code appears to be production-ready, i.e. hasn't failed any pre-production tests. The solution is to put: <pre><code>Tree.dndController.selectNone(); </code></pre> prior to first line of Layke's refreshTree solution above. In response to meta suggestions, here it is: <pre><code>refreshTree : function() { // Destruct the references to any selected nodes so that // the refreshed tree will not attempt to unselect destructed nodes // when a new selection is made. // These references are contained in Tree.selectedItem, // Tree.selectedItems, Tree.selectedNode, and Tree.selectedNodes. Tree.dndController.selectNone(); Tree.model.store.clearOnClose = true; Tree.model.store.close(); // Completely delete every node from the dijit.Tree Tree._itemNodesMap = {}; Tree.rootNode.state = "UNCHECKED"; Tree.model.root.children = null; // Destroy the widget Tree.rootNode.destroyRecursive(); // Recreate the model, (with the model again) Tree.model.constructor(dijit.byId("myTree").model) // Rebuild the tree Tree.postMixInProperties(); Tree._load(); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to update dojo tree data dynamically
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USkcrossen
UserOwnerUserId
1. USkcrossen
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. 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.