WRT to my 'hijack' request, the first part anyway ...
I have a similar need - to create diagram / view based (rich text) documents that pull element details from wherever the elements are, i.e. a document based on a diagram and the elements on that diagram *not* based on a package. I can't find any examples of that but I'm sure there must be a way.
The advice above gives me part of what I'm looking for - I can now generate a document and include elements from outside the package the diagram is in (and with filtering I can control which of those I include) :-)
But, is there a way to limit the scope of the document to the currently selected diagram ?
If the diagram is in it's own package I get what I'm after, however if I move it into a shared package the document includes all diagrams within that package.
So, specifically, what controls the 'scope' field - the first field of the Generate Documentation dialog?
- If I choose a package that field name is Package and I can select any package I want; the document is generated based on the full package
- If I choose an element on a diagram or in the browser, that field name is Element and has the name of the currently selected Element; the document is generate on the element only
- If I choose a diagram (click on the diagram itself or select on the browser) then the selection changes to Package when choose Generate rich Text Document and does the whole package not just the diagram