Existence of an attribute

Question

question

Marco Baccalaro asked Apr 10 2018 at 12:50 PM Marco Baccalaro commented Apr 10 2018 at 3:20 PM

Existence of an attribute

I have this code that returns <no path>:

Object box = model().find("Tools/FlowItemBin/Box/Box");
treenode itemBehaviour = box.attrs.behaviour;
return itemBehaviour;

But this code returns "It exists":

Object box = model().find("Tools/FlowItemBin/Box/Box");
treenode itemBehaviour = box.attrs.behaviour;
if (itemBehaviour)
	return "It exists";
else
	return "It does not exist";

It returns "It does not exist" if I change the second row to:

treenode itemBehaviour = box.find(">behaviour");

Why does this happen? Is it because those are hashed nodes?

Software Version:

FlexSim 18.0.4

attributes objectexists object.attrs

attributeexistence.fsm (16.1 KiB)

______

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 · 2018-04-10T15:06:22Z

Matthew Gillespie answered Apr 10 2018 at 3:06 PM Marco Baccalaro commented Apr 10 2018 at 3:20 PM

This is a bug that we'll be fixing soon, but the issue is that currently box.attrs.behaviour is exactly the same as calling behaviour(box). This, like all the old commands that return a treenode, will return saferef instead of returning a null treenode.

So currently, if you use box.attrs.behaviour, you need to treat it like an old command and use if(objectexists(itemBehaviour)).

You could also use box.attrs.find("behaviour").

We'll be fixing the attrs property so that it no longer returns saferef when the attribute doesn't exist.

· 1

question