I’m having a massive problem with dimensions in layout changing (unpredictably) when they are moved. I frequently move detail views and dimensions around the page as I am assembling a drawing and this is becoming a massive problem with drawings being published without me noticing the numbers are now wrong. They seem to be dimensioning to the detail view itself (so a 1:50 detail view with a dimension on it will read 3650mm correctly and will change to 73 which is no longer correct)
Under my History setting I always have both Record and Record Annotation History turned off. Broken History Warning is turned on but over ridden by my other controls. History Purge does nothing either.
Could this be a problem with the dimension settings themselves? Have never had this happen before and have been using Rhino 7 for 6 months now.
Apple macOS Version 10.14.6 (Build 18G103) (Physical RAM: 64Gb)
Mac Model Identifier: iMac19,1
Language: en-NZ (MacOS default)
AMD Radeon Pro 575X OpenGL Engine (OpenGL ver:4.1 ATI-2.11.20)
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: 4 GB
Graphics: Radeon Pro 575X
Displays: iMac (217dpi 2x), Kamvas Pro 22 (102dpi 1x)
Graphics processors
Radeon Pro 575X (4 GB)
iMac (2560 x 1440)
Kamvas Pro 22 (1920 x 1080 @ 60 Hz)
USB devices
Seagate: Fast SSD
Apple Inc.: FaceTime HD Camera (Built-in)
MOSART Semi.: 2.4G Wireless Mouse
Logitech: G502 HERO Gaming Mouse
VIA Labs, Inc.: USB2.0 Hub
BizLink Technology Inc.: USB-C To HDMI Adapter
Bluetooth devices
Unknown: Magic Keyboard with Numeric Keypad
Third party kernel extensions
com.displaylink.DisplayLinkDriver (5.2.5 (90)) EBD03A5D-AAF7-359E-A73A-410864E86B3A
Third party plugins
/usr/lib/log/liblog_network.dylib
Hello - Can you please post a file, or send one to tech@mcneel.com, that shows the problem? As small and simple as possible, so long as it shows the problem, would be best.