Hi @krthk86g ,
Unfortunately, I saw first now that there was a further question to this topic.
The main idea here (what was suggested) for the workaround is to use 3d components in the sequences /the steps instead of 2d symbols. This means that for each 2d symbol you can create and to add to the top assembly a 3D component. For (arrows, tools, symbols but sometimes also for texts and additional info)
So, the installation tools info could be provided by adding some additional 3d components which are not part of the assembly
We can use also for some 2d symbols e.g. arrow a 3d flat components:
Ok, for long texts is this not so good idea – so in this case the models widget could be combined with some text Area widget where the text could be displayed but in generally texts could be implemented also in 3d components
When you try to combine a sequence with a 3d Widget or 2d Widget display (e.g. the display of text in text Area widget will change when for example you will start the step 3) - for this you can use JavaScript code with listeners
e.g. stepstarted or stepcompleted – the example below is not related to the topic but demonstrates the general usage of the mentioned listeners:
//=============================================
$scope.$on('stepcompleted', function(evt, arg1, arg2, arg3) {
var parsedArg3 = JSON.parse(arg3);
//console.warn(arg3)
console.log("stepcompleted stepNumber="+parsedArg3.stepNumber + " nextStep="+parsedArg3.nextStep);
$scope.$applyAsync(()=>{
// $scope.setWidgetProp(modelWdgName, 'disabled',false)
$scope.app.params['disabled']="false";
})
});
//============================================= $scope.$applyAsync(()=>{ $scope.setWidgetProp(modelWdgName, 'disabled',false) })
$scope.$on('stepstarted', function(evt, arg1, arg2, arg3) {
var parsedArg3 = JSON.parse(arg3);
//console.warn(arg3)
console.log("stepstarted stepNumber="+parsedArg3.stepNumber + " nextStep="+parsedArg3.nextStep);
$scope.$applyAsync(()=>{ $scope.app.params['disabled']="true";
})
});
//================================================================
The display of info outside the 3d model in text widgets (labels 2d or 2d or text area)could be used only for the display of general step information but it will be difficulty to display e.g. information related to small components inside large assembly models when you want to relate very detailed information for small parts
Unfortunately I do not have an example for this application case.
