and while “XArrayName” and “UseIndexForAxis” values affect exported profiles as well as debugging in UI (parameters are set accordingly in the panels), “CompositeDataSetIndex” does not affect neither the exported profiles nor the UI.
Could it be a bug or maybe the command is misplaced in the script?
Looks like there is a bug in the way the widget is updated in the GUI when the command is run in python.
However the result (what you call “Exported profile” i suppose) should reflect the values used in your scripts.
Some of the profiles generated via “plotOnIntersectionCurves” are made up of multiple polygonal meshes, some of which contain a limit amount of data which I would like to skip and that’s why I’d like to control which one is selected for the export, but even from the script the “CompositeDataSetIndex” has no effect as reported.
I’ve just tried with the 5.8 release RC1 and found that:
1 - If I set CompositeDataSetIndex = [ ] the first polygonal mesh (out of 2) is selected in UI
2 - If I set CompositeDataSetIndex to 0, 1 or 2 the first polygonal is still selected in UI
3 - If I set CompositeDataSetIndex to 3 or higher no polygonal mesh is selected in UI