From 92ab61a3b1720f1f8e76188b51dac50102b133c2 Mon Sep 17 00:00:00 2001 From: Amin Yahyaabadi Date: Thu, 18 Nov 2021 09:58:51 -0600 Subject: [PATCH] fix: use unsigned int so that 0xFFFFFFFF can be stored --- opennurbs_defines.h | 4 ++-- opennurbs_object_history.cpp | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/opennurbs_defines.h b/opennurbs_defines.h index fa156bae..35e2e0cf 100644 --- a/opennurbs_defines.h +++ b/opennurbs_defines.h @@ -2133,7 +2133,7 @@ class ON_CLASS ON // the values. The reason for the gaps between the enum // values is to leave room for future snaps with prededence // falling between existing snaps - enum osnap_mode + enum osnap_mode: unsigned int { os_none = 0, os_near = 2, @@ -2409,7 +2409,7 @@ class ON_CLASS ON_COMPONENT_INDEX // Do not change these values; they are stored in 3dm archives // and provide a persistent way to indentify components of // complex objects. - enum TYPE + enum TYPE: unsigned int { invalid_type = 0, diff --git a/opennurbs_object_history.cpp b/opennurbs_object_history.cpp index a3d06de4..fd77eaee 100644 --- a/opennurbs_object_history.cpp +++ b/opennurbs_object_history.cpp @@ -31,7 +31,7 @@ class ON_Value // The VALUE_TYPE enum values must never be changed // because the values are used to determine the parameter // type during file reading. Additions can be made. - enum VALUE_TYPE + enum VALUE_TYPE: unsigned int { no_value_type = 0,