I’m looking into that now.. there’s probably some other logic stealing the control focus on tab.
I thought this should work the same way like entering Attribute User Text.
Thanks and sorry for the confusion.
Yes, it should, I just need to see what’s stealing away the focus. It’s most likely the command line and should be a simple fix.
EDIT, yes, it was the command line getting the focus. I’ve fixed it and get in the next release candidate. RH-87722
While we’re at it. When a key and value is entered as Attribute User Text for a model object referenced in Grasshopper, the recompute in Grasshopper is triggered after entering a key and then again after entering a value?
I think this has no benefit and the recompute should only happen after a value is entered. Now I get the problem one might add just keys but not values…
Anyway, I’m really looking forward to more options on what triggers recomputations.
Hmmm, I don’t think there’s a simple solution for that other than using the command line version SetUserText as each time you modify a key or value a modify object attributes event takes place, which Grasshopper responds to.
RH-87722 is fixed in Rhino 8 Service Release 21 Release Candidate
It appears to work as expected now. Thanks everyone who was involved!