None of the permutations I tried resulted in bad behaviour. I tried to get the build to switch to the wrong configuration by selecting various modes while launching and quitting different combinations of applications that normally prompt the discrete GPU to activate.Then I tried to see if I could find ways to make build perform the wrong behaviour. It passed them all.įirst, I tested it in situations that triggered the bug when using the standard build, and build handled them all excellently, every time. I put it through various tests to make sure that it did what it is supposed to do, and that it did not do anything it shouldn't do. Sorry, something went version seems to work perfectly. I think a better solution would be to first select Dynamic Switching to ensure the smoothness, then change it immediately afterwards to the user's last selected preference. Do note that forceSwitch doesn't help in this case, since it resolves any discrepancy to the system mode, while my solution resolves it to the user's preference, which is how it should be.ītw, I have also read that you have selected Dynamic Switching to default upon login so that the app runs smoothly.In the displa圜onfigurationCallback section in GSGPU.m, if the user has selected Integrated Only but the discrete graphics is on, there will be a call to to change it back to Integrated Only.Created a static variable in GSMux to note which mode the user has selected.The few lines of code I've added in fixes this problem: The problem is that the mode will change to Discrete Only after certain apps which use Core Graphics close, such as Chrome or iOS Simulator. I have been a fan of your app for a long time, using it to force the Integrated Only mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |