ExportWithOrigin has a bug. Any objects selected to be exported which are on a layer which is turned off after object selection but before picking the insertion point is not exported. Layers may need to be turned off to facilitate selection of the insertion point.
This is different behavior than Move or Copy for example where all objects selected are moved or copied including objects on layers which are turned off after objects are selected.
Instructions for repeating the bug.
Start ExportWithOrigin
Select objects in response to “Select objects to export” and Enter
Turn off one or more layers with some or all of the objects just selected.
Pick a point in response to “Insertion base point. Press Enter to use world origin”
Select the file name and location and complete the command.
The objects which were originally selected but are on the layers turned off are not exported.
This bug needs attention. It is more than an inconvience. It can result in a file being inadverdently created without some of the intended geometry. Depending on the situation it may difficult or impossible for the recipient of the file to obtain the missing geometry. @pascal Can this be put on the heap with reasonable priority?
@pascal Thanks for putting it on the stack. But there is a very good reason to be able to select an object, then turn off that layer while completing a command such as ExportWithOrigin, Move, Copy, Rotate, etc. Frequently it is much easier to pick a needed insertional point, reference point, target point, etc after turning off a layer with some objects. I do it frequently.
Why is it “wrong” to include the previously selected objects in the exported objects?
Hi David - in general, Rhino avoids doing things with objects you cannot see - I was surprised that Move works the way it does - so, wrong, in the context of that ‘don’t mess with objects the user cannot see’ idea, but that is less strict than I thought. With groups that have hidden objects, Rhino draws a ghosty version of the hidden bits when you drag or move so you can see something and are not surprised if ‘off’ objects have been changed - this seems reasonable to me and should maybe be implemented in any context where something is happening with hidden objects. It seems to me anyway.
@pascal How would you deal with the situation where objects selected to be exported or transformed obscure points/lines/etc which need to be snapped to for the insertion point, reference point, target point, etc? I run into this situation when scaling and orienting imported large meshes. If I can’t turn off the layer with the mesh then I don’t know how i will be able to snap to the points needed to scale or orient it. BTW, the answer is not to create a block.
I’ll note that include selected objects on layers which are turned off should only apply for layers turned off after the command is started.