1 ACCEPTED SOLUTION
Accepted Solutions
Hi @JH_10275801 ,
tested today but have some further quesitons to your post/feedback.
So the code mentioned /is clear but I did not pay attention on the first time I looked on it/ it will do nothing with the data e.g. to save. So means the code will take picture and will do ... something what you need to know, to be defined in further code.
For example take a picture on HL standard /not view/ will save the picture by default ...<FileExplorer Location>\Pictures\Camera Roll:
But the code you mentioned will save it to variable data and nothing else, so it is important to know what are the actions later , because possibly this was relevant for the occuring of the issue your described
The left , first picture is that when is done by HoloLens 2 take picture in vuforia View. This command will save the picture as mentioned to the Camera Roll folder. The second picture on the right is also done by take Picture HoloLens 2 default called in View ,but there we can see the inside the picture another picture shown on 3DImage widget. So that was a picture what I did in Vuforia View on Hololens 2 and set to the src property of the 3DImage widget.
I used 2 different buttons with 2 different /but similar impementations /prog code
//==========================
$scope.takeScreenie = function () {
let props = {
"withAugmentation": true,
"imgWidth": 3904,
"imgHeight": 2196
};
//==========================
let successCb = function(result, params) {
console.log("params: " + JSON.stringify(params));
console.log("result: ", result);
$scope.setWidgetProp('3DImage-1','src','data:image/jpeg;base64,'+result)
$scope.$applyAsync();
};
//++++++
tml3dRenderer.takeScreenshot(props, successCb, ()=>{});
}
//==========================
//=================
$scope.takePicture= ()=>{
//---------------------------------------------------------------------------------------
var callbackfnc = function (pngBase64String, args) {
$scope.setWidgetProp('3DImage-1','src',pngBase64String)
$scope.$applyAsync();
console.warn(pngBase64String)
};
//---------------------------------------------------------------------------------------
$scope.screenShotPar = function(augmentation) {
let params = { dataURL:true, withAugmentation:augmentation,"imgWidth": 2880,"imgHeight": 1406 }
tml3dRenderer.takeScreenshot(params, callbackfnc, null);
$scope.$applyAsync();
}
//---------------------------------------------------------------------------------------
$scope.screenShotPar(true)
}
//====== utilitiesthe one creates a a picture with the higher resoluton 3904x2196:
so the arrea on 3DImage widget (there are no properties for width and high set -so it follow the picture size) is much larger as in the other picture which was made with the 2880 x1406
So all both functions are working on my HoloLens 2 device when I took the picture and set it to a widget URL source . I did not observerd any issues, at least I am not aware that there are any . So the question is what did you with the picture that you run in the issue.
On my device Vuforia view / "Hey, version" HL will answer with 9160.7473. What is your version/string returned by HL device ?
Thanks
BR
