Syntax error when adding pick option

Question

question

Shinya O asked Jul 19 2023 at 2:15 AM Shinya O commented Jul 27 2023 at 1:44 AM

Syntax error when adding pick option

Hi,

I encountered a syntax error when adding pick options.

It looks like there's something wrong with the auto-generated flexscript.

This phenomenon was found in FlexSim2021.0 and was not improved even after converting to FlexSim2023.0.

It's also strange that the "{" is green because there are no blank lines on lines 65 and 66 of the On Arrival Trigger in DP1.

I would like to explain this phenomenon to my customer, do you have a good explanation?

Thanks in advance.

DP_sample.fsm

Software Version:

FlexSim 23.0.8

pick option desion point

1689731883714.gif (1.2 MiB)

1689732774288.png (25.0 KiB)

dp-sample.fsm (36.5 KiB)

· 2

Jason Lightfoot ♦♦ commented · Jul 24 2023 at 4:41 PM

Hi @Shinya O, was Kavika F's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.

0 ·

Shinya O Jason Lightfoot ♦♦ commented · Jul 25 2023 at 12:02 AM

I am waiting for @Kavika F 's reply to my post.

0 ·

______

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 · 2023-07-19T14:51:18Z

Kavika F answered Jul 19 2023 at 2:51 PM Shinya O commented Jul 27 2023 at 1:44 AM

Hey @Shinya O, for the first issue, I can replicate your error with the model you've provided, but I can't seem to replicate it with a new Decision Point I drag out from the Library. I'm using v23.0.9, and the panels look slightly different when you select the different DPs. Also, if you remove some of the existing triggers and add them back, it seems to work fine. Is there a specific set of steps that you take to produce this error consistently?

For the second issue, that seems to be a visual bug considering the code still runs even with that "commented" curly brace. I'll add that to the dev list - to fix the syntax highlighting in that scenario. Thank you for pointing this out.

· 4

Kavika F ♦ commented · Jul 19 2023 at 3:55 PM

Upon further investigation, it seems that there's a bad spacing character in the code. If you delete the last two back-slashes (\\) from line 91, you'll notice that the curly brace on line 92 is no longer green. This also fixes the syntax error you get after adding the "Enter Restricted Area" PickOption.

0 ·

1689782037373.png (7.7 KiB)

Shinya O Kavika F ♦ commented · Jul 20 2023 at 6:11 AM

For the first issue, I do not know how to reproduce this issue with a specific procedure from a new model. There is no information other than that it was created by some procedure using FlexSimJapanese 2021.

For the second issue, thank you for your reply. I hope the visual bug is fixed soon.

I found that by opening the code of the On Arrival trigger in the corresponding model and pressing "Apply", no syntax error appeared. For some reason FlexScript fails to compile properly?

0 ·

Kavika F ♦ Shinya O commented · Jul 26 2023 at 3:46 PM

Hey @Shinya O, the two issues are related. The visual bug is caused by the same thing that is causing the flexscript compilation error. To avoid this, do as you said and hit "Apply" to get rid of the error. The dev team has opened a case for this already.

Is there something else you had a question about?

0 ·

Show more comments

question