In Rhino 5, object select/deselect events did not trigger RhinoDoc.ModifyObjectAttributes. In Rhino 6, they seem to. This is problematic for my purposes because there’s no means to check whether or not that was the cause of the event - with actual attributes I can compare OldAttributes to NewAttribu…

To reproduce, try writing the following c# script in Grasshopper: private void RunScript(object x, object y, ref object A) { RhinoDoc.ModifyObjectAttributes -= Modified; RhinoDoc.ModifyObjectAttributes += Modified; } // <Custom additional code> void Modified(object sender, Rhino.D…

as @marcsyp figured out, it’s related to the auto-points-on behavior - if you window select (and control points don’t turn on) the event doesn’t fire. attn @dale @idid

Hi @andheum , [image] andheum: Is it supposed to be this way? The short answer is yes. When “auto points on” is enabled and you pick something that qualifies for having it’s control points turned on, Rhino adds some super-sneaky data to the object attributes so it can determine what objects …

[image] dale: Is this a huge problem or just an annoyance? If I may chime in: I think it a non-trivial issue as there is apparently no obvious means anymore to distinguish between selecting and modifying . So it’s now up to the developer to sift through the attributes and find a change if th…

We sorted this out in a very brutal way: if ( Converter.getBase64( e.NewAttributes ) == Converter.getBase64( e.OldAttributes ) ) return; inside the event. Full code here . There probably is a faster way…

Or, could the args object have a “ChangeKind” attribute (or similar) to specify what sort of attributes change triggered the event? This would be ideal from my point of view - in the handler I can just filter on that property and figure out if the given change was one I intended to react to.

I agree – if the attributes data can become less sneaky (i.e., exposed) then it would allow for a much cleaner decision tree and also support the case where for some reason you need to know if the selection of an object has triggered a parallel event in the Rhino UI (e.g., GripsOn). Distinguishing …

I’ve logged issue for this. https://mcneel.myjetbrains.com/youtrack/issue/RH-45106 – Dale

Change in RhinoDoc.ModifyObjectAttributes?

Rhino Developer

andheum (Andrew Heumann) March 26, 2018, 9:02pm 2

Seems this was reported before? Rhino Beta: `ModifyObjectAttributes` triggered on selection/deselection of NurbsCurve-like objects

Topic		Replies	Views
Rhino Beta: `ModifyObjectAttributes` triggered on selection/deselection of NurbsCurve-like objects Rhino Developer rhinocommon , bug	6	1139	December 11, 2024
ModifyObjectAttributes not triggering? Rhino Developer	10	1474	October 21, 2025
Event handling - ModifyObjectAttributes triggered by AddRhinoObject Scripting windows	3	93	February 17, 2025
RhinoDoc.ModifyObjectAttributes fired after each object attribute change Rhino Developer rhinocommon , event_handling , rhino6	1	599	April 24, 2020
Where to register hiding Rhino object event Rhino Developer windows	1	208	February 27, 2024

Change in RhinoDoc.ModifyObjectAttributes?

Related topics