Let us say : there is, but it is not out in the wild.
Also, it has a wider approach than just listing the names: it also targets "doublettes hygiene", "altered paths" reconciliation and possibly a "find a model from those I posess with suitable likeness to one I don't posess" feature ; the latter two aimed at .fpm files you might receive from others.
The core - of course - is an analyzer scuttling down the entitybank directory subtree and recording what .fpe files and corresponding .bmp icons it finds, so, later, the program can answer search requests by not only showing the name(s) with
the "paths" to find them, but also what they look like [imagine how many items you will get as a result if you search for "build*" or "barrel*", just names are not efficient here].
The bad thing is that the user has to initiate a (re-) scan manually now and then to update the internal list, because there is no known way to learn automatically that GG "just has downloaded a few new models". I'm trying to speed up the scan process by evaluating the editors\downloadinfo directory, but ....
And the worst thing is there is no way to get the path found over to GG's editor, the user has to manually follow the path displayed in GG's editor.
The search facility is currently limited to just a single partial string search in the objects' names - so, it is VERY basic.
A feature to assign and maintain searchable custom attributes is still not implemented; it probably would at least mean employing sqlite as a background database.
I would really like some input on the following questions before I release something to the public:
* Will users actually take the trouble to maintain custom attributes ?
Probably not if there is not an easy feature to select a number of entries and mass-assign attributes ?
* how many user defined attribute columns are useful ? Are "5" ok, too many or not enough ?
* Is the author's name of a model a useful search attribute at all?
[edited 1 time]
Lives of great men all remind us we may make our lives sublime