I recently changed my Aliases for the polyline, which has some unforeseen consequences for the content cache component.
Notice the difference in Aliases between:
P for: * ! _PolyLine
P + L for: ! _PolyLine
If I repeat the Polyline command in an Alias, Content Cache never actually resolves, thinking a command is still running. My scrip relies on detecting whether there is new geometry in a specific layer to automatically add User Text attributes. As a result, the attributes are not added, forcing me to manually trigger an update to the component.
The interesting thing is that the same thing happens when I perform extend, however, it does actually trigger an update for the content cache when I press enter. So shouldn’t the component also update when I finish the Polyline command?
Reason I changed the hotkeys was for Instant Aliases to work more akin to Fusion, where I repeat commands until I activate another or cancel.
Also can we get the definition and the file that is being used.
I can see that using Grasshopper to actively respond to and event like adding a new object to the file or updating and object could get quite confusing for Grasshopper. Normally we would use a plugin event watcher in C# or something to respond to any object added or updated in Rhino and then post processing of all objects could be custom.
Anyway, we do need to look at the specific logic in this case to see how it is falling apart.
For the longest time during the Rhino 8 WIP I have been using similar logic and only now that I’ve changed my hotkeys does it break down. In any other circumstance it works fine.
