Two Non-Critical Bugs (Control+Alt Click & Spacebar/Magnifying Glass)

When I went to search for object locations, it seemed to be acting abnormally-- see the linked video for documentation ( ). The first three times I tried in the video I clicked the button. When I hold the mouse down the icons stay in place, but the icons still have their black backgrounds, and some of the locations don’t match up.

Definitely not a killer problem, but worth noting at least!

EDIT:::::::: I found another quick bug, adding it here instead of making a whole new post! When I click spacebar then the magnifying glass, RhinoWIP goes nearly completely unresponsive, and I have to force quit-- here’s video again ( ). Both of these issues are reproducible on my end.


Software information

Software versions
Rhinoceros version: 5.2 WIP (5C95w)
IronPython version: 5.1.2015.132
Language: en (MacOS default)
OS X version: Version 10.11 (Build 15A284)


Third party kernel extensions
com.nvidia.CUDA (1.1.0) 5AFE550D-6361-3897-912D-897C13FF6983
com.sophos.nke.swi (9.4.50) CF19823A-698E-308B-9AE2-1037B1BF3409
com.sophos.kext.sav (9.4.50) 752EC8CA-5B00-3884-8F8D-0ACDF15E3FBB

Hardware information

Computer hardware
Hardware model: MacBookPro11,3
Processor: Intel Core i7-4870HQ CPU @ 2.50GHz
Memory: 16 GB
Architecture: Intel 64 bit

Video hardware
Graphics: NVIDIA GeForce GT 750M 2048 MB
Memory: 2048 MB
Screen size: 1440 x 900
Displays: Color LCD (221dpi 2x)

USB devices
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple Inc.: Bluetooth USB Host Controller

Bluetooth devices

OpenGL information

OpenGL software
OpenGL version: 2.1 NVIDIA-10.6.42 310.42.05f01
Render version: 2.1
Shading language: 1.20
Maximum texture size: 16384 x 16384
Z-buffer depth: 24 bits
Maximum viewport size: 16384 x 16384

Implementation settings
Use texture compression: No

Appearance settings
Antialiasing: 4x
Mip map filtering: None
Anisotropic filtering: None

Thanks for reporting. I’ve filed both:

I was not able to duplicate the second item you reported, but I’m also testing on a different version, so it could be that it has been fixed. Note that the Find feature is still being ported: