Hi Brayton -
FWIW, decades of using MCAD programs have me keeping modeling and drafting completely separated by making all annotations (linework?) on the layout instead of in model space.
-wim
Hi Brayton -
FWIW, decades of using MCAD programs have me keeping modeling and drafting completely separated by making all annotations (linework?) on the layout instead of in model space.
-wim
I had always dismissed annotations in layout space because of the likelihood of breaking my entire drawing set if I need to move the model, as well as the relative difficulty of using Grasshopper to generate geometry in layout. Maybe I should give it another look.
Hi Brayton -
Please do. Mikko has quickly fixed issues with broken annotations in the past, and this should be getting rather robust now.
-wim
Yeah, I’ve always avoided doing that in Rhino. That doesn’t seem like a very good idea in Rhino.
The only time I do that in Rhino is for simple text or a quick temporary dimension workaround for a faster printout.
In Rhino I prefer keeping 99% of entities on the workspace layers.
Rhino’s layouts seem very underdeveloped still even after all these years. Not to mention the new bugs.
I don’t recall seeing a bug report from you about annotations on layouts getting broken…
-wim
Indeed, I could probably put more effort into making my perspective clear I would agree, but please see this as an example of some of my effort, while I’m not yet sure if this has been corrected atm:
I was working on another thread and stumbled on anew way of seeing these bugs in active detail views:
I can still look into this and maybe work on a new thread that investigates things I could be imagining, to be sure there’s any ongoing issues. This one here was mostly about the grid and not necessarily annotations per say. So for now this is mostly relative to grid/layout matters from the past which may or may not be associated with the present. Hopefully soon I can do more testing.
In the meantime, it’s not like I haven’t tried, but I’ll plan to tryhard er:
Just wanted to share this with anyone it may concern.
This isn’t necessarily an example relative to vector vs raster, but rather print regular vs print to pdf:
See the following:
Screenshot showing dimension lines that are hidden due to invisible shading
Compare above screenshot to the following print to pdf:
angle plate.pdf (169.7 KB)Supplemental screenshot of pdf:
fortunately the pdf came out nicer than the layout views indicated in Rhino
Not sure if the disparity is related to dpi settings… It would be nice if Rhino could display the dimension lines better, considering there’s no shading that should hide them.
Indeed, I could probably put more effort into making my perspective clear I would agree
FWIW, in the threads that you link to from here, I literally have no clue what you are talking about. It would really help if you could just provide a 3dm, and clear “step 1, step 2, step 3” instructions. I suppose I could spend a few hours trying to decipher them as they are but there are currently 2964 other threads that I need to get through…
-w
Fare enough.
I don’t recall seeing a bug report from you
I literally have no clue what you are talking about. It would really help if you could just provide a 3dm, and clear “step 1, step 2, step 3” instructions. I suppose I could spend a few hours trying to decipher them
I’ll keep it in mind for the future when I have more moments to provide my 2 cents hopefully in a more clear self evident and irrefutable manner.
In time we’ll get through it together. It’s possible things I’m imagining still might’ve already been improved. I’ll see when I get there.
I’ve put this one on the list as RH-85633 Print: Fake2D Clipped Edge Gets Layer/Object Color
This link appears to be broken. I get a 404 error when I follow it.
Hi Brayton -
I get a 404 error when I follow it.
Thanks. That’s now open.
-wim