Versions afftecte: Beta, Rhino 7, Rhino 6, doesn’t matter. Been there for a while, got asked for a 3DM file last time, you don’t need one.
Select any object, doesn’t matter what it is. Edit it’s name in the properties. Because of the annoying behavior of the name field in the properties (also discussed previously) it remains highlighted when you hit enter (and it shouldn’t, as any text you type afterwards renames it, when you THINK you are entering a command. The number of objects I have in projects that are named “move”, “copy”, “CPLane” etc is off the hook, and is particularly frustrating as I tend to name things for a reason so when I come back to them I remember why this line at a goofy angle having out in space was for amidst all the other construction geometry, but I digress.
With the utterly annoying name field still highlighted, select export selected from the file menu.
Blammo, death by annoying Name Property Field.
Does not matter what version, Been there since V6. Doesn’t matter which Mac OS version.
You do not need an uploaded model file to reproduce this, it happens all the time, specifically any time you rename something (which I always do right before exporting it as 3MF) and FORGET to click on something else to kill the accursed “remains highlighted for no good reason” name property text field.
Rant mode offf.
Sorry, just had it happen again for the 3rd time today, and was annoyed.
I suspect the crash is because the name property text is SELECTED and when you hit “export selected” it’s somehow thinking the text fields selection is a model and pukes at that point.
It turns out Mac crash reports can’t be processed automatically like Windows reports can. That’s why I can’t find any.
I tried it again.
Drew a box, named it, changed it’s name, and with the name selected, I ran ExportSelected by using the ExportSelected under the Save icon.
I tried ExportSelected again from the File pull-down menu, and did get a crash.
@LewnWorx
The developer identified the problem and just checked in a fix.
I’ll be able to test that fix later this week.
My guess is it will be included in the 7.3 service release.
Any particular thing mac users need to do to ensure the crash reports are being seen? I was utterly unaware that the hundreds of crash reports I’ve sent in over the past few years aren’t being seen, just sorta figured the “send to McKneel” button on the dialog meant you folks were getting those…
Now if we could change the behavior of the text remaining selected (which results in inadvertantly renaming objects on a far too regular basis, as you rename it, hit enter, forget it’s still selected, go to type a command and thus rename the just named object to the command name, that’d be spiffy.
I have hundreds of objects that are named after commands, which isn’t particularly helpful, as the whole point of naming them is to assist when selecting amongst multiple overlapping objects, to allow one to recall why this particular curve or object which serves as construction geometry to be understandable hours days or weeks later, only to discover the painstaking time spent naming all this stuff is for naught as they’re all now named “move”, “copy” or whatever.
You’re mistaken.
Mac crash reports are seen and we used them anonymously to try to find patterns of problems to fix.
We do the same thing for Windows crash reports, but because on the differences between them, we can automatically process them and tech support people can get a very brief look at how many crashes from an email address, and how the processing tagged them. It give us a little glimpse into what might be the cause of a problem that we do not have for Macs.
As I mentioned, the fix was checked into code this morning.
I’ll test it later this week.
It will be in the next Service Release Candidate.
