From dfe5442daeca425a462f27db9ece8d92054d7d9d Mon Sep 17 00:00:00 2001 From: Magne Sjaastad Date: Wed, 3 Sep 2025 13:23:23 +0200 Subject: [PATCH] Removes scripting capability of trajectory points For large point arrays, the scripting causes overflow in the grpc communication. Disable scripting to make sure the grpc object size is below size threshold. --- .../ProjectDataModel/WellPath/RimPointBasedWellPath.cpp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/ApplicationLibCode/ProjectDataModel/WellPath/RimPointBasedWellPath.cpp b/ApplicationLibCode/ProjectDataModel/WellPath/RimPointBasedWellPath.cpp index 0999c2061a..b5e9c29856 100644 --- a/ApplicationLibCode/ProjectDataModel/WellPath/RimPointBasedWellPath.cpp +++ b/ApplicationLibCode/ProjectDataModel/WellPath/RimPointBasedWellPath.cpp @@ -21,8 +21,6 @@ #include "Well/RigWellPath.h" #include "Well/RigWellPathGeometryTools.h" -// Make sure to include cafPdmFieldScriptingCapabilityCvfVec3d. Include of general cafPdmFieldScriptingCapability causes unity build issues. -#include "cafPdmFieldScriptingCapabilityCvfVec3d.h" #include "cafPdmObjectScriptingCapability.h" #include "cafPdmUiOrdering.h" @@ -35,7 +33,7 @@ RimPointBasedWellPath::RimPointBasedWellPath() { CAF_PDM_InitScriptableObject( "Point-Based Well Path", ":/Well.svg", "", "PointBasedWellPath" ); - CAF_PDM_InitScriptableField( &m_trajectoryPoints, "TrajectoryPoints", std::vector(), "Trajectory Points" ); + CAF_PDM_InitField( &m_trajectoryPoints, "TrajectoryPoints", std::vector(), "Trajectory Points" ); m_trajectoryPoints.uiCapability()->setUiHidden( true ); }