i am working on a uwp application.
I use a MapControl displaying a map from BingMaps. Everything works perfectly when i debug on my machine but when i debug on a mobile emulator the map doesn't display (instead there is a blue background).
I've also tried with the MapControl sample from the uwp samples found on github, and i have exactly the same issue.
Does someone have an idea about this problem ?
Thank you in advance for your help
It should be the problem of your mobile emulator's version. I discussed this problem with my Colleague before, and I tested in the latest version of mobile emulator, the MapControl can be displayed.
Related
I have copied the project from my old amchine to windows 10 machine. Application works without any problem on simulator. If I right click to see the properties, I don't see IOS, Android and build hints. Please advise if there is something I'm missing here.
This was removed ages ago in Codename One 5.0 but was deprecated before that. See https://www.codenameone.com/blog/removing-old-preferences.html
You should use Codename One Settings in the right click menu.
IDE: Eclipse
Desktop OS: Mac
Device : Android 4.0.4
Hi,
last week i sent a new android build to the server, and it updated the jar files i have on my Mac, then i installed the app on LG android 4.0.4 device that i tested before, and was surprised to find some pages display all black.
After investigating a little, i discovered that when i use tabs on any form the form will be displayed black only on android, no problem on simulator nor IOS iPhone 6S.
I looked at the forum and i found similar problem happened a year ago , and the solution was to use "android.asyncPaint=false" temporarily . now this removed the black, but messed all the rendering while navigating between tabs.
So my question is why this happened now? the past three months i was developing and deploying on android without any problem. Did the newest update corrupt something?
Thanks
Sam
Using the android.asyncPaint flag is discouraged as it will fallback into a relatively slow compatibility mode. We are currently investigating some regressions in some rendering optimizations that affect some devices and are in the process of deploying a solution for that.
Please let us know if the issues persist.
So I have a website and I mean to make 2 version of it, the desktop version (with full features) and mobile version (simplification of the desktop version). I'm using media query in CSS to adjust the style. It works well in native browser. When I open my web using native browser it will show the mobile version style. But somehow when I open my web using Opera Mini, it keeps showing the desktop version instead.
I have googled it and didn't found any clue. Any idea how does it happen?
Thanks!
I finally found what's wrong with it. Turns out I was stupidly using #media screen only and Opera Mini doesn't seem handle it well. I've googled it for hours. Someone said actually Opera Mini supports #media screen but other people said that the right media property for Opera Mini is #media handheld. Well, I tried to play safe by simply changing it to #media all. And it works!
There are a number of reasons why Opera Mini is showing the desktop version of the site. The most likely is that your website is not properly detecting Opera Mini as a mobile site and is not returning the correct content. If you're using some plugin or other piece of software that is automatically handling the routing of desktop vs. mobile for you, that might be the culprit. Also, it's possible that this is happening by design, because of how Opera Mini works.
Opera Mini runs web content through Opera's own proxy servers and attempts to 'optimize' the content before delivering it to the user. That is, content is rendered first on the proxy server and then delivered to the device. This of course creates all kinds of complications for someone who is trying to deliver a consistent mobile web experience to their users. Fortunately, Opera provides a development guide to help give you a better sense of what's going on and how to cope with it.
Opera Mini is, in my experience, a very difficult browser to work with. At the Wikimedia Foundation, we server a very limited Wikipedia (and sibling project) experience when we detect someone's using Opera Mini.
You should definitely read through the opera mini development guide and make sure that any device detection you're doing is correctly recognizing opera mini as a mobile browser. If you're just using media queries, you may either want to reconsider a more robust approach to mobile detection, or adjust your design accordingly to work for opera mini. Good luck!
We have encountered something that looks like a Silverlight 4 rendering problem when running our Silverlight 4 app in FireFox 4 and 5 on MacBook’s. There is no problem in Safari or OOB (that’s
Safari I guess).
The problem is that large parts of the UI goes white and gradually reappears by moving the mouse over the white areas, or if the UI canvas is repainted.
We use Telerik controls in our app, but the problem can occur just by scrolling a list inside a scrollviewer, so I dont think its Telerik related.
We have only seen this problem on MacBooks, not on iMacs.
Have anyone else experienced problems like this? Is this a problem in the Sl plugin?
See screenshots below.
I can provide a video if necessary.
Link to an example from our Silverlight client in FireFox 5 on a MacBook: sl client on mac
Link to an example of our client with the rendering issue: sl client on mac with rendering issue
This question is also posted on Silverlight.net.
This looks like a problem with either Firefox for mac, or the SL client. Try making sure you're running the most up-to-date versions of both (since it has been almost half a year since you've posted this, there are new versions).
Have you tried to reproduce your problem on a different browser? Does it happen on chrome or safari? If so, then it's probably a plugin issue.
I don't think you can write SL code that will cause the problem you are experiencing, so the fault is not likely with you.
Does anyone know if silverlight plugs into chrome, or when they plan to support it?
This guy have had partial success with silverlight in chrome, but it does not seem to be supported:
http://wildermuth.com/2008/09/02/Silverlight_2_and_Google_Chrome
From The Microsoft Silverlight Team in the silverlight forum:
Hello, currently we don't have plans
to support Chrome. We will support it
in the future if it gains enough
market share. Please understand, each
browser implements the plug-in model
differently, so it'll be a lot of
effort to officially support a browser
100%... By the way, IE 8 also runs
each tab in its own process. If a tab
crashes, other tabs will still work
fine.
UPDATE:
Jon Galloway has just posted instructions on how to get silverlight successfully running on Chrome here:
http://weblogs.asp.net/jgalloway/archive/2008/09/17/silverlight-on-chrome.aspx
The official word on what is supported looks like this:
alt text http://www.jesseliberty.com/sl/browsers.jpg
The reality is that we do run on a lot of browsers, but things change might quickly in these here parts.
For what it is worth, the Dev Branch of Google Chrome was recently updated to support Silverlight 2. I tried it and it works for me. Of course, you have to use the Dev release of Google Chrome. You can get more information about switching to Chrome Dev here.
Silverlight already works with web-kit, and since Google's Chrome is based on web-kit, it shouldn't be too much effort to get it working.
Indeed, this gentleman seems to have had some success.
Based on this, I would suspect that Silverlight will be fully supported by Chrome by the time it goes gold.