Copy the pull strategy is impossible when using 'Edit Selected Objects'

[support5CRPZ]

[ FlexSim 17.2.3 ]

I can't copy the pull strategy using 'Edit Selected Objects' pane.

It's possible only using All Variables copy.

Is it right?

P.S It same in 2018 Beta.

[jeff_nordgren · Accepted solution]

@david.seo

Seems to work fine for me. The only this I have issue with is what the "Pull Strategy" is referred to in the list of variables. If you use "receivefromport" as the variable name, it will copy the Pull Strategy. For me, that isn't real intuitive but that's the one that works. Maybe a "rename" of that variable (and maybe others as well) is in order? Just sayin'. @Matthew Gillespie, @Matt Long, @anthony.johnson

[support5CRPZ]

Thanks @Jeff Nordgren'

@Matt Long, @anthony.johnson, @Matthew Gillespie

I think the variable name of Pull Strategy is "Pull". I found 'Pull' is the check field of Pull Strategy. I want to know which trigger is 'PullContinuous'?.

Yes. some variable names are not intuituve to the user not using English. I want the variable names will be changed to the same trigger name.

For example cycletime is 'ProcessTime'. Thanks.

[philboboADSK]

For backwards compatibility reasons, renaming the variables is infeasible.

If you use the sampler in a Script window, you can hover over the various widgets in the Properties window to learn what variable they are connected to.

Perhaps we should update the Copy Variable UI so that you can sample the widgets to select their variable name. We would need to update it so that it works with code fields as well, and not just edit fields, checkboxes, and dropdown menus.

[support5CRPZ]

Thanks. @phil.bobo

But Input fields like Pull Strategy have not the Sampler button in the Quick Property.

[jeff_nordgren]

@david.seo

The "pullcontinuous" variable in the Copy From Highlighted variables area, points to a node in the "variables" of the object called "pullcontinuous". But that variable does not show up on the GUI for the object. I believe it is a backwards compatibility issue and that node is no longer used.