Command history: Command: _MoveHole Select holes in one planar surface_Pause Point to move from ( Copy=No )_Copy=_No
Starting point and target point clicked.
The result: nothing happens, the hole does not move and is not copied.
Max.
Software information
Software versions
Rhinoceros version: 5.1 (5B161)
IronPython version: 5.1.2015.131
Language: nl (MacOS default)
OS X version: Version 10.9.5 (Build 13F1134)
Plug-ins
None
Third party kernel extensions
None
Hardware information
Computer hardware
Hardware model: iMac10,1
Processor: Intel Core2 Duo CPU E7600 @ 3.06GHz
Memory: 4 GB
Architecture: Intel 64 bit
Video hardware
Graphics: ATI Radeon HD 4670 256 MB
Memory: 256 MB
Screen size: 2560 x 1440
Displays: iMac (109dpi 1x)
USB devices
Apple Inc.: Built-in iSight
Apple: Internal Memory Card Reader
Apple, Inc: Apple Keyboard
Wacom Co.,Ltd.: CTH-661
Apple Computer, Inc.: IR Receiver
Apple Inc.: Bluetooth USB Host Controller
Bluetooth devices
None
OpenGL information
OpenGL software
OpenGL version: 2.1 ATI-8.24.17
Render version: 2.1
Shading language: 1.20
Maximum texture size: 8192 x 8192
Z-buffer depth: 24 bits
Maximum viewport size: 8192 x 8192
Implementation settings
Use texture compression: No
This is the object: CopyHoleBug.3dm (136.8 KB)
I can move any of these holes without problem, but as soon as I tick the Copy option, nothing happens anymore. That is, no move or copy of the hole. Rhino continues to function normal though.
Max. (have to go now, more details later if needed)
I am getting it to work fine with the provided file. With copy selected, I have to select the hole, select my reference, move it to the copy locations. Mark the copy locations with a left click at each location and then right click to complete the command and see the result.
I sussed it out, “Enter” did it. I was mislead by the fact that moving a hole only needed two LMB clicks, but copying requires finalizing by hitting Enter. I still believe it is a bug, since there is no visual clue of where you put the new hole after your target click, it only appears after hitting enter. Only then you can check whether you hit the mark or not. I realize that is the same for MoveHole, but there is no added value in entering to confirm your action.
I agree here - I think the command was written to avoid regenerating the display mesh every time a hole was copied, which could slow the operation down if the object is complex. But it is a bit disconcerting to only see the hole show up in wireframe until you finish the command.
In Windows Rhino in any case, no Enter is needed for MoveHole to complete the command if Copy is set to No. Maybe MacRhino is set up differently, I’ll have a look.
