Open bitsy opened 4 months ago
Also, happy to share my work-in-progress code... should I paste here, or would a pull request be more appropriate?
Hi @bitsy , thanks for your feedback!
You can go ahead by making the pull request, so that we can review and comment on specific parts of the code it there's the need to.
Awesome will do! Sorry for the late response, just trying to tidy up and test the code a little more before I post. @sanzoghenzo, which branch should I fork for this pull request?
you can use the develop-4
branch.
✈ Pre-Flight checks
🐞 Describe the bug
This command is so close to working, but there's one major issue I've run into while using it: it copies reference planes in each source legend view to the model space in the destination project. From a quick Google search, this appears to be a common issue with the way Revit handles copying/pasting reference planes in legend views.
I noticed this when I copied about 30-40 legend views to another project and wound up with nearly 300 new reference planes in my model (visible in plan view). We use reference planes in legends in our office template so that you can snap the legend views to guide grids on sheets and so that we have consistent graphics/alignment of legend components.
⌨ Error/Debug Message
♻️ To Reproduce
⏲️ Expected behavior
I expected all elements including ref. planes in source legend views to get copied to the destination legend views with correct subcategories assigned to reference planes.
🖥️ Hardware and Software Setup (please complete the following information)
Additional context
In the "Hardware and Software Setup" section, I substituted my username with
%USERNAME%
.I've written a solution to this problem but could use some feedback. It basically involves recreating new reference planes in the destination legend views that match the properties of the source reference planes. I'd like to initiate a pull request but wanted to be sure I'm not missing some important context or previous discussions. It's my first time posting an issue here.