» Conventions.NodeReference
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

Conventions.NodeReference

In contrast to a Help Patch, the Node Reference Page on the Wiki should contain reference material and discussions. Node Reference and Help Patch are complementary, they are not supposed to replace each other.
A good node reference page should contain

  • links to external web pages describing the workings and the context of the node (eg. wikipedia, microsofts directx reference etc)
  • reference material on the node´s internal workings like source code fragments, diagrams and tables
  • a FAQ section
  • known bugs and workarounds
  • links to supplementary modules and related nodes
  • changes to the semantics of the node in various releases
  • a backlink section which lists all places in the wiki and in the forum, where the node is mentioned in context.

anonymous user login

Shoutbox

~6h ago

Urbankind: circuitb:Wrongcop is epic! :)

~7h ago

joreg: @tobi: use GetSlice() as the patch i referred you to is demonstrating. or start a forum thread with your patch.

~7h ago

TobiTobsen123: hmm yes i can see the values...but how to handle them as seperate values? I need to forward them via TCP/IP...

~9h ago

joreg: @tobi: OSCDecoder helppatch has a section: OSC_Advanced (bottomright) that demoes decoding of multiple messages

~9h ago

TobiTobsen123: I'm using an OSCDecoder, it receives two arguments...works but how can I seperate the arguments into two seperate values

~12h ago

u7angel: @mediadog, make it a forum question.

~12h ago

u7angel: @mediadog, tty renderer ?

~14h ago

microdee: however non-conductive objects are invisible for this so the pencil and the sticks in the video are still a mysteries