The Microsoft Teams splash screen stays open all the time.
How can I get it to close after Teams starts up?
I have exactly same problem. I believe that, in my case it was because I enabled NVidia's desktop manager. Microsoft might be hiding the splash screen outside virtual desktop area and NVidia desktop manager always brings it back to the viewable area of the desktop.
I have been personally using Microsoft Teams in my organization and it works fine every time i run it.
Check your network speed or computer memory usage from the task manager and see if there are some extra services running behind. You better close them.
Related
When a Windows 10 computer wants to share some of its screens using webrtc protocol (firefox navigator), a list of the windows that can be shared appears. In this list, only "normal" applications appears, not the one related to "apps". By example, spotify window appears, but OneNote window is not listed.
It seems (?) webrtc screen share is not compatible with UWP apps.
Knows someone a way to share the screen of an app via webrtc ?
Note: following link allows to reproduce this issue:
https://mozilla.github.io/webrtc-landing/gum_test.html
you do not need share anything, just push "window" and see the list of windows that appears.
I believe Chromium (the open source version - not sure about Chrome) faces the same problem as UWP requires to use a new Win 10 API which shows it's own window selector. And then obviously that selector doesn't work on other problems. So it's a common problem on Win 10, with no known good solution as far as I can tell.
How memory is managed if lot's of application is opened.
For example if user keeps opening apps and hits to windows button to turn back to home screen, how windows phone manages the memory?
Is there any limitation on this?
Usually when an app gets dismissed it will remain in memory but will no longer get any CPU time and therefore saves power. However it can also be removed from memory e.g. tombstoned. Here is an article on the states within the windows phone. The process of how to work with this state and getting back is described in this MSDN article.
HTH
My Windows Phone XNA game calls Guide.BeginShowKeyboardInput to get the user's name. While the Guide's input screen is shown, if the user presses the Home or Search (hardware) buttons, the game is deactivated as usual - but if the user then presses the Back (hardware) button, the game should resume but it doesn't. Instead it shows the "Resuming..." message until Windows Phone gives up trying to resume the game and kills the process.
Please note:
My app is failing Microsoft certification because of this problem - I really need to fix it!
This only happens in my game when the Guide input screen is shown - when it's not shown, the game
resumes properly after being deactivated.
This problem only occurs when the game is run on WP7.x (verified problem on WP7.5 and
WP7.8) - although the game seems to resume properly on WP8 devices.
I've created a blank XNA game project, called Guide.BeginShowKeyboardInput and tested it using WP7.x devices, and this problem-behavior doesn't occur.
I've tested the game without enabling Music & my Trial License manager (they use timers) and it still does this.
Exact same behavior occurs in the emulator (resume-failure on WP7.x emulators, works fine on WP8
emulator)
I used threads to asynchronously download content during the loading screen - but they already completed and exited.
I don't believe other threads are running, although this seems like
it could be a thread-blocking issue.
Any other ideas on what could be blocking the game from resuming when the Guide.IsVisible or how to debug/resolve this problem?
The solution to this issue was simply to NOT use SuppressDraw when dealing with any operation that passes control outside of the app, e.g. Launchers, Choosers and the Guide.
Have you tried calling "Guide.EndShowKeyboardInput" in either the Deactivating or closing events?
So that the guide is closed before the app suspends, you do get 10 seconds to suspend so this might be worth looking into.
If you want the guide to re-show on resume, then in your state saving code just have a flag and open the guide if it's set.
Microsoft declined to submit my application because I took a screen shot of the game which included the actual emulator.
Looking at this answer, the person says that I should us the snipping tool when I have made the phone emulator at 100%. And indeed, the snipping tools spits out an image of that screen at exactly 480x800 which is exactly what Microsoft wants. However, whenever I use the snipping tool, there is still the top black border of the WP7 remaining. I've looked at a few images on the Marketplace and other applications have it as well...I think. Some don't. Can anyone advice me on this please? How I can avoid getting penalised...again.
Will this suffice?
If you update to the Windows Phone 7.1 SDK and Emulator, the new emulator has a built-in screenshot function to take screenshots without these issues.
I have never had my app rejected due to a screenshot taken from the emulator, I can't say you wont have issues, but assuming everything else in your screenshot checks out; the images from the emulator are the correct size and should be approved.
After I've shut down a VS 2008 web project, well, a lot of times, I see many instances of the WebDev icon in the "tooltray" / system notification area:
These are no longer active instances; they were shut down by VS.
When I mouse over any of these, Windows Vista "conveniently" collapses the tray for me. This makes life miserable if the app I want is in between any of them (e.g., Outlook in the image above), and even worse if I actually want to right click on the "active" WebDev.
Any idea how I can get VS, WebDev, or Windows to fix this behavior?
There is a utility on CodeProject that does this: TrayIconBuster
http://www.codeproject.com/KB/system/TrayIconBuster.aspx
It runs every x minutes and removes all phantom icons...
Not the perfect solution, because I think this should be built in to Windows...