Bug - Parameters, On Set event is triggered before value changes

Question

question

Gui Vaccaro asked Jan 27 2025 at 3:09 PM Jason Lightfoot answered 10 days ago

Bug - Parameters, On Set event is triggered before value changes

Hello,

In the Parameters tables the OnSet trigger is fired at the first OnKeyDown, hence before the value is changed. As a consequence, on set code is executed mistakenly. This becomes worse if one uses the parameter as "Option". In this case, to access the options, a double-click is necessary, firing the event before any option appears. On that note, why would a double-click be necessary if there is already an "Edit Mode" feature in the parameters table as for other dashboards: when not in edit mode, the simple drop-down should suffice.

Thank you for any clarification.

Software Version:

FlexSim 25.0.2

bug report parameters on set

1737990502433.png (128.5 KiB)

1737990534245.png (98.6 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 · 2025-01-31T15:34:33Z

Jason Lightfoot answered Jan 31 2025 at 3:34 PM

I normally would add the condition if (isReset) which gets me through any issues since I want to reset the model when making such changes. I agree the timing /sequence and population of old/new values has not always matched what might be expected and I believe the developers are aware of this.

· 3

Gui Vaccaro commented · Jan 31 2025 at 3:42 PM

Hi, @Jason Lightfoot ,

thank you once more! I will try it again, but it would be great if the interface worked better in this case. Having the trigger set before the change happens and dealing with two drop downs increases the complexity way too much.

0 ·

Jason Lightfoot ♦♦ Gui Vaccaro commented · Feb 07 2025 at 2:33 PM

Noted - I've linked this post to the issue in our tracker - if there's some movement relating to this we may get an update in this post. Has the isReset flag allowed you to get past the issue for now?

1 ·

Gui Vaccaro Jason Lightfoot ♦♦ commented · Feb 07 2025 at 10:09 PM

Absolutely. Thank you.

0 ·

question