While creating the attached demo file I´ve also noticed that Grasshopper Player somehow caches the selected objects from the prvious run, when you open the GH file in the grasshopper window instead of using Grasshopper Player. That´s definetly no desired behaviour. At least not for me.
What about the second observation I’ve mentioned?
With the selection being persistent even after a run of the gh player is completed?
Is this also resolved with 8.17?
When you run the player Grasshopper loads the picked .gh file, if is already open it uses the open instance. Then it asks for the inputs and solve.
If the file was open you still have the last solution there.
If you have it open is because you are doing changes to it that you want to test on each play.
Next time you play it, will ask again for every contextual input.
So this is meant to be a feature?
Or at least something coherent with the logic of GH in general?
One can potentially use it for adapting the GH defintion without having to use the input parameter for any “Get *” component instead?
Is it meant to be like debugging with the breakpoint at the very end of the defintion?
I´m just confused, that non pre-defined user input at the start of a run doesn´t necessarily gets removed immidiately after a run.
I´ve had some issues in the past with persistent unwanted previous selections while exchanging GH player definitions with co-workers. But back then I didn´t spend time investegating further, because the “anomaly” could be resolved quite quickly with some Undos, Redos, Closes and Saves of defintions. Unfortunately I can´t reproduce an exact case at the moment at this point anymore.
But once I will expirience something odd again I will keep you posted.
At least now I have a bit more understanding of what the mechanics behind could be. So that already helps.
