d3.js - check if d3.select or d3.selectAll -


i have method on reusable chart can passed selection , return value if passed d3.select('#id') selection or array of values if passed d3.selectall('.class') selection. i'm interrogating passed argument context._groups[0] instanceof nodelist, feels little fragile using undocumented property, may change in future versions. there more built in way of determining if selection comes select or selectall?

selection.size() not here, tells result of selection, not how called.

edit: here's context of use. i'm using mike bostock's reusable chart pattern , instance includes method getting/setting label donut.

to me, api usage follows principle of least astonishment, it's how expect result returned.

var donut = app.rotatingdonut();  // set label 1 element d3.select('#donut1.donut')     .call(donut.label, 'donut 1')  d3.select('#donut2.donut')     .call(donut.label, 'donut 2')  // set label multiple elements d3.selectall('.donut.group-1')     .call(donut.label, 'group 1 donuts')   // label 1 donut var donutonelabel = d3.select('#donut1').call(donut.label) // donutonelabel === 'donut 1'  // label multiple donuts var donutlables = d3.selectall('.donut').call(donut.label) // donutlabels === ['donut 1', 'donut 2', 'group 1 donuts', 'group 1 donuts']

and internal method definition:

app.rotatingdonut = function() {    var label = d3.local();    function donut() {}    donut.label = function(context, value) {     var returnarray;     var islist = context._groups[0] instanceof nodelist;      if (typeof value === 'undefined' ) {        // getter       returnarray = context.nodes()           .map(function (node) {return label.get(node);});        return islist ? returnarray : returnarray[0];     }      // settter     context.each(function() {label.set(this, value);});      // allows method chaining     return donut;   };    return donut }

well, question here @ s.o. doesn't have answer (it has happened before).

that seems case of question of yours: "is there more built in way of determining if selection comes select or selectall?". no.

to prove that, let's see source code d3.select , d3.selectall (important: not selection.select , selection.selectall, different each other).

first, d3.select:

export default function(selector) {     return typeof selector === "string"         ? new selection([[document.queryselector(selector)]], [document.documentelement])         : new selection([[selector]], root); }

now, d3.selectall:

export default function(selector) {     return typeof selector === "string"         ? new selection([document.queryselectorall(selector)], [document.documentelement])         : new selection([selector == null ? [] : selector], root); }

as can see, have two differences here:

  1. d3.selectall accepts null. not you.
  2. d3.selectall uses queryselectorall, while d3.select uses queryselector.

that second difference 1 suits you, know now, since queryselectorall:

returns list of elements within document (using depth-first pre-order traversal of document's nodes) match specified group of selectors. object returned nodelist. (emphasis mine)

and queryselector only...:

returns first element within document matches specified selector, or group of selectors.

therefore, undocumented (and hacky, since using _groups, not idea) selection._groups[0] instanceof nodelist using right seems way tell selection created d3.select selection created d3.selectall.


Comments

Post a Comment

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

i'm implementing inapp billing in android app. works well, however, i'm trying decouple broadcast receiver activity manifest. suggestion in android's trivialdrive sample: // important: dynamically register broadcast messages updated purchases. // register receiver here instead of <receiver> in manifest // because call getpurchases() @ startup, therefore can ignore // broadcasts sent while app isn't running. // note: registering listener in activity bad idea, done here // because sample. regardless, receiver must registered after // iabhelper setup, before first call getpurchases(). currently there's class extends broadcastreceiver : public class iabbroadcastreceiver extends broadcastreceiver { /** * intent action receiver should filter for. */ public static final string action = "com.android.vending.billing.purchases_updated"; private final iabbroadcastlistener mlistener; public iabbroadcastreceiver(iabbroadcastlistener listener) { m...
Read more

python Tkinter Capturing keyboard events save as one single string -

is possible store keyboard events 1 string? code below stores 1 char , prints it. card reader or bar code reader, contains collection of character/ string not 1 character @ time. goal save char pressed text variable. from tkinter import * root = tk() def key(event): text= event.char text+= event.char print ("pressed", text) def callback(event): frame.focus_set() print ("clicked at", event.x, event.y) frame = frame(root, width=100, height=100) frame.bind("<key>", key) frame.bind("<button-1>", callback) frame.pack() root.mainloop() currently, creating text variable , everytime key() function gets called, , text stores last character typed. you can define text module level variable , , use module level text inside key function - text = '' def key(event): global text text+= event.char print("pressed", text)
Read more

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -

here tables: create table customer ( cid int primary key, name varchar(32) ) create table ord ( oid int primary key, cid int foreign key references customer, address varchar(20) ) here's linq-to-sql statement: var aaa = c in db.customer select new { c, o = c.ord.tolist() }; and here's inexplicable query generated linq-to-sql: select [t0].[cid] [cid], [t0].[name] [name], [t1].[oid] [oid], [t1].[cid] [cid2], [t1].[address] [address], (select count(*) [dbo].[ord] [t2] [t2].[cid] = [t0].[cid]) [value] [dbo].[customer] [t0] left outer join [dbo].[ord] [t1] on [t1].[cid] = [t0].[cid] order [t0].[cid], [t1].[oid] i want understand how rid of count(*) part. it's entirely uncalled for! linq needs count(*) in order determine number of entries returned o = c.ord.tolist() .
Read more