I am working in a project where I am building two version of application native win32 and Windows Store App.
My rendering code is working in win32 but in Windows store app the screen is blank with clear color. I tried to debug the issue and captured some frame from Visual Studio Graphics Diagnostic tool. Interestingly the capture frame is showing full rendered screen with all objects showing (while the actual rendering window is blank)!
Can anyone give me some clue, what can be the issue?
Related
I've been following the examples for using SkiaSharp with Xamarin Forms, particularly the section on using bitmaps. I'm doing this in Microsoft Visual Studio 2017 version 15.9.11. I'm only targeting Android currently.
This page https://learn.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/graphics/skiasharp/basics/bitmaps has a section on Loading a Bitmap Resource, where the bitmap is an embedded image resource in the project.
So, we add the image and make it type 'embedded resource'
and then run the example code to simply display the image on the canvas.
string resourceID = "SkiaTest.Media.monkey.png";
Assembly assembly = GetType().GetTypeInfo().Assembly;
using (Stream stream = assembly.GetManifestResourceStream(resourceID))
{
resourceBitmap = SKBitmap.Decode(stream);
}
All pretty simple, and it works fine if I run the code on my phone if it is connected via USB in the standard way (a Sony Z5) so the second in the list here, not the Player:
Here it is working via USB:
But if I try and use Xamarin Live Player (the first in the list above) then it crashes on this line:
using (Stream stream = assembly.GetManifestResourceStream(resourceID))
Note that the app runs fine in Live Player if I don't try and load the bitmap, it's only that line that triggers the crash, and only in Live Player.
So I wonder if anyone has any ideas what could be causing Live Player to fail over this issue? Is the resource not being copied to the phone? Does Live Player just not support this type of activity?
The reason you are facing this issue is that Embedded Resources are not yet supported by Xamarin Live player which is causing this exception.
More details can be found in the Troubleshooting Xamarin Live Player document.
http://developer.nokia.com/community/wiki/images/thumb/9/9c/One.png/360px-One.png
http://developer.nokia.com/community/wiki/images/thumb/9/9c/One.png/360px-One.png
The image in this link shows some unidentified UI portion on the top right of the screen. Can someone please describe why it keeps on showing ?
I am unable to identify and correct it.
These framerate counters only shows up in development when the debugger is attached. You'll notice if you run your app when Visual Studio isn't connected and running this UI will disappear.
Here's some more info about it:
http://msdn.microsoft.com/library/windows/apps/gg588380(v=vs.105).aspx
And how to hide it if your really want to:
https://stackoverflow.com/a/5393504/250254
http://www.jeff.wilcox.name/2010/07/counters/
I'm the author of a Windows application that's been around for years. The app uses the wxWidgets UI library. For the newest version, we upgraded to the Microsoft c++ compiler in Studio 10 and to the latest Windows SDK library. We did not change much else in the app. Now, several users have reported that after a period of time running the app, the menus go crazy. All of the users reporting the problem are running on Windows XP. The menus either get huge, filling the screen, and have a giant italic font with strikethroughs. Or they get really small, so that the only thing shown are up and down arrows, suggesting the rendering code thinks the screen real estate is too small to display anything else.
You can find example screen shots here:
Once the menus go crazy, all menus are affected, except the standard Windows and MDI menus. The only way to recover is to restart the app.
The code in the app and wxWidgits is a thin layer on top of the standard Windows API. Once the menus are created, afaik Windows manages the rendering.
Any ideas what's going wrong?
I am developing apps for window phone 7 using phonegap. I am facing the problem when launching the apps in emulator. I can see the splashscreen but not the index page. I just see the white blank screen after splashscreen. While running on emulator I got message "this computer do not have required graphics processing unit configuration."
I test with other in built apps with visual studio for window phone. It work fine.
What is the problem? With my graphics or something else.
Did you set up your app to launch index.html. If you have change the tree it's not a problem. You can change it in CordovaLib, CordovaView.xaml, CordovaView.xaml.cs. In this one, you will find StartpageUri. Be sure that is pointing on your file
Flash CS6 won't display any AS3 projects while debugging anymore. When compiling for debugging it turns up white in the default "debug window" inside of Flash. If I right-click in the debugger window it says "Movie not loaded". No compiler errors are shown. The resulting swf file only runs if opened with the Flash Player from Finder.
This applies for all projects that I know have been working fine up until now. I've also tested to create a new, blank FLA on which I only draw a rectangle with the same result.
If, however, I select a Flash Player version prior to 10 (falling back to AS2) as the target for the test file containing only a rectangle, it does compile and show up fine.
I've uninstalled Flash and Flash Builder (and deleting any trace of the applications in the Library folders) and then reinstalled it multiple times without any result. I've also tried to uninstall Flash Player and Flash Player Debugger to no avail. For this I'm following the advice on Adobe's site and are using their Flash Player uninstaller applications, but it doesn't seem to uninstall all instances of the Players...
I believe the problem lies in the version of Flash Player Debugger that Flash uses internally to display the swf when debugging and it seems to somehow persist between re-installations. Is there a sure-shot way to reset this entirely?
Has anybody encountered this problem before?
I finally found the problem myself. It seems like the Chrome extension called FlashFirebug randomly causes these issues. When I deactivated the extension Flash started working properly again.