Conversation
Conflicts: nodes/vvvv.nodes.string.js
|
Thanks for this huge contribution, and sorry, that it took me so long to respond. I suspect the QuerySelector node adds redundant functionality: you can already retreive DOM data by an ID by creating an input IOBox and labelling it with "#id" (where you replace "id" with the actual id, obviously). Like described in the "Reading from the DOM" section of the VVVV.js Integration Guide. Or maybe I missed something? Correct me if I'm wrong. |
|
Yes, I use query selector to retrive information from dom elements, but I need to know from select element which is selected. I'm on holidays in spain so I can't answer fast) On Tue, Aug 19, 2014 at 10:36 AM, Matthias Zauner
|
|
Hi, im returned from holidays. |
|
Hi, I was away from VVVV.js for a while, but back now :) Ok, I'm pretty sure, QuerySelector does the same as named IOBoxes do, described in the VVVV.js Integration Guide. For example, you can get the selected option of a select box by naming an input IOBox like So, if you can confirm that this accomplishes the same, I would suggest we drop the QuerySelector node, in order to avoid duplicate functionality. As for the bugfix: I think it will be added automatically to the pull request, as soon as you push again to that branch. Probably this is what happened with the "fix CDR" commit above. |
Add some nodes
CAR
CDR
DeleteSlice
Reader
GetSlice
GetSpread Advanced
Sort Advanced
Unzip
Occurrence