question

Hi @Judith S,

setnodenum(token.Item.find(">spatial/offsetsx"), 1);

Let's break apart what is going on. First of all, the setnodenum() function uses the following syntax to set a value to a treenode:

setnodenum(treenode thenode, num value)

So the 2nd parameter in the top code is easy: 1. We are setting the value of some treenode to 1.

And which treenode are we going to set a new value on? For the code you're asking about, the treenode is defined using the following:

token.Item.find(">spatial/offsetsx)

Several things are happening here:

1. token is a reference to some token moving through your Process Flow.
2. From token you are using dot-syntax to access the Item that has been associated with the token.
3. From Item, you are calling that Object's find() method, which will traverse into its tree data to search for a node at the given data tree path.
4. The path looks like this: >spatial/offsetsx. You can kind of relate this path to a path on your hard drive, like C:\Program Files\FlexSim. FlexSim is a folder under Program Files. The \ character has a meaning. So do other characters, like the :. Let's look at FlexSim's path syntax for this code:
   1. > - dive into the Item object's tree data
   2. spatial - find the node named spatial
   3. / -the forward slash indicates to look at the previous node's child nodes
   4. offsetsx - this is the name of the child node of spatial that we are looking for
   5. This image shows an example of how this path would work:

      

So in the end, the meaning of those two lines of code is this:

1. Set the Item's offsetsx attribute (which helps define its size in the x-dimension) to 1.
2. Set the Item's offsetx attribute (which helps define the Item's position along the x-dimension) to 0.

The whole concept of offsets vs spatials is a good topic for a brand new question. If you need to explore that topic, go ahead and ask a new question. Or comment below with any follow-up questions regarding reading the code examples above.