Adding new button in ExtraPanel and making space for him from a module

Question

question

Valentin R asked Jun 13 2019 at 9:59 AM Valentin R commented Jun 27 2019 at 8:14 AM

Adding new button in ExtraPanel and making space for him from a module

Dear reader,

I'm trying to add a new custom button to my flexsim's interface (In the ToolPanel) from a module. I've been inserting it "by addition" from my module which works quite well. However, the next elements on the ToolPanel still need to be moved in order to make space for it. I've then selected the spacialsx of the ExtraPanel, the spacialx of the divider4 and the spacialx of the UserPanel and added them "as replacement" to my module. Then I changed the values:

spacialsx of the ExtraPanel from 273 to 323
spacialx of the divider4 from 836 to 886
spacialx of the UserPanel from 848 to 898

and used the save defaults to try applying the changes. The result of this manipulation can be see on the picture below.

capture.png

I must be doing something wrong because, as it can be seen, the values in the "replace" of the module are still the initial values and only the value of spacialsx of the ExtraPanel has been changed as I wanted. Do you have any idea about what the problem is in this case ?

Thank you all for your consideration,

Val

Software Version:

FlexSim 19.1.0

module button toolpanel

capture.png (102.5 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 · 2019-06-13T20:03:29Z

Matthew Gillespie answered Jun 13 2019 at 8:03 PM Valentin R commented Jun 27 2019 at 8:14 AM

Lines 215 - 219 of MAIN:/project/exec/globals/nodefunctions/savedefaultviewproject is setting those values to hard coded numbers. I removed those lines for the 19.1.1 bug fix, so you can either wait till then or you can replace that nodefunction and remove those lines yourself.

· 4

Valentin R commented · Jun 17 2019 at 10:41 AM

I used the module replace function to replace the values where you mentioned them. Once I "saved default", the modification took place and everything looked as I wanted it. However, if i close FlexSim and reopen it, this modification is not taken into account. At that point, if i simply "save default" it does apply the modification as I want it to. Looks like the openning routine of FlexSim does not act the same way as the interface reopening routine of the "save default" ... Do you have any idea about what is happenning there ?

0 ·

Matthew Gillespie ♦♦ Valentin R commented · Jun 19 2019 at 10:52 PM

I just tried this on 19.1.1. (It's released now so you don't need to replace the savedefaultviewproject node anymore) It all works fine for me. Are you sure your changes actually got saved? Do you see the nodes in your module's installdata node?

Also I would recommend adding your own toolbar panel instead of adding an item to the Extras panel. This is because the toolbar panel finds the biggest item and sizes all the other items to be the same size. You can see when you hover over the new item you added to the Extras panel that the blue box suddenly cuts off on the right side. And if you were to add two small items to the panel you'd get a big gap between the two.

1 ·

Valentin R Matthew Gillespie ♦♦ commented · Jun 26 2019 at 9:34 AM

Thank you very much, I tried the 19.1.1 and it works well for the button problem. I still encounter a new error that appeared after some time working on my module in the 19.1.1 version (cf. screenshot linked capture-error.png ). This error appears when opening the FlexSim 19.1.1's version which contains my module. Is this one appearing because the "module SDK" I used was the one of the 19.1 version ?

0 ·

capture-error.png (95.4 KiB)

Show more comments

question