I find Trigger "Travel to Object" Conditions because the versions different

Question

question

Steven Chen asked May 7, '20 Phil BoBo edited May 11, '20

I find Trigger "Travel to Object" Conditions because the versions different

Hello,

I found the condition "Travel to object" condition is because the version is different. I found the condition is because the version is different.

Can you assist in updating "Travel to Object"?

Thank you.

20.0 20.0.fsm

20.1 20.1.fsm

Software Version:

FlexSim 20.1.1

flexsim 20.1.1 travel to object

image003.png (56.7 KiB)

image001.png (19.0 KiB)

image002.png (19.7 KiB)

· 1

Joerg Vogel commented · May 11, 2020 at 04:18 AM

The difference comes from introducing a property of TaskExecuter class. gettasksequencequeue is still an old command of the pre-dot era. Dispatcher.taskSequences is an actual class property. It is time to change from commands to class methods and properties whenever it is possible. Otherwise we will never have an progress towards classes, if the picklist options don’t show the whole new syntax.

Probably you can use,

content(gettasksequencequeue(current)) == 0

but “content” is already deprecated, so will be “gettasksequencequeue” in one of coming versions.

0 ·

Answer 1 · 2020-05-10T16:59:25Z

Joerg Vogel answered May 10, '20 Matthew Gillespie commented May 11, '20

The source code header is wrong declared for the variable current. It is declared as Object, but it must be Dispatcher. Dispatcher inherits Object Class, but not other way around.

· 1

Joerg Vogel commented · May 10, 2020 at 05:04 PM

@phil.bobo, maybe you can put it onto the dev list to check the headers or to cast directly from Object to Dispatcher if properties or methods of TaskExecuter Class are involved. Many Thanks!

0 ·

Answer 2 · 2020-05-11T16:08:00Z

Phil BoBo answered May 11, '20 Phil BoBo edited May 11, '20

Thanks for pointing this out. I've added a case to the dev list.

In the meantime, you can press the down arrow to get the previous condition.

question