hi @mkarimi, I continue my thread on testing markups, but I posted the windows testing in the iRHino thread,. Sorry I should have posted i there instead. Here’s the post:
I’ve tried everything, and came back full loop. back to trying Rhino 9 markup. wish me luck.
Can’t believe there aren’t very good programs for doing what type of markup I would like. So if I can figure out how to use Rhino for managing Gcode docs then it might work lol.
I really don’t want to have ta dust off my pen tablet
hopefully Rhino markup will let me draw bad curves and then smooth them out afterwards
is there a way to edit dimensions in the markup? I want to adjust text and arrow size, but can’t.
The relevant panel in properties does not show up when I select the dimension. Same goes for lines, I would like to be able to change line type, enable/disable arrows, …
When I double click a markup in the markup panel, it overlays over the current model using the markup’s stored view. That is a very nice feature. But i find the transparency slider very confusing.
It seems to range between “current model and markups” and “old model with no markups”.
“Old model and markups” vs “new model with no markups” could be better. Or better yet, separate sliders for model data and for markup data. Another good tool could be a vertical slider as on the picture below with old version on the left and the new on the right.
I really like the idea of a markup tool. Even in the WIP state it can do a lot of cool things.
If you select a markup object (during markup) you would get a widget that allows you to modify some of its properties. Like thickness (arrowhead size is tied to line thickness)
This seems like a bug, I logged here: RH-96158 Properties panel missing markup objects
Yes, cause my workflow at the moment doesn’t include a pen tablet so my curves will be silly looking, and indeed if I could rebuild the curves I draw then that would really help me be able to fix my mistakes.
I’m trying to remember the struggle.
Basically I went off into a different direction after all the trouble I had, and I literally had to teach my self very extensive skills in MS Word, in order to get done what I needed.
And if Rhino markup can’t ultimately do what I need then I’ll have no choice but use MS Word.
I literally researched the whole worlds internet and unfortunately MS Word was my best option at some point.
So, let me try to compile the design intent behind the project of marking up my CNC Gcode documents for other readers.
Basically it begins with the limitations of certain CNC controls. As a programmer you don’t always have the fortune of making the program as absolutely easy to read as possible for other users whom might need to look at the code.
So, what I’ve done over history is I will print out the code color coordinated and then add in my own hand written notes later on – to make the program appear more obvious in how it’s constructed.
That’s what I was trying to show here:
So for a machine operator or a newbie manager who might not understand the particular machine’s quirks can then better understand why the program is structured a certain way.
I’ll try to upload a real photo in a minute…
To be honest I also primarily do this for my self to better organize my own thoughts in order to save my time going forward, cause I never know when I’ll have to look at my code again and have to instantly understand what I’m looking at and why I wrote it the way I did.
So this is like a habit of mine to better adapt to the situation over time. I like to see clearly where the inflection points are and what the sections are doing in my programs.
I consider these copies with my hand written notes to be like the ‘master’ file per se.
I don’t always have full control over the alignment of the ‘comments’ (in parenthesis in this case), and am limited on the format and quantity on this particular machine.
Hence, the need for hand written notes due to limitations of machine control code format, etc.
Now for my main interest in trying to use Rhino markup, I’m imagining the ability to turn my little pen markings into editable entities in Rhino in order to copy paste and edit them to streamline my process and enable me to print many copies of this layout for other users of my code to help them better or more quickly understand the methods to my madness when they try to interpret these documents.
In a minute I’ll try to share what I came up with in MS Word…
For now, until I find a better solution, this is what I’ve got that shall suffice…I still feel however that Rhino can make it way better and more intuitive.
MS Word didn’t give me very much control over the squiggly brackets…