[Plugin] AttributeInspector 1.1.1 – 2014-05-08

TIG

I'll re-add it for you.
If you can add an RBZ you can add the other file type?
Are you making it v8 ?
You either have to do a save_as v8 after making it in v2013 - and remember to get/use with the alternative tool that's available from the Authors' Guidance page for v2014.
When we finally move over to the newer PluginStore version only an RBZ upload will be needed for both Download/AutoInstall...
But while there are both versions working for users we need the alternative format....
Users will be forced to migrate to the newer version once it goes public after beta-testing is finished...

jiminy-billy-bob

@aerilius said:

I updated to 1.0.1, now with more entity types in the UI.

Nice! Love it

EDIT : Really usefull

Anton_S

Useful plugin, AE.
The dialog looks professional, as well.

Thank you!

jiminy-billy-bob

I'll repeat myself, but this plugin is really great!
It's more than usefull for debugging my plugin

Thanks again for this!

inteloide

Perfect plugin Aerilius !!!

I wanted to write a plugins similar a long time ago, but you do it before and better than me !

Thank you soooo much !

Inteloide

jiminy-billy-bob

When changing the value of an attribute of a layer, the attribute vanishes.

Aerilius

I cannot reproduce this. What steps to reproduce it? What is the dictionary, attribute and value?

jiminy-billy-bob

@aerilius said:

I cannot reproduce this.

Suddenly, I can't either! Just as I was about to record it.
Well, if it happens again, I'll get back to you.

jiminy-billy-bob

I get this in the console whenever I open the dialog in SU2014 (Win7). It works fine, though.
It happens even on brand new files.
I don't have this in SU2013.

AEAttributeInspectorDialog Error for callback 'get_title'; 
undefined method `typename' for #<Sketchup;;Model;0x8a58710>
C;/Users/Marjorie/AppData/Roaming/SketchUp/SketchUp 2014/SketchUp/Plugins/ae_AttributeInspector/AttributeInspector.rb;407;in `get_title'
C;/Users/Marjorie/AppData/Roaming/SketchUp/SketchUp 2014/SketchUp/Plugins/ae_AttributeInspector/AttributeInspector.rb;303;in `block in create_dialog'
C;/Users/Marjorie/AppData/Roaming/SketchUp/SketchUp 2014/SketchUp/Plugins/ae_AttributeInspector/Dialog.rb;199;in `call'
C;/Users/Marjorie/AppData/Roaming/SketchUp/SketchUp 2014/SketchUp/Plugins/ae_AttributeInspector/Dialog.rb;199;in `action_callback_wrapper'
C;/Users/Marjorie/AppData/Roaming/SketchUp/SketchUp 2014/SketchUp/Plugins/ae_AttributeInspector/Dialog.rb;152;in `block in <class;Dialog>'
-e;1;in `call'

#<Sketchup::Model:0x8a58710> is the active model (in case you're wondering).

Dan Rathbun

Sketchup::Model#typename() is added into the API by "dcutils.rbs"... so turn the DynamicComponents extension back on, and you will no longer have the errors.

Dan Rathbun

Also.. I would like to say that I wrote at least one plugin which I purposely added a AttributeDictionary to a collection object, because I did not want the user messing with it, or having it included in an attribute report.

Dan Rathbun

Another think that throws me off a bit, is that I am used to the +/- buttons being on the top toolbar, in the Scenes and Layers managers.

BUT.. I like it, mainly because I myself thought about doing this, but never had the time to do much more that the simple lister pluglet for the GeoLocation dictionary.

jiminy-billy-bob

@dan rathbun said:

Sketchup::Model#typename() is added into the API by "dcutils.rbs"... so turn the DynamicComponents extension back on, and you will no longer have the errors.

Thanks!

Aerilius

The bug has been fixed some time ago in the (not yet released) next version. I'll publish it soon.

Dan Rathbun

v1.0.1

When I choose "materials", nothing happens. (I should see a blank list when no dictionaries are attached to any material in the model.)

Should materials not having dictionary attached be displayed but grayed out ?

Dan Rathbun

Clicking (giving focus to) the edit boxes in the righthand pane, cause the row height to increase (by differing amounts, depending on whether the attribute name or value box gets focus.)

genma saotome

Hi Dan, would it be possible to expand upon this idea and code up something that will find all elements that match an attribute value? AFAIK there isn't a way to find faces that have no materials applied... and I have a plug-in I use all of the time that makes use of the dictionary to hold an assigned value (always about faces) but if I decide to change that value I have no way to tracking down all instances except by recollection and/or trial and error. So being able to do this attribute --> this value --> show me all that match would be very handy for me. By "show" it would be adequate to show the attribute information but I think it would be better to select them instead.

I think anyone else who uses the dictionary feature might also benefit because those data are not part of SU's own selection function and your plug-in, as it is now, does reveal that data. I think taking the next step and figuring out how to do a select based on Dictionary attributes and their values would be a big plus.

Thank you for any consideration you give this.

Dan Rathbun

@genma saotome said:

Hi Dan, would it be possible to expand upon this idea and code up something that will find all elements that match an attribute value?

ThomThom's SelectionToys plugin can modify your selection set by many filters.
There are at least 4 filters regarding add or remove objects according to front/back material set as default ( nil.)

So first you window select a bunch of objects. Then use the SelectionToys face filter, so only faces remain in the set.

Then use the default material filter for front faces, and/or back faces.

Install manually via
http://extensions.sketchup.com/en/content/selection-toys
or using the ExtensionWarehouse dialog from within SketchUp 2013 and higher. Navigate to ThomThom's page, and scroll down to SelectionToys

Aerilius

A lot of the ideas are things that I had found and added myself, others did I integrate now. Sorry that I still haven't finished/published the update because I want to be sure the quality is right.
(Some extension stores have longer update cycles, so when I discover an overseen issue, I can't publish a quickfix.)

As for searching within the selected entities by attribute, I had thought of that idea, but decided not to get distracted but focus first on the main function of reading/editing attributes. One could certainly add a lot of ideas, but to make a "good" user interface one needs to carefully think about user workflows and how a feature affects the plugin's complexity (of UI and code). I'm not yet sure if search is something that I should better leave for thomthom's Selection Toys.

Checking an entity for a "direct" property is on thing, but speed would also be much more affected for attributes, when you consider every entity can have multiple dictionaries, with each mutiple attributes/values. And Christina found that attribute dictionaries can have their own nested attribute dictionaries…

jiminy-billy-bob

Have you considered browsing through the read/write_default stuff?