Do you think it's possible in the future to solve this linking behaviour ?
I have done some research and testing on this, and in summary, the Revit API does NOT allow a plugin to access a selected element in a linked file. The API will allow the selection of a linked file element, but it will not return the actual element the user selected in the linked file. This is explained in
http://thebuildingcoder.typepad.com/blo ... 69d0dd970b - with the relevant text being
RevitArkitek • 6 months ago
Any news regarding getting user selected linked elements? I wish to employ a tool where user may select a light fixture in host model or linked model first and then click tool to get info. But when selecting linked elements they are not recognized as being part of the selections set. I'm still in 2014. Thanks.
------------------------------------
Dear Adam,
That is a very valid question.
ActiveUIDocument.Selection.Elements cannnot return elements in any other document, simply because it would be returning duplicate elelement ids from multiple different documents, which would lead to great confusion.
In theory, there could be a way: UIDocument(linked_document).Selection.Elements could work, eventually; I do not think it does right now, though.
I don't even think we instantiating a UIDocument off a linked document is currently allowed...
Cheers, Jeremy.
So in summary, unfortunately assigning proxies to elements in a linked file is not possible.
Paul