Observers and deleted entity information work around

DanRathbun · June 28, 2021, 6:43pm

#delete_key is an instance method of the dictionary class.

Most things you use #delete_attribute on, inherit it from it’s definition in the Entity superclass.

But not models. The Model class is not an Entity subclass, so it’s #delete_attribute method is unique (and is actually not documented.)

ADD: The difference in behavior will likely be avoided if you attach dictionaries to either the DefinitionList collection or your Definition objects. Both are Entity subclass objects so would inherit the #delete_attribute method that works.

DanRathbun · June 28, 2021, 6:59pm

I did not see an open issue, so I logged it:

github.com/SketchUp/api-issue-tracker

`Sketchup::Model#delete_attribute` undocumented and differs from `Sketchup::Entity#delete_attribute`

opened 06:58PM - 28 Jun 21 UTC

closed 07:43AM - 29 Jul 21 UTC

DanRathbun

Ruby API SketchUp

#### SketchUp Ruby API Issue `Sketchup::Model#delete_attribute` is undocument…ed and it's behavior differs from [`Sketchup::Entity#delete_attribute`](https://ruby.sketchup.com/Sketchup/Entity.html#delete_attribute-instance_method). REF: https://forums.sketchup.com/t/observers-and-deleted-entity-information-work-around/166128/15 Attempts to delete an attribute from an existing non-Trimble dictionary attached to a model object **fail**. Coders are forced to access the dictionary's [`#delete_key`](https://ruby.sketchup.com/Sketchup/AttributeDictionary.html#delete_key-instance_method) method instead.

tt_su · July 29, 2021, 7:44am

Just to echo my response in the GitHub tracker:

Sketchup::Model have no delete_attribute. This is one of the unfortunate monkey-patches Dynamic Component adds. Extension authors should not rely on it.

DanRathbun · July 29, 2021, 3:09pm

And also echoing, that monkey-patch doesn’t do anything because it was always written with a bug in it, and wrapped in error trapper block that suppressed any exception being output to the console.