. 3. Wires when select a component
When select a component the wires change( inputs and some outputs) and segmentation in data tree wires doesn’t look as dash pattern.
hmm… the panel text to number issue seems to be related to unix vs windows newlines, similar to a bug I encountered for the C# scripting component: C# component is rounding doubles
I’m guessing the panel naively splits multiline data that’s been created with Windows-style "\r\n", and fails to parse the leftover '\r' lumped in with the number text.
As a workaround you could drop this little C# script into the canvas: fix_panels_mac.gh (4.5 KB)
foreach(var obj in GrasshopperDocument.Objects){
var panel = obj as Grasshopper.Kernel.Special.GH_Panel;
if (panel==null) continue;
panel.SetUserText(panel.UserText.Replace("\r\n", "\n"));
}
(GH on Windows is robust enough to parse Mac-style newlines, so this shouldn’t break anything)
Sorry for the delayed reply. Thanks for the report and the detailed steps.
Unfortunately, I cannot reproduce this. I tried with option+e as well as holding down the e key and pressing the 2 key for the é character. The é character appears as expected. When I press esc, the search dialog closes as expected without a crash.
Can you please provide some additional information? Please navigate to Rhinoceros > About Rhinoceros > More info… > Copy to clipboard and paste the content back into a reply here. Perhaps there’s a third-party kernel extension on your machine getting in the way.
I might need to switch my macOS language to another language to reproduce this. I think I see a couple crash-reports coming across our automated reporting system that might also be this issue, so I’d love to reproduce it.
The escape key has to be pressed while the cursor state is waiting for a keypress to complete the character - ie. when the orange highlight is active, as in the screenshot above.
Might sound like an odd thing to do but I had Option-Q mapped to “Toggle Preview On/Off” and also to a dead-key on my regular keyboard layout, which is how I accidentally triggered it.
Here’s the information from the About page, also just submitted a crash report.
Third party kernel extensions
com.displaylink.driver.DisplayLinkDriver (4.0.0 (85514)) 5A240BCF-1B8D-3A9E-B21B-B12D639AC9D9
com.3dconnexion.driver (10.5.2) 23F2462E-B272-3BBC-A8DC-BEE242EE3FA7
com.kensington.trackballworks.driver (1.3.0) 598CF9DF-CC79-34D9-B2DA-C63E7516FD0A
com.intel.kext.intelhaxm (6.0.1) 8FF2C637-0A5E-367E-B007-5B08655B1E8A
Hardware information
Computer hardware
Hardware model: MacBookPro9,1
Processor: Intel Core i7-3820QM CPU @ 2.70GHz
Memory: 16 GB
Architecture: Intel 64 bit
Video hardware
Graphics: NVIDIA GeForce GT 650M 1024 MB
Memory: 1024 MB
Screen size: 1680 x 1050, 1200 x 1920
Displays: Color LCD (129dpi 1x), DELL U2410 (94dpi 1x)
USB devices
Apple Inc.: FaceTime HD Camera (Built-in)
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple Computer, Inc.: IR Receiver
Apple Inc.: Bluetooth USB Host Controller
Generic: Ultra Fast Media Reader
Kensington: Kensington Slimblade Trackball
3Dconnexion: SpaceNavigator
Bluetooth devices
None
OpenGL information
OpenGL software
OpenGL version: 2.1 NVIDIA-10.30.25 355.11.10.10.30.120
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
