Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can't access the settings in the <code>compSlider</code> function because in your example they are defined in <code>init()</code>, making them local to that function. If you moved the declaration up in scope:</p> <pre><code>$.fn.compSlider = function( method, options ) { var settings = $.extend( {}, defaults, options ); }; </code></pre> <p>Then you'd be able to access it there. Or just defining it (<code>var settings;</code>) in compSlider and removing <code>var</code> in <code>init()</code> would be enough.</p> <p>Update:</p> <p>In repsonse to your comment, yes, sorry, forgot about the issue #2. As it is, you will not be able to access the settings for each plugin object because you cannot "go down" in scope. In other words, you cannot access a local variable of a function from outside of that function. And that is what settings are, local to the <code>compSlider</code> function (if you use the structure I proposed), they are lower in scope as far as your <code>opt()</code> function is concerned.</p> <p>You can, of course, always go up in scope. To achieve this you could set up a variable in the plugin's global space that stores references to all objects created.</p> <pre><code>var compSliderObjects = []; $.fn.compSlider = function( method, options ) { //store objects in compSliderObjects }; </code></pre> <p>However, this is just the an idea, and you still need to figure out how you want to access the compSliderObjects and pull the right settings. Will each object have a unique id? If so, an array of objects (<code>{id: 2, settings: data}</code>). If not, you need to figure out how you want to uniquely identify them and pull them from the array. </p> <p>Also, do you really need to access them globally? It's less work and code to just call the object and get the settings (as shown in the fiddle).</p>
    singulars
    1. This table or related slice is empty.
    1. POjQuery scoped settings for plugin based on Plugins/Authoring article
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDonamite
    1. USDonamite
    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. CO150lbs: I tested this and it didn't work. The problem still existed where the latest element to have the .compSlider() method applied to it would update all "settings" for every other element that had previously hd .compSlider() applied. You can see two different DOM objects here, both of which had different settings, however both of which are showing the same settings (settings.container which is a selector): http://cl.ly/0u0L1i433V3m1d2V0B1Z
      singulars
      1. PO
      1. USDavid Kullmann
    2. CONot exactly sure where you are going wrong then, but I put up a jsfiddle to demonstrate what I'm talking about: http://jsfiddle.net/kFL5N/. I'm not sure that's what you want to do, but it demonstrates seperate settings for each instantiation.
      singulars
      1. PO
      1. USDonamite
    3. CO150PoundsOfDonamite: See "issue #2" in the original post. I think I may just do the method you are suggesting, though.
      singulars
      1. PO
      1. USDavid Kullmann
 

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