More Properties Name Field Fatal Bugs

@John_Brock

So I got the latest bug fix release. All the property name bugs are still very much alive and well.

Rather than focusing on the symptoms (myriads of fatal crashes) how about we focus on the cause?

HOW TO REPRODUCE AT WILL

  1. Create anything. Doesn’t matter.
  2. Select it.
  3. Click in properties / name field and rename it
  4. Hit return
  5. Do pretty much ANYTHING else.
  6. Crash

Stuff I know in step 5 that will kill it:

Export Selected
Boolean (any variety)
Group (or ungroup)
Create Block (or explode) or any thing else block related
Any Solid Edit Tool Submenu item
Any Curves Tool Submenu Item

In short the problem is 100% related to leaving the damn name field in focus when you hit return. Pretty much anything you do after that (particularly menu based stuff) will cause an instant crash.

HOW TO FIX

The solution is simple. Just kill the focus in the property name field once you hit return after naming something. There’s absolutely ZERO good reason to leave the field in focus. If someone screws up typing the name they can reselect the field and rename it.

WHY THIS NEEDS FIXING

Because 95% of the time the next operation is something else. A command line command, menu command, etc, and the vast majority of these will cause a crash.

Why else?

Because we rename stuff for a reason. And it doesn’t help with the damn field remaining in focus and typing a command that now not only doesn’t take but renames the object to the name of the command completely wrecking the whole point of naming something in the first place.

This bug has been here for a really damn long time now, and I’ve encountered in various forms always reporting them as what I was trying to do AFTER naming something, and thus the number of crashes was limited to what I tend to do AFTER renaming something.

So please, address this. It’s been causing me to lose work since V5, and a LOT of lost work in the last 6 months as I’ve migrated my files to a NAS Raid 10, and it does not support the persistent storage stuff that Apple uses for autosave and internal versioning, so when I crash? I lose everything since the last save and in the last six months this bug in it’s various forms have cost me hours and hours of work I’ve had to recreate.

Its not your fault my stuff is on a NAS, however after losing an entire weeks worth of work when an internal SSD died (I run full backups every sunday night at 4AM, and it died saturday afternoon) moving files on a raid 10 NAS makes sense.

VERSION / ENV STUFF BELOW

Rhino 7 SR2 2021-1-12 (Rhino 7, 7.2.21012.17002, Git hash:master @ b109c0eb42133053936614c484cb870a02a53b49)
License type: Commercial, build 2021-01-12
License details: Cloud Zoo

Apple Intel 64-bit macOS Version 10.14.6 (Build 18G3020) (Physical RAM: 96Gb)
Mac Model Identifier: MacPro5,1
Language: en-US (MacOS default)

AMD Radeon RX 580 OpenGL Engine (OpenGL ver:4.1 ATI-2.11.21)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: ATI Technologies Inc.
Render version: 4.1
Shading Language: 4.10
Maximum Texture size: 16384 x 16384
Z-Buffer depth: n/a
Maximum Viewport size: 16384 x 16384
Total Video Memory: 8 GB
Graphics: Radeon RX 580
Displays: LG HDR 4K (271dpi 2x), LG HDR 4K (271dpi 2x)

Graphics processors
Radeon RX 580 (8 GB)
LG HDR 4K (3200 x 1800 @ 60 Hz)
LG HDR 4K (3200 x 1800 @ 60 Hz)

USB devices
Genesys : USB3 Reader
Kensington: Kensington Slimblade Trackball
3Dconnexion: SpaceMouse Enterprise
Apple, Inc: Apple Keyboard
Apple Inc.: Bluetooth USB Host Controller

Bluetooth devices
None

Third party kernel extensions
com.3dconnexion.driver (1.1.3) 7F3D461C-BC8E-3D27-A964-2FCC8BE205E2
com.rim.driver.BlackBerryUSBDriverInt (0.0.68) 5794FFBC-214B-B40A-95A5-07DA0A6402B6
at.obdev.nke.LittleSnitch (5470) A938A4D4-0642-39B0-A99E-4FA69C7F9660
com.dvdfab.kext.fabio (1) no UUID
com.kensington.trackballworks.driver (1.5.0) DB29005C-2B91-3805-A070-DE97F5D7061F
com.AmbrosiaSW.AudioSupport (4.1.4) no UUID
com.malwarebytes.mbam.rtprotection (4.6.12) EB8FB437-AE7D-3B5D-AD84-0CDB871BDBB0

Third party plugins
/Library/Frameworks/3DconnexionClient.framework/Versions/A/3DconnexionClient
/usr/lib/log/liblog_network.dylib

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
/Applications/Rhino 7.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 7.2.21012.1002
/Applications/Rhino 7.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 7.2.21012.1002
/Applications/Rhino 7.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 7.2.21012.1002
/Applications/Rhino 7.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 7.2.21012.1002
/Applications/Rhino 7.app/Contents/PlugIns/Displacement.rhp “Displacement” 7.2.21012.1002
/Applications/Rhino 7.app/Contents/PlugIns/RhinoRender.rhp “Legacy Rhino Render” 7.2.21012.1002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Import_OBJ.rhp “Import_OBJ” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/export_XAML.rhp “export_xaml” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/QuadRemesh.rhp “QuadRemesh” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Export_OBJ.rhp “export_OBJ” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/export_SVG.rhp “Export SVG” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/MeshCommands.rhp “MeshCommands” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Export_DAE.rhp “Export_DAE” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/export_PDF.rhp “PDF Export” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/export_IGES.rhp “IGES Export Plug-in” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Import_SVG.rhp “Import_SVG” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/BlockEdit.rhp “BlockEdit” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Export_AMF.rhp “Export_AMF” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp “Rhino Render” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/import_DST.rhp “Import_DST” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/export_PLY.rhp “PLY - Polygon File Format Export” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Import_AMF.rhp “Import_AMF” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 7.2.21012.17002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 7.2.21012.17002

What made you think this was fixed?
It’s reported but not yet fixed:

https://mcneel.myjetbrains.com/youtrack/issue/RH-62337

@John_Brock

Ah ok. For some reason thought it was fixed in last update.

At any rate can we at least update the scope of the bug to include my post above? It’s not just group, it’s pretty much any menu item and a lot of other stuff as well, and it’s because the field remains in focus.

And while you’re in there, can we just make the field lose focus when you hit return to finally cure the inadvertent renaming of objects when you follow it with a command line command.

I don’t think this an unreasonable request, and it certainly wouldn’t be difficult to do as surely the text field class has events that get kicked when you hit return / tab / etc, and those could easily be used to kill the focus on the field so stuff doesn’t get renamed when you type something else after hitting return.

I and many others have pointed this out many times over the last several years and it just tends to fall through the cracks and never gets addressed.

Done.
I just linked this Discourse thread into the defect report.

I think the Developer will be back at work this next week.

Based on how interrelated these tools are under the hood, I suspect the change will not require a great deal of work.
What concerns me is because these tools are so interrelated, that this change may cause unintended breakage of other tools that currently work fine.

They will figure it out.

Thankee. Really.

You guys fix this? 99% of my crashes will vanish. My Rhino related stress levels will drop to practically zero, as outside of this bug and it’s myriad of variants, I actually look forward to firing up Rhino after having to use Autocad all week for work stuff (only because we have to have dynamic blocks, and because of that I have to endure dozens of unfixed AutoCad bugs that have been there (some literally for decades), and to be honest I look forward to using Autocad somewhat less than having a root canal administered with a sledge hammer and a crowbar.

If ya’ll really wanna be heroes, implement Dynamic block read / write for DWG’s and I can toss Autocad in the trash, as everything else I need to do in Autocad I could far more effectively and efficiently do in Rhino, but the Dynamic blocks thing I can’t get around.