OilfieldToolsNet/ResInsight
4
0 Fork 0
mirror of https://github.com/OPM/ResInsight.git synced 2026-10-26 15:10:22 -05:00
Code Issues Packages Projects Releases Wiki Activity

Removes scripting capability of trajectory points

Browse Source 
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.
This commit is contained in:
Magne Sjaastad authored and Kristian Bendiksen committed 2025-09-03 16:11:13 +02:00
1 parent 4a8af2ff9d
commit bde4eeb892
1 file changed
+1 -3
Download Patch File Download Diff File Expand all files Collapse all files
ApplicationLibCode/ProjectDataModel/WellPath/RimPointBasedWellPath.cpp
+1 -3
View File
@@ -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<cvf::Vec3d>(), "Trajectory Points" );
CAF_PDM_InitField( &m_trajectoryPoints, "TrajectoryPoints", std::vector<cvf::Vec3d>(), "Trajectory Points" );
m_trajectoryPoints.uiCapability()->setUiHidden( true );
}