Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><em>Tidied up for greater clarity</em></p> <p><code>.trigger()</code> returns a jQuery object so you are denied the option of doing <code>$.when() ... $.then()</code>.</p> <p>On the other hand, <code>.triggerHandler()</code>, will return an object of your choice, thus making it possible to do the deferred trick.</p> <p>Your code is organised in three functions, simplified below. The call path is 1,2,3 and the all-important return path is 3,2,1.</p> <p>(1) The highest level (JSON success) function will include the following lines :</p> <pre><code>function() { ... $.when($('#' + data[0].ID).triggerHandler('click')).done(function() { $.each(data[0].ListEntries, function (key, val) { ... }); }); ... }; </code></pre> <p>(2) The click handler triggered by (1), will be as follows :</p> <pre><code>$("img.Button").on("click", function () { return GetModels(this.id);//here `return` passes on the jqXHR object, up the return path. }); </code></pre> <p>(3) And the lowest level function containing the JSON, on which (1) depends, will be of this general form :</p> <pre><code>function GetModels(id) { ... var jqXHR = getJSON(function(){...}); ... return jqXHR;//it is vital to retutn the jqXHR object arising from the json call. } </code></pre> <p>Notes :</p> <ul> <li>The return path delivers, as the "promise" argument to the <code>.when()</code> method in (1), the jqXHR object arising from the <code>.getJSON()</code> call in (3). The chained <code>.done()</code> in (1) is thus forced to wait for the jqXHR to be resolved (ie. complete) before firing the function that is provided as its argument.</li> <li>The click handler makes no assumptions about how it is invoked. It simply returns the jqXHR object. Thus when invoked with <code>.triggerHandler()</code>, the click handler can have additional behaviour appended to it without affecting the normal click action.</li> <li>It would be simpler to call <code>GetModels()</code> directly from (1), cutting out the middle-man (2), which is fine if <code>GetModels()</code> behaviour is uniquely wanted. If, however, (1) needs to be responsive to any future changes to the triggered click handler (2), then the above approach needs to be adopted.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow can I have $.each wait until a .trigger('click') event loads everything?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBeetroot-Beetroot
    1. USBeetroot-Beetroot
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I have $.each wait until a .trigger('click') event loads everything?
      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. VTAcceptedByOriginator
    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. COevent.preventDefault() in the triggered click event is saying "Object doesn't support this property or method". The code setting up the click event is: $("img.Button").on("click", function () { GetModels(this.id); }); This is what populates the divs with data needed for the OP code. Does something here need to change?
      singulars
      1. PO
      1. USChris M
    2. COOK, for an img `.preventDefault()` isn't necessary as an img has no default action, so that line can be deleted. For completeness above, I have left it in but added some safety to avoid the error being thrown.
      singulars
      1. PO
      1. USBeetroot-Beetroot
    3. CODang, still no go. The dependent $.each still isn't waiting for the click to finish. I think I'll have to find another method of populating this dependent data.
      singulars
      1. PO
      1. USChris M
 

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