Thanks for the feedback. So seems to be clear now.
I tested the issue according your description. So I created a project with 3 different models where I can change the model via list widget. I used a javascript to synchronize. The userpick should call a query function to receive the properties.- it will write specific component properties to a textArea widget.
So used general query :
//====================================================
$scope.app.testQuery= function(modelWidgetId,pathId,dispWidgetId) {
BPRN("app.testFunction()");
let metaDATA=PTC.Metadata.fromId(modelWidgetId)
metaDATA.then(function(meta) { console.log("success func of metaData");
let outStr="SEL INFO:: "
//a fix test with object
var ptc_mat = meta.get(pathId,'PTC_MATERIAL_NAME','PROE Parameters');
console.log("PTC_MATERIAL_NAME= " + ptc_mat);
var dispName = meta.get(pathId,'Display Name','__PV_SystemProperties');
console.log(pathId + dispName);
var DV_System_Categ= meta.get(pathId). getCategory ('__PV_SystemProperties')
console.log(JSON.stringify(DV_System_Categ))
outStr="DisplayName="+ dispName+" | MATERIAL::" + ptc_mat+ " | DV_SYS::" +JSON.stringify(DV_System_Categ);
$scope.setWidgetProp(dispWidgetId,'text', outStr);
$scope.$applyAsync();
}) .catch(function(err)
{console.log("problem with the read of metadata ");console.warn(err);});
} Where I called this query inside the userpick event:
angular.element(value).scope().$on('userpick',function(event,target,parent,edata) {
console.log('event');console.warn(event);
console.log('target');console.warn(target);
console.log('parent');console.warn(parent);
console.log('edata');console.warn(edata);
if (edata) {
if ($scope.currentSelection) {
tml3dRenderer.setColor($scope.currentSelection, undefined);
//'rgba(255,10,10,0.8)'
}
$scope.currentSelection = target + '-' + JSON.parse(edata).occurrence;
let r =parseInt(Math.random()*255);
let g =parseInt(Math.random()*255);
let b =parseInt(Math.random()*255);
let a =parseInt(Math.random()*0.8)+0.2;
$scope.blinkSelection($scope.currentSelection,'rgba('+r+','+g+','+b+','+a+')',200,10);
$scope.app.testQuery(target,JSON.parse(edata).occurrence,'textArea-1');
} })All tests are ok and the functionality was working according to the spec. So, I was not able to reproduce an issue with this project. I will attach my test project here, so possibly you can check what are the differences to your workflow. Please, let me know if you could find something. Thanks!
I tested today more detailed the issue and I think to understand the reason why this occurs. Let consider the following setting ventil1, ventil2 and ventil3 (pictures)
this is the original geometry Ventil 3 - so it is displayed OK. But for the another models Ventil 1 and Ventil 2 we have then:
So we can see that the display is not correct! So I think this is the issue what you reported right?
But let look on this version named Ventil 4.
What is there the difference. I used here the edit structure mode form Creo View MCAD to remove the components. And I think this should be the correct workflows.
In this case the behavior work as expected. OK the issue what you described here is also not OK but I think this is something I could report to R&D
OK I found another issue with userpick and switch between models and some issue in the tml3dRenderer where it switch the position to zero world coordinates and this issue occurs after enough switch between different pvz. My opinion this could be more critical issue but fortunately it does not occurs on mobile devices - so tested and verified that on IOS and Android and it is working stable. So that the unexpected movement of the components when we select an ithem with userpick and switch to different pvzs is no issue on the mobile devices....
But let go back to your issue.
- the one workaround could be to use the Creo View MCAD and to edit the structure /advance edit:
where you can remove physically the components form the assembly.
But using the same model many times with different names is not really efficient workflow. Better I think if you define a different step, where you could blank, move or change color etc. form different components. In this case the both issues (wrong display and flipping of to zero world coordinate position) will not occur. So then you can select a different steps and simple call the step via script. Example of such script:
//////////////
//definition of the function
$scope.app.playModelStep = function (sequence,modelName,step_number,play) {
//sequnece -sequnece name e.g. TestFigure1 - as shown in UI
//modelName - model name e.g. model-1
//step_number - set this number to current step
//play true/false execute play for the model
$scope.$applyAsync(()=>{$scope.setWidgetProp(modelName, 'sequence', '');});
$timeout(function () {
$scope.$applyAsync(()=>{$scope.setWidgetProp(modelName, 'sequence', 'app/resources/Uploaded/l-Creo 3D - '+sequence +'.pvi');});
},50);
$timeout(function () {
$scope.$applyAsync(()=>{$scope.setWidgetProp(modelName, 'currentStep', parseInt(step_number));});
if(play) //check if play should be applyed
$timeout(function () {angular.element(document.getElementById(modelName)).scope().play(); }, 100);
}, 500);
};
//////////////////////////////////Attached an updated versions of the test project where Ventil_4 is an assembly with physical delted items and the issue there is not reproducible.
