it simply hides visually behind the already open file but seems to be in focus already but again just not visible. using the menu to open a new file seems to work.
anybody?
I cannot reproduce this in 8.7.24138.15432 on macOS Sonoma. Here is what I tried:
- Launched Rhino 8 and started a new modeling window (with command+N)
- Pressed command+N again to start another modeling window.
The new modeling window appears in front of the first window. What are we doing differently?
just in case, did you position any geometry in the first window before you opened a second window?
also i have the MacOs Menu set to autohide, maybe that makes a difference?
No. Doing so makes no difference here.
Iâm not sure what setting youâre refering to. What happens if you quit Rhino, disable autohide, then restart Rhino and test?
and how will you know that not the old window is showing?
nothing. the effect is the same, the new window hides behind the previously open project, so that is not causing it.
Systeminfo
Rhino 8 SR8 2024-5-16 (Rhino 8, 8.8.24137.03002, Git hash:master @ 827c456690f0d1d35b3df9321534fb35df1a5672)
License type: Educational, build 2024-05-16
License details: Stand-Alone
Apple macOS Version 13.6.6 (Build 22G630) (Physical RAM: 64GB)
Mac Model Identifier: Mac13,2
Language: en
.NET 7.0.0
Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M1 Ultra
MateView (2304 x 1536 @ 60.00Hz)
USB devices
Dialog Semiconductor (UK) Ltd: MateView
Logitech: G Pro Gaming Mouse
Apple Inc.: Apple Keyboard
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/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/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/libswiftCryptoTokenKit.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftOSLog.dylib
/usr/lib/swift/libswiftAccelerate.dylib
/usr/lib/swift/libswiftAppKit.dylib
/usr/lib/swift/libswiftCoreImage.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/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
/Users/richard/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/bella_rhino.rhp/libbella_dotnet_native.dylib
/usr/lib/log/liblog_network.dylib
Rhino plugins that do not ship with Rhino
/Users/richard/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/bella_rhino.rhp âBellaâ 23.3.0.0
Rhino plugins that ship with Rhino
/Applications/Rhino 8.app/Contents/Frameworks/RhMaterialEditor.framework âRenderer Development Kitâ 8.8.24137.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp âCommandsâ 8.8.24137.3002
/Applications/Rhino 8.app/Contents/PlugIns/NamedSnapshots.rhp âSnapshotsâ 8.8.24137.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCodePlugin.rhp âRhinoCodePluginâ 8.8.24137.3002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp âRDK_EtoUIâ 8.8.24137.3002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/MeshCommands.rhp âMeshCommandsâ 8.8.24137.3002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp âRhino Renderâ 8.8.24137.3002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp âRhinoCyclesâ 8.8.24137.3002
/Applications/Rhino 8.app/Contents/PlugIns/SectionTools.rhp âSectionToolsâ 8.8.24137.1002
/Applications/Rhino 8.app/Contents/PlugIns/Displacement.rhp âDisplacementâ 8.8.24137.1002
/Applications/Rhino 8.app/Contents/PlugIns/PanelingTools.rhp âPanelingToolsâ 8.8.24137.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp âIronPythonâ 8.8.24137.3002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp âGrasshopperâ 8.8.24137.3002
here a video that you see what i am seeing. the window appears for short but gets hidden behind automatically.
Because the first window says âUntitledâ in the document title (top center) and the second window says âUntitled 2â. (The windows are also in different positions on the screen).
Thank you, that helps. It matches what I had in my imagination from your description. The SystemInfo is also useful to have. Since youâre still on macOS Ventura (13.6.6), I tried to reproduce this on my test-ventura Mac. Itâs running macOS Ventura 13.6.7 and, unfortunately, I still could not reproduce it. Itâs a long-shot that the buggy behavior youâre seeing is due to a minor release (certainly possible, but unlikely). Itâs likely more related to some Rhino setting.
@dan make sure that the command history is closed so that the tooltip thingy is displayed in the bottom left:
2 Likes
That was the critical detail I was missing. Now this makes a lot more sense. Thank you Jari!
Logged in:
RH-83106 Command popover causes wrong document to be key after Cmd + N
1 Like