Double Menu Items and Mysteriously Highlighted Points in File

Hello All,

I have read these threads for a bit before posting and I have noticed that
many post become threads for troll-like commentary. I hope that
my question gets answered with maturity and mindfullness.

So…

My situation is thus. ( After installing the most recent update v7…) I was using the edge tools and for some reason
noticed that I have two “merge edges” command options in menu. ( please see accompanying images)

Also after using the “show edges” command I now have green points permanently
highlighting at the end points of the surface’s open edges. These points remain highlighted
even after the surface had been deleted.

Can some one tell me what caused the dots and how to get rid of them and also explain why I have two “merge edges” option in my menu?

With best regards,

Do the green points show even after closing the “Show Edges” dialog? If so, could be a display anomaly.

I don’t know about the two “MergeEdges” entries, that might be a bug, I don’t have a Mac here.

hi @gr12 at the moment there will no longer be fixes to Rhino 7, unless it is severe, and this seems more like a papercut

As for the other issue, I cannot reproduce that here, and don’t recall ever having seen it. Pls run _SystemInfo in Rhino and post back the results.
If you can repeat the behavior that these points stay visible after running the ShowEdges command, a sample file would be helpful.
Can the points be selected? Default ShowEdges color is Magenta and default Selection color is Yellow, so to me it looks like these are just point objects.

Yes, they are permanently displayed.
Even when all layers are turned off.

Current status: Still there …still working on the drawing file

Hello Giijs,
Thanks for the info on the fixes status of Rhino 7. *( …even though your subjective *
paper cut rating of the issue felt a bit unnecessary…as neither of us can tell if the issue has correlated side effects or if there is more depth to the glitch )

Answers to the questions you mentioned:
Points cannot be selected (If they are point objects, it seems that I have no way of interacting with them as point objects.)

Please see _SystemInfo results at d of note

The larger draw back is that I have to share the file with several independent working partners that may import
the data into other programs so I am hoping that the ‘paper cut’ has no overarching/deep seated effects on the work process.

Again thanks for giving the my inquiry your attention

_SystemInfo :

Rhino 7 SR36 2023-12-12 (Rhino 7, 7.36.23346.16352, Git hash:master @ 11a364321297eb8cdb34405a3308d8911f58706d)
License type: Commercial, build 2023-12-12
License details: Stand-Alone

Apple macOS Version 13.6.1 (Build 22G313) (Physical RAM: 64Gb)
Mac Model Identifier: MacBookPro16,4
Language: en-US (MacOS default)

AMD Radeon Pro 5600M OpenGL Engine (OpenGL ver:4.1 ATI-4.14.1)

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: 8176 MB
Graphics: AMD Radeon Pro 5600M
Displays: Color LCD (264dpi 2x), DELL S2722QC (163dpi 1x)

Graphics processors
Intel UHD Graphics 630 (1536 MB)
AMD Radeon Pro 5600M (8 GB)
Color LCD (1792 x 1120 @ 59.00Hz)
DELL S2722QC (3840 x 2160 @ 60.00Hz)

USB devices
Realtek: HID Device
Compx: 2.4G Receiver
Apple: composite_device
Apple Inc.: Touch Bar Backlight
Apple Inc.: Touch Bar Display
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple: Headset
Apple Inc.: Ambient Light Sensor
Apple Inc.: FaceTime HD Camera (Built-in)
Apple Inc.: Apple T2 Controller

Bluetooth devices
None

Third party kernel extensions
None

Third party plugins
/usr/lib/swift/libswiftCore.dylib
/usr/lib/swift/libswiftCoreFoundation.dylib
/usr/lib/swift/libswiftDarwin.dylib
/usr/lib/swift/libswiftDispatch.dylib
/usr/lib/swift/libswiftIOKit.dylib
/usr/lib/swift/libswiftObjectiveC.dylib
/usr/lib/swift/libswiftXPC.dylib
/usr/lib/swift/libswift_Concurrency.dylib
/usr/lib/swift/libswift_StringProcessing.dylib
/usr/lib/swift/libswiftos.dylib
/usr/lib/swift/libswift_RegexParser.dylib
/usr/lib/swift/libswiftMetal.dylib
/usr/lib/swift/libswiftsimd.dylib
/usr/lib/swift/libswiftCryptoTokenKit.dylib
/usr/lib/swift/libswiftOSLog.dylib
/usr/lib/swift/libswiftAVFoundation.dylib
/usr/lib/swift/libswiftCoreAudio.dylib
/usr/lib/swift/libswiftCoreLocation.dylib
/usr/lib/swift/libswiftCoreMIDI.dylib
/usr/lib/swift/libswiftCoreMedia.dylib
/usr/lib/swift/libswiftQuartzCore.dylib
/usr/lib/swift/libswiftUniformTypeIdentifiers.dylib
/usr/lib/swift/libswiftNetwork.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftCompression.dylib
/usr/lib/swift/libswiftFileProvider.dylib
/usr/lib/swift/libswiftIntents.dylib
/usr/lib/swift/libswiftPrivate_BiomePubSub.dylib
/usr/lib/swift/libswiftPrivate_BiomeStreams.dylib
/usr/lib/usd/libIex.dylib
/usr/lib/usd/libHalf.dylib
/usr/lib/usd/libAlembic.dylib
/usr/lib/usd/libusd_ms.dylib
/usr/lib/usd/libosdCPU.dylib
/usr/lib/usd/libImath.dylib
/usr/lib/usd/libIlmThread.dylib
/usr/lib/usd/libIexMath.dylib
/usr/lib/usd/libtbb.dylib
/usr/lib/usd/libMaterialXCore.dylib
/usr/lib/usd/libMaterialXFormat.dylib
/usr/lib/swift/libswiftAccelerate.dylib
/usr/lib/swift/libswiftAppKit.dylib
/usr/lib/swift/libswiftCoreImage.dylib
/usr/lib/swift/libswiftExtensionFoundation.dylib
/usr/lib/swift/libswiftCoreML.dylib
/usr/lib/swift/libswiftVision.dylib
/usr/lib/swift/libswiftDemangle.dylib
/usr/lib/swift/libswiftSystem.dylib
/usr/lib/swift/libswiftExtensionKit.dylib
/usr/lib/swift/libswiftRegexBuilder.dylib
/usr/lib/swift/libswiftWebKit.dylib
/usr/lib/swift/libswiftGLKit.dylib
/usr/lib/swift/libswiftMapKit.dylib
/usr/lib/swift/libswiftModelIO.dylib
/usr/lib/swift/libswiftSceneKit.dylib
/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/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 7.36.23346.16352
/Applications/Rhino 7.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 7.36.23346.1002
/Applications/Rhino 7.app/Contents/PlugIns/RhinoBonusTools.rhp “Rhino Bonus Tools” 7.36.23346.1002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 7.36.23346.16352
/Applications/Rhino 7.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 7.36.23346.1002
/Applications/Rhino 7.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 7.36.23346.1002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 7.36.23346.16352
/Applications/Rhino 7.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 7.36.23346.1002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 7.36.23346.16352
/Applications/Rhino 7.app/Contents/PlugIns/Displacement.rhp “Displacement” 7.36.23346.1002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/BlockEdit.rhp “BlockEdit” 7.36.23346.16352
/Applications/Rhino 7.app/Contents/PlugIns/RhinoLabsTools.rhp “Rhino Labs Tools” 7.36.23346.1002
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp “Rhino Render” 7.36.23346.16352
/Applications/Rhino 7.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 7.36.23346.16352
/Applications/Rhino 7.app/Contents/PlugIns/RhinoRender.rhp “Legacy Rhino Render” 7.36.23346.1002

I was referring to the Two ‘merge edge’ entries in the toolbar only

As for the points issue, can you send the file that has these points, do you have steps to reproduce the issue? If confidential and/or too big, you can send it here to my attention
System info does not reveal anything that is suspicious.

Hello Gijs,

Oh I see. Please accept my apologies for the curt statement in my reply.
Yes, two merge labels are admissible.
I get back to you later on the rest…

Thanks again