Hey everyone! First-time poster. I've been trying to find a work-around for this for a good bit.
Background: structural engineer designing house plans that need sheets for both a "right hand garage" (RH) version and a "left hand garage" (LH) version (which is pretty much the mirrored view of the right hand one). our files are old and kind of mashed together so text styles/scales can be different for even the same type of object.
We need both regular (RH) viewports on some sheets, and mirrored (LH) viewports on other sheets. To avoid copying the entire drawing in modelspace and mirroring it and then relocating the eye of the LH viewports to look at the mirrored copies, we have written a couple LISP codes to flip the VIEW perspective of the viewports on the LH sheets to Bottom (thus looking at the RH drawings from behind therefore mirroring them).
BUT, this causes all text to read backwards. We print the RH sheets to PDF first, and then we have created another LISP code to change the mirrtext property, flip all Mtext and Text in modelspace, and re-justify back to its original position, thus making it readable to print the LH sheets to PDF. (We undo that operation to make it readable again in normal RH view before closing out).
Our last problem to solve however, is that that LISP function cannot affect the text contained within a dimension string because mirrtext doesn't affect dimension strings, so all dimensions are still reading backwards on the LH sheets.
Right now our solution is making copies of the top view dimension strings, putting them on a separate layer, and then mirroring the location and pasting it on the bottom view to read backwards and vpfreezing the respective layers in each viewport.
To avoid having multiple copies of the same dimension string, is there a way to temporarily change the property of all dimension strings to read backwards on the top view so that they show up correct on the LH sheet bottom view?
I’ve attached a screenshot of the flipped viewport. Ignore the regular text that’s backwards, we already have a fix for that. We just need one for the dimension text. Any ideas?
