Changing the spatial/gesture scale via JavaScript

Hi Allan, 

I thought of using model items and binding the gauges to the items. 

I used the following code:

$scope.makeBig = function() {
$scope.view.wdg['model-1']['scale'] = 1.0000;
$scope.view.wdg['3DGauge-1']['x'] =$scope.view.wdg['modelItem-1']['x'];
$scope.view.wdg['3DGauge-1']['y'] =$scope.view.wdg['modelItem-1']['y'];
$scope.view.wdg['3DGauge-1']['z'] =$scope.view.wdg['modelItem-1']['z'];

}

Unfortunately this won't work properly. Their value changes to the right number, but in the preview, the position isn't right. But maybe the idea can help you.

Greetings

whity

I'm not sure that changing the scale of the ThingMark is a hack. I think it is just the other side of the frame of reference from what you are doing with the model scale. Unless PTC is saying otherwise I would do it.

If you move on with scaling all the items you could simplify it a lot by not using application parameters for everything and just doing it all in a JS function called on "Value Changed" for the slider. Here is a function i wrote to update 36 different x, y, z, rx, ry, rz values on slider movement to allow you to move a mechanism with a slider.

$scope.kinematicUpdate = function () {
 let position = $scope.view.wdg['slider-kin'].value;
 let studioIDArray = Object.keys(kinematicsJSON[position]); //array of studioIDs to update
 for(let i = 0; i < studioIDArray.length; i++) { //get into the "time" object
 let theStudioID = studioIDArray[i]; //studioID for object to update
 let propertyArray = Object.keys(kinematicsJSON[position][theStudioID]); //make an array of the keys, "x, y, rx" etc...
 for(let y = 0; y < propertyArray.length; y++) {
 let theProperty = propertyArray[y];
 let theValue = kinematicsJSON[position][theStudioID][theProperty];
 // console.log("ID, Prop, value ", theStudioID, theProperty, theValue);
 $scope.setWidgetProp(theStudioID, theProperty, theValue);
 };
 };
};

and here is a sample of the JSON object it is reading from.

{
 "0": {
 "modelItem-kin-cs": {
 "rx": 0,
 "ry": 0,
 "rz": -0.002016251,
 "x": -0.00000191786,
 "y": 1.75985e-7,
 "z": 0
 },
 "modelItem-kin-link": {
 "rx": 0,
 "ry": 0,
 "rz": -0.005322145,
 "x": -0.0000179498,
 "y": 0.00000190598,
 "z": 0
 },
...
 "1": {
 "modelItem-kin-cs": {
 "rx": 0,
 "ry": 0,
 "rz": -2.08465873,
 "x": -0.00197919,
 "y": 0.00021795,
 "z": 0
 },
 "modelItem-kin-link": {
 "rx": 0,
 "ry": 0,
 "rz": -5.391225358,
 "x": -0.018065299,
 "y": 0.002781849,
 "z": 0
 },
...
 "2": {
 "modelItem-kin-cs": {
 "rx": 0,
 "ry": 0,
 "rz": -4.099274077,
 "x": -0.00388313,
 "y": 0.000496852,
 "z": 0
 },
 "modelItem-kin-link": {
 "rx": 0,
 "ry": 0,
 "rz": -10.42893833,
 "x": -0.034640691,
 "y": 0.006904911,
 "z": 0
 },
...

You could build an object with the initial position of all your objects and then multiply them by the scale value and update instead of looking up by position like i did.

Hi All,

Some updates on this post since @mgoel appears to be going through every post in the forum asking people to mark them as solved.

My requirements for the experience have evolved a bit since my original post.  The original experience could have worked fine by scaling everything in the experience and the hack of scaling the ThingMark works great for this.  But now I have some elements that I want to scale (the model and associated gauges, labels and images) and some that I don't (some images that I have placed on the floor and made behave like toggle buttons using JS).

So really now that the experience requirements have changed, the "spatial scale" option that I originally asked about wouldn't really help at all and neither will the ThingMark size hack.

@jmikesell's method of scaling looks like a way to help me reduce the amount of code and I'll look at using that as I move forward and develop things more.

But as for my original question about using JS to control what I called the "spatial scale" or the gesture scale, I still haven't seen any answer as to whether that's possible or not.