When I set a breakpoint for an app which is currently running in full screen mode, I can not switch to any other screen when the breakpoint is reached. I'm stuck in the full screen app. The only chance I have is to hard reset the machine. I just found a single 7 year old post with Google that exactly describes my dilemma. There MUST be a solution (except having a 2nd machine) after 7 years seeing how much Apple is promoting this dreaded full screen mode.
Related
MacBook Pro retina (2013). Yosemite was doing fine; but after I upgraded it to El Capitan, I get white screen showing up every few minutes during regular coding and browsing. I searched online but most white screen problems of Mac users happened during the upgrade, but mine is during regular use. Anyone knows how to debug problems like this?
EDIT: some more clues --- 1. the pointer is still visible and I can move it around as well; 2. I can even take a screenshot of the white screen; 3. when I swipe up on touchpad I still get to "show my desktop", but after I swipe down the white screen comes back.
It sounds like there is a scheduled job that starts up in the background and runs an incompatible app. What does your console say when you reboot?
You need to remove 3rd party internet related software that isn't fully compatible with El Capitan and then reboot.
Also, did you try the fixes recommended
here.
Specifically
1) enter single user mode and run /sbin/fsck -fy
2) boot into safe mode
You may also need to remove these items (tuntap, a VPN software):
/Library/StartupItems/tap
/Library/StartupItems/tun
Win7 Directx 11 with VS 2012 -- When I let my app run in full screen on my development computer, eventually, the program exits full screen back to windowed, all by itself, and pops up a dialog telling me windows resources are running low. The dialog tells me something about turning off interactive themes or something to that end. When I run the program in release mode on one of our client machines, the app runs fine, does everything it should, but after a while, instead of popping up the dialog about windows resources, I get an exception window with exception 0x40000015 as the error. This only happens if I am in full screen, windowed, it never crashes. Event Viewer shows nothing at all about the crash. Any thoughts?
Thanks in advance. Basically what my app is, is a wrapper graphics library. When it says I am using all the resources, my resource monitor shows that I never went above 20% of memory and the cpu never went above 14%. The 0x40000015 error number is rather general and doesn't exactly point me in any real direction.
This is not related to trying to exit an app in full screen, as that I have the code required to prevent the exception related to that problem.
R
It turned out to be a component issue on the target platform. The ReportLiveDeviceObjects info was helpful and will continue to help down the line.
I created a small OSX app that takes a picture on the webcam every hour. However, as soon as the first webcam picture is taken, the app gets listed in the dreaded "Apps using significant energy" list under the MacBook battery menu. It then remains in this list until the app is closed.
However, when examined in Xcode, it is clear the app only consumes energy for the brief second that the photo is taken, as seen here:
Is there any way to tell OSX to re-audit energy usage? Or could I silently quit and restart my app after each photo to "clear its record"? How else can I get rid of this false bad-rap from the OS?
EDIT: Further research shows that simply accessing the camera is does not automatically put an app on this list. Apple's own Photo Booth app, for example, does not get listed even when it is filming video. I've edited the title and question to be more explicit about finding what it is that triggers this warning.
I'm using the popular ImageSnap code for taking the picture. The same issue happened with both the original and the new Mavericks-specific version.
I have developed a windows phone application and it works fine when it is open and running actively.
It tracks the user movements on the map and shows the position moves with push pins.
Now I want to ensure that the same application runs even the phone is locked when this app was open.
I have added the below code for it to work under lock screen. After this when I verified the app I realized it is not running when the application is locked.
Is there any other change I need to make to get this work under lock screen.Any help would be greatly appreciated.
private void initiliazesettings()
{
PhoneApplicationService.Current.UserIdleDetectionMode =
IdleDetectionMode.Disabled;
}
To have your app running under lock screen on Windows Phone 7.0/7.1/8.0, you need to set ApplicationIdleDetectionMode, not UserIdleDetectionMode. See details here.
Supossing you placed the method in the right place, that code only keeps the screen on, but doesn't make your app run in background when the lock screen is activated. Windows Phone 7 apps cannot run in background, they get tombstoned.
For Windows Phone 8 this is possible - see the sample here from MSDN.
However for Windows Phone 7/7.1 you can't do this.
You can prevent the screen from locking due to the user not interacting with it (as your code shows). However if you manually lock the screen the app will still be made dormant or tombstoned and your location code won't run.
Your only other option is to use a scheduled background task to read the location of the phone, but bear in mind that this is far from real time data (it is a cached location and you only run once every 30 minutes in the best case scenario).
I have this issue when debugging mobile apps on the emulator. When I press F5, the build starts, then the deploy, then the app pops up in the emulator.
Because this takes a minute or 2, I am checking my SO score and maybe ask a question while I wait, and the emulator is in the background. When I finally switch back to the emulator, it shows the start page, not my app.
I figured out that by pressing the back button I can bring the debugged application to the foreground, but still, I don't know what is pushing it into the background to begin with. Has anybody noticed this, and found a way to prevent it?
The default behavior in WinMo is that if the device has no activity for a certain period of time (set in Settings->Today->Items->Today Timeout), the Today screen will come to the fore. Check to see if that's what's happening (though I think the smallest interval is still larger than a couple minutes).