I'm writing a SharpDx(directX) Windows Phone 8 game where everything worked until now. When I changed the size of the DrawingSurface, the phone screen during debugging was only black. Immediately I have everything undone and uninstalled the app, then the screen was still black. Now I have checked with breakpoints where the program stops working, at the end came out that, the phone every line passes through to the line
TouchCollection touchCollection = TouchPanel.GetState();.
After that nothing happens, there is also no warning or anything. However, when I start the app without debugging, I can easily operate the app.
Has anyone an idea?
Here is a Screenshot:
![]]1
I have now found the solution to my problem.
Solution(Very simple):
The DrawingSurface doesn't work because an Microsoft Advertising SDK has disturbed it.
Related
Yo. Some of you might already know but Xamarin Apps are booting pretty slow and the delay occurs before any line of code is executed - at least i figured that out with some breakpoints.
So i want to cover that up using a Splashscreen. But since Xamarin is for multiple platforms i'd like to... welll... use cross platform code.
The most important part is: i do NOT want to cover my code delay. I want to App to NOT open with a white blank screen like it currently does, but e.g. with an image or some animation or such stuff.
and yes i already googled a little but everything i found seemed to be android specific or iphone stuff, or it just takes affect after the system boots.
There is no cross-platform way to do that yet. (Answering in 2017/Dec)
You'll need to make it for each platform.
Android: https://developer.xamarin.com/guides/android/user_interface/splash-screen/
iOS: https://developer.xamarin.com/guides/ios/application_fundamentals/working_with_images/launch-screens/
I am building a WPF Application that is going to be used on Desktop as well as on a Surface Pro Tablet running the Win10 Creators Update.
If a Textbox gets Focus the onscreenkeyboard of Win10 should open on the bottom of the screen and move the application up the screen to push the focused element back into view.
I have implemented WpfTabTib which worked pretty well until we updated the tablet to the creators version. Technically it is still working but with an ugly animation moving the window up, down and up again to open the keyboard.
Having read that microsoft adjusted the behaviour of the keyboard to match the uwp behaviour I have updated my .Net framework to 4.6.2 without the hoped result. It seems Microsoft doesn't care for this behaviour.
Does anyone have the same problem or an different approach for me ?
Thanks a lot!
Edit: Updating the Tablet to an Insider Preview of the coming Windows Fall Update changed the behaviour again: The opening animation is now a little better, but still far from nice. And as new problem closing the osk doesn't move the application back down.
i am using xbox one to developo my app in windows 10 using kinect sdk 2.0 .The problem is Hand cursor not showing up.
After a couple hour of research on internet, found nothing :(
but finally I solved the solution posted on many forum. Guys here is the solution.
"Controls Basics-WPF" code run without showing any problem on windows 8, we can move around the hand cursor and so on.. but the problem was in windows 10. no hand cursor no fun at all... just extra work to solved out the problem. i was about to install windows 8 as i am working at Kinect Fitting Room APP in WPF.
but thank God finally I solved out the problem and thought to help out you guys.
A little Magic trick. Its already in the app but we never tried it :D
In Debug or Release mode select either x86 or any cpu, no problem at all.
Just go to "Engagement and Cursor Setting" in the app. leave just first option of Engagement style which is set by default. the first option for Engagement style is not working at all in windows 10 (system hand open/ still).
select option Manual (hand over head) or (hand on screen) and there we can get our hand cursor working exactly as in windows 8.
and the magic works :D
Glad to help who are still stuck.
I'm dealing with a strange issue that's been giving me headaches for a long time.
I've got a Windows Phone 8.1 (WinRT) app, whose first version I published a couple of years ago. Over the last few months, I've been working on a major update which includes augmented reality as the most prominent feature.
Obviously, the app needs to make use of the camera preview, and that's where trouble starts. I've read discussions in other threads about problems with the camera API, but I didn't find a definite solution.
Before submitting the update, I performed extensive tests on my Lumia 620 and all worked fine. But if the app is downloaded from the store, it crashes and the camera picture goes green as soon as the camera preview starts. It is the very same app package and all required capabilites have been declared.
So basically I can't tell if my app works or not, unless I submit it to the store.
Any help will be appreciated.
Edit: After several hidden-app submissions, I've narrowed down the cause of the crash to the following block of code:
RandomAccessStreamReference rasr = RandomAccessStreamReference.CreateFromUri(new Uri("ms-appx:///Assets/Square44x44Logo.scale-100.png"));
var streamWithContent = await rasr.OpenReadAsync();
The last of the above lines causes the app to terminate. The same code works fine when the app is deployed from VS.
Any ideas?
It looks like the problem is now resolved. The cause of the crashes was the asset file. This file is a scaled version of the app tile, which is created automatically by Visual Studio. Using this file is allowed when the app is deployed from VS, but not in the store.
I am currently developing an app that seems to hang my Windows Phone 7 phone. If I start the application and then press the home button or use the back arrow and then repeat this several times then the phone actually hangs in the middle of the app start animation and I need to restart the phone.
To troubleshoot this issue I created a new project and removed all my code and put there my xaml and animations only. My xaml with the animations inside are about 2800 lines long. When used under debugger no exceptions are thrown nor any other error messages are shown.
I created a project for demonstrating my issue. Here are the steps to reproduce the problem
Open the project in Visual Studio
Select Windows Phone 7 Device
Run the application.
Start using the home or the back button to quit the app and then relaunch it again and again.
Repro_Crash - This is the project that I am using to reproduce my issue.
Image of the Crash - from this point I am forced to restart the phone.
I am looking for hints or tips regarding how to figure out what is happening!
I've tried your project and it runs perfectly fine on my HTC HD7 NoDo. It displays only a large wall of letters without any animations and does not crash the phone. I'm using the latest Mango Beta 2 Refresh SDK.