Dynamic User Library Objects with User Input & External Connections

Question

question

Adam C asked Feb 08 2018 at 10:10 PM Matthew Gillespie commented Feb 12 2018 at 10:17 PM

Dynamic User Library Objects with User Input & External Connections

Hello,

I need some help on a rather involved problem to assist with scalability on a complex model. I have a user library object (visual tool containing an assortment of combiners, queues, and separators) that needs a lot of changes to occur in the dropscript (or maybe another method, if better). Once the object is dragged to the model, it should prompt the user for the ID number of the new object (think hotel room number). That ID number then needs to be written on labels of the visual tool and its child objects, and the visual tool name needs to change to reflect the ID. Finally, some A and S connects need to be made from other objects already in the model to a few of the child objects.

The generic pseudo-code below is basically how I have approached it. Setnodestr worked at one point, but it is messed up now due to meddling. It is backing out of the dropscript and diving down to the visual tool labels, borrowing from the Dropscript examples. There are also issues with how to change the new object's name without permanently changing the user library object (or how to change it back after creating the object).

Any guidance is appreciated!

treenode newitem = dropuserlibraryobject(node("..>item",c));
 
userinput(globalvariableA,"Please input text value for label A");
 
setnodestr(node("..>item/labels/labelA", c), globalvariableA);
 
setnodestr(node("..>item>subitem/labels/labelA", c), globalvariableA);
 
contextdragconnection(externalobject1,item,"A");
 
contextdragconnection(item,externalobject2,"A");
 
contextdragconnection(externalobject3,item,"S");
 
replacename(node("..>item",c),"item",globalvariableA);
 
return newitem;

Software Version:

FlexSim 17.1.6

user library dynamic user input connections activities from code

______

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-02-09T20:34:54Z

Matthew Gillespie answered Feb 09 2018 at 8:34 PM Matthew Gillespie commented Feb 12 2018 at 10:17 PM

You shouldn't set anything on the library object. The newitem returned from the dropuserlibraryobject command is the new instance of the library object created in the model. You should modify that object, something like this:

treenode newitem = dropuserlibraryobject(node("..>item",c));
 
userinput(globalvariableA,"Please input text value for label A");
 
newitem.labelA = globalvariableA;
newitem.subnodes[1].labelA = globalvariableA;
 
contextdragconnection(externalobject1,newitem,"A");
contextdragconnection(newitem, externalobject2,"A");
contextdragconnection(externalobject3,newitem,"S");
 
newitem.name = globalvariableA;
 
return newitem;

Note that you can access labels of objects by name using dot syntax.

· 2

Adam C commented · Feb 12 2018 at 8:48 PM

@Matthew Gillespie Thanks for your input. Between your comment and reviewing with some colleagues, this is mostly functional. There seems to still be an issue with retrieving the data (which is now stored directly to a label on the newitem object to cut out the global variable, which had issues) set with userinput. My more experienced colleague believes the code does not pause while the input box is open and that is the issue. He suggested making a custom GUI, but I am hoping there is a simpler fix

//call and drop new item
treenode itemn = dropuserlibraryobject(node("..>itemn",c));
Object newitem = itemn.as(Object);
//prompt user for item ID, store to variable, and write to labels
userinput(newitem.labels["labelA"],"Please input new item ID.");
string labelA = newitem.labels["labelA"].value;
newitem.subnode[1].labels["labelA"].value = labelA;
//make connections to external objects
contextdragconnection(model().find("ExternalObject1"),newitem.subnodes[1],"A");
contextdragconnection(model().find("ExternalObject1"),newitem.subnodes[1],"S");
//rename new item and return
newitem.name = labelA;
return newitem;

0 ·

Matthew Gillespie ♦♦ Adam C commented · Feb 12 2018 at 10:17 PM

Yeah, the userinput command doesn't stop the rest of the code in the function from executing.

Here's an example where I use a custom GUI made from the GUI builder to ask for user input. The GUI is set to be modal so you can't do anything else in the model until the name is input. The OnPress of the OK button calls a function on the library object and passes it the input name. That function then sets the object's name and label.

customgui.fsm

0 ·

customgui.fsm (14.9 KiB)

question