I got confused as that corner is related to a curve which I didn’t select. But I realized that Rhino somehow fillets that corner instead because it cannot create a fillet with radius 50 mm with the curves I was trying to do.
I would expect in this case to get a message saying “Cannot fillet this curve with this radius” or something, rather than filleting a different corner than intended.
Looks like you can’t fit a fillet that big in that area and Rhino places it at the closest location where it can fit. What if you do the exact same thing but change the fillet radius to 5?
Yes @Thestripper, that’s what I wrote in my original post:
5 mm works fine, but that’s not the point. The point is, Rhino shouldn’t be filleting a different corner just because the corner I want to fillet doesn’t work with the given radius. Now the affected corner was in my viewport, but imagine this happening outside your view without you realizing.
Yeah, no I get what you are saying. I would add as a general rule of operating Rhino that it’s a good thing to keep an eye on your command line history and Undo any command that seemed like it had no effect. Because, just as you say, if you execute a command that for any reason seems like it did nothing it’s a good practice to undo that command. This is because something in your work might have changed that you did not intend and it may have happened outside of your viewport and you don’t notice until later.
To Rhino’s defence this time however, the mistake was a draftmans error.
If you want a fillet there and you want it as big as possible you could try using the “Curve>Arc>Tangent to Curves” command.
Hi Simen. I’m sorry if you think I was condescending. I can assure you that it was not my intention. I was just trying to be helpful because I know how frustrating it can be to get hung up on things in drawing. My remark about this being a draftsman error to begin with might have sounded a little harsh. I was not trying to be mean or condescending towards you. But because it’s not possible to fit a fillet that big in that area, it is to begin with a draftsman error. Rhino is of course at fault for placing a fillet at random in a place that you did not specify. It should instead give you a warning that it can’t fit a fillet there. Just as you said further up and Gijs also linked to.
That might seem like a good rule, but remember you are dealing with a very dumb critter here - the Rhino (no offense intended towards the animal of the same name).
If you undo a command that had no result you will undo the previous command.
Of course the command line will tell you what command undo just wiped out. So yeah, you have to constantly watch the command line to figure out whats happening, always.
In reality, having to constantly and incessantly watch the command is not a good thing for users. Its a sign of developer incompetence. Rhino should be consistent in its behavior so that once you learn how its programmed to work you should not have to constantly watch the command to see how it works. When something like this does not work in a predictable and logical way the user is forced to do extra work to overcome developer’s incompetence.
It would not be very difficult to program Rhino so that if a command fails and the users hits Undo that the response would be “no undo, the last command failed” instead of wiping out the result of whatever command preceded the last command.
Only if there is a button to deactivate such warnings. Rhino could have an ‘education’ mode where all these warnings pop up and a ‘work’ mode where warnings are deactivated by default.
Its not a warning its documentation of what Rhino is doing. That is what the command line feedback does.
If you draw a line and run Undo command, Rhino command line tells you that it is undoing the line.
If a command fails and you run undo Rhino undoes the previous command.
What it should do is tell you that the command you are trying to undo failed instead of undoing the previous command. Of course, when the user moves on to another command then the failed command should then be removed from the undo stack.
Adding to this bug report here is another example. The points are where to pick on the curves
Fillet ( Radius=1 Join=Yes Trim=Yes ExtendArcsBy=Arc) weird_fillet.3dm (42.6 KB)
