Properly handling embedded images in Xamarin.Forms while using Live Player - xamarin.forms

Building and deploying on the real device takes ages. Xamarin Live Player is great and handy, but has some harsh limitations. I want to use the embedded images approach, that is working when the solution is built and deployed but falls into those limitations of the Live Player, and I am getting such exceptions:
[LogEntry: Time=2018. 05. 04. 9:42:31 +02:00, Level=Error, Title=Visualization Error, Message=Object of type 'NInterpret.InterpretedObject' doesn't match target type 'Xamarin.Forms.Xaml.IMarkupExtension' (TargetException)]
Is there any simple workaround to make the application show in Player? I could happily live with not showing the image at all (or at best showing a placeholder instead) when using Player and have the image shown as expected when using the regular flow.

Related

VR View Web and iOS

In the VRView web documentation there is the following statement in the known issues section;
360° images will have incorrect orientation in iOS Safari if you explicitly declare your iframe (instead of using the JavaScript API) and the code and images are hosted on different servers.
However as far as I am aware I am not using the iFrame mode of operation, but instead using the .JS method in the examples, however the video is still at 90 degrees when the phone is put into VR Mode.... I can sort of live with the image not quite in full screen mode, but not with the orientation.
Alternatively is there a way to 'self-host' the VR View package, on a Hosting platform, so that the iFrame method of calling the video works?
<iframe src="/vrview/src/embed?video=injected1.mp4&is_stereo=false"></iframe>
Doesnt work as it says Forbidden - You don't have permission to access /vrview/src/embed/ on this server.
Any help gretefully received

HERE map isn't displayed well on mobile

i have issue when using mobile to view app, when i go to map section it's not displayed well.
this is how it looks, and it's not the same on all devices (this is SS taken from ZTE Blade A6 lite which has version 7.1.1), on some newer androids it's fine.
I was wondering are there some limitations to implementation or it's known issue?
If the map is rendering fine on other android devices, then problem could be with device and not how the sdk works. you can refer to github for efficient map rendering practices followed in our sample code implementation(https://developer.here.com/documentation/android-sdk/4.2.0.0/dev_guide/content/topics/examples.html). Is there any specific error which is logging at the application level while map rendering. Do you mind sharing to know the issue better.

Photoshop tvOS LSR extension gives error

We're trying to create a tvOS application icon for our new tvOS application. We've downloaded the necessary extensions and the example .psd. We've tried to generate a preview using the plugin but it keeps saying it's missing a background layer.
I've added the layer, named it background, and locked it, but the same error keeps popping up.
I haven't used the photoshop plugin, but what it probably means is that at least one layer has to be the right size (e.g. 400x240) and has to be opaque.
Also, for what it is worth, you don't need to create a separate layered image unless the layers are of a different size. You can just drag the individual layers directly into the assets.

DirectShow - order of adding filters causes image to look strange with Microsoft Lifecam Studio

I'm working on a video capture application using DirectShow and have noticed certain problems. In particular, with a Microsoft LifeCam Studio camera, the following strange situation occurs:
If the order of adding the capture filters is: video capture first, then audio (camera microphone), then the image from the camera gets a strong pinkish tint - looks like a black and white image run through a color transform to make it pink.
If I swap the order of adding the filters: audio (microphone) first, then video, then the problem goes away.
I've first noticed this in my application but have since verified that the same happens in Graph-Edit.
Is there any reasonable explanation for this phenomenon?

Adobe Air Browser

Im trying to implement a mini browser in adobe air. The browser should work in the same ways as a mobile phone browser, i.e. fit the width of the website to a certain width(specified within the html component) and leave the height to be scrollable.
I have managed to do a mini browser by using the scaleX,scaleY properties of the mx:HTML component however these make the websites look unreadable.
I have also tried setting the css3 zoom property, and that works fine, but it only zooms out certain elements, therefore messing up the site layout.
My question is: Is there a way to make a mini web browser which shows the full content of the website?
Thanks for your help
Air browser cannot be scaled without have an horrible look (no anti-aliasing).
A few years later but here is what I ended up doing:
The requirement was to show the full website that person B was looking at so that person A could guide them through the site. Due to all the limitations of the Adobe AIR Browser we ended up using IECapt (http://iecapt.sourceforge.net/) within an external process to capture the screenshot and send it back to AIR.
This is all well and good, but IECapt is quite out of date as well so recently we have started to look at the using Chromium (http://www.magpcss.net/cef_downloads/) as an ANE within our application and with that we can alter the zoom and dimensions of the page while still being able to keep it up-to-date.

Resources