I think, it is a rather 'half-cooked' solution. Firstly, it's not a cross-platform solution and secondly, it's based on 'physical' path of the file. What about searching in the AC internal database of LOADED libraries? That is what I would expected from such a add-on. That would tell me whether my object that I am looking for is loaded in active libs or has to be loaded (optional dialog box).
So outcome would be variable values:
0 = not in loaded libs (optional dialog window to allow loading it in)
1 = loaded
example:
I have a lib part that calls macros. Macros are localised versions, so macro files are called differently like macro_AUS.gsm, macro_UK.gsm, macroblabla. I would like to be able to 'switch' the script to a macro currently present in loaded libs. That would make localisation (for example) so easy.
