Buildnodeflexscript on node with subnodes

Question

question

Laurenz Peleman asked Oct 24 2017 at 11:54 AM Mischa Spelt commented Oct 25 2017 at 2:44 PM

Buildnodeflexscript on node with subnodes

Hello everyone

I am trying to assign some custom code 'on the fly' to the flow level triggers of a FloWorks flow tank, using the following code. The onpassfluidlevel node containing the level trigger code exists of different subnodes, corresponding to each defined level trigger, which require each some specific code.

treenode levelTriggers = getvarnode(flowTank, "onpassfluidlevel");
for (int i = 1; i <= levelTriggers.subnodes.length; i++) {
	string triggercode = "Object current = ownerobject( c ); Other code to add";
	setnodestr(levelTriggers.subnodes[i],triggercode);
	switch_flexscript(levelTriggers.subnodes[i], 1);
}
switch_flexscript(levelTriggers, 1);
buildnodeflexscript(levelTriggers);

What happens now is that, on executing the buildnodeflexscript command, the sudnodes are built (the red Flescript S in the model tree turns black) but the parent node (onpassfluidlevel) isn't. Hence, the code of the subnodes is not called. I tried to write additional buildnodeflexscript statements, either with the node or the flow tank object as argument, but whatever I tried, the parent node couldn't be built. Does anyone know how this can be overcome?

I post this question here because I think the behaviour is not related to FloWorks specifically, but to building nodes with subnodes in general.

Kind regards

Laurenz Peleman

Software Version:

Choose One

FloWorks development

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2017-10-24T13:11:56Z

Phil BoBo answered Oct 24 2017 at 1:11 PM Mischa Spelt commented Oct 25 2017 at 2:44 PM

Does your levelTriggers node have a syntax error?

I just tested this with new nodes in a Processor's variables and it works fine:

flexscript-subnodes.png (138.3 KiB)

· 10

Laurenz Peleman commented · Oct 24 2017 at 1:47 PM

Thanks for your quick reply @phil.bobo. I don't think there is a syntax error, at least pasting the code manually in the level trigger sheet on the flow tank object does not give a warning message.

I think you added your return statements manually, i.e. without using setvarstr. Could that explain the different behaviour?

0 ·

Phil BoBo ♦♦ Laurenz Peleman commented · Oct 24 2017 at 1:52 PM

It works fine that way too.

Before executing the script (the nodes have string data):

After executing the scripts:

0 ·

before.png (139.6 KiB)

after.png (141.1 KiB)

Laurenz Peleman Phil BoBo ♦♦ commented · Oct 24 2017 at 2:02 PM

You are able to change the string code of the parent node, something I cannot do (nothing happens if I try). Could the node be protected some way, which causes building to fail as well?

0 ·

Show more comments

Laurenz Peleman commented · Oct 24 2017 at 2:23 PM

Okay, my mistake, I thought it wouldn't make a difference, but apparently it does: the flow tank I am talking about is the flow tank on a flow vessel task executer object, not a 'real' flow tank. I am able to assign code to the onpassfluidlevel of the latter, but fail to do it for the vessel tank.

0 ·

Phil BoBo ♦♦ Laurenz Peleman commented · Oct 24 2017 at 2:32 PM

The onpassfluidlevel variable on the FlowTaskExecuter's Tank doesn't have its dataType set. Right-click the node and select Node > Add Text Data or set its dataType using code:

treenode flowTank = model().find("FlowTaskExecuter1/Tank");
treenode levelTriggers = getvarnode(flowTank, "onpassfluidlevel");
levelTriggers.dataType = DATATYPE_STRING;

0 ·

Laurenz Peleman Phil BoBo ♦♦ commented · Oct 24 2017 at 2:47 PM

Okay, so that allows me to turn the S black when building. However, in the Trigger Levels sheet of the vessel tank the code fields are still empty after building. Only if I stop the run, explicitly enter the code window and apply or save, the code seems to be 'recognized' when I resume the model run. Hence, the initial problem (on-the-fly code not running) is not solved yet.

0 ·

Show more comments

question