topic Re: Display & View Errors/Bugs in FlexSim Forum

Display & View Errors/Bugs

cphilpottX22K5 — Mon, 01 May 2023 15:36:42 GMT

[ FlexSim 23.1.0 ]

I am seeing some strange things happening here, and want to know if there are documented causes for any of the following:

1. There are names of process flow objects appearing in my model window. This is persistent through restarting and resetting to the default workspace.
2. I am getting the following error repeatedly in the system console:
1. exception: FlexScript exception: Array index out of bounds at VIEW:/active/MainPanel/BackPanel/SplitterXPane/ToolTabPane/TabControl/Toolbox/ToolsTree>eventfunctions/drawToolDelegate c: VIEW:/active/MainPanel/BackPanel/SplitterXPane/ToolTabPane/TabControl/Toolbox/ToolsTree
3. The display of the toolbox is not working correctly. (I think this may be related to the System console error)

---

I have been in and out of the model tree and creating sub-flows recently, but otherwise not doing anything that I would expect to create these errors. If sharing the model is required then I will need to create an alternate version without any of our client data and confirm that the errors are still happening. Any pointers in the right direction in the meantime would be appreciated.

Re: Display & View Errors/Bugs

jason_lightfoot_adsk — Mon, 01 May 2023 17:42:44 GMT

It certainly looks like the view's focus is the process flow. Reopen the default workspace. If it's the same then it looks like the model node may have been overwritten.

What things are you doing in the tree?

Re: Display & View Errors/Bugs

cphilpottX22K5 — Mon, 01 May 2023 19:22:19 GMT

Mostly browsing and looking for variables or labels that I can't see elsewhere.

Occasionally I will need to delete something from the model tree, but I don't know how these things get there. I made progress (or what I think is progress) on this issue, for example

...

(Image paste not working...)

I found in my model tree an instance of a Sub-Flow which was no longer listed in the Process Flow dropdown. That alone accounted for most of the display of these objects names in the model view.

The remaining objects that I don't expect to see are two decide objects and two source objects which also should not be in the top level of the tree. Deleting those seems to have fixed all of these issues.

Re: Display & View Errors/Bugs

jason_lightfoot_adsk — Tue, 02 May 2023 09:58:09 GMT

Where possible use the properties to configure standard objects and labels to customize them. Of course sometimes the relevant property does not exist - in which case variables might need to be accessed.

I'm not sure how your subflow got relocated. It's worth pointing out the danger in testing an object's location using the property 'up', where if you use = instead of == you will inadvertently change the location to the place you were trying to test for.

current.up==model()

can become

current.up=model()

and if current was a pointer to your subflow then it would end up in the model.

Re: Display & View Errors/Bugs

cphilpottX22K5 — Tue, 02 May 2023 19:36:00 GMT

That could very well have happened.

Re: Display & View Errors/Bugs

Jeanette_Fullmer — Sat, 06 May 2023 04:59:45 GMT

Hi @Chandler, was Jason Lightfoot'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 unaccept and comment back to reopen your question.