Allowing UIKit to handle device rotation in OpenGLES 1.1 is actually all slower, and if so, under what circumstances?

I allowed UIKit to handle the rotation of the device for me (my iOS application has UIViewControllerone that implements shouldAutorotateToInterfaceOrientation:), and I was very pleased with how simple it was to make it all work.

Since then I have been told that this is slower than doing all the rotation operations manually. However, this did not confirm my tests, however, on the iPad (iOS 4.2) or on the iPod Touch 2G (also iOS 4.2).

I was a little surprised when I was told that in any case there will be a big difference, because judging by how UIKit works, it seems that OpenGLES does not have the ability to flip pages. So -[EAGLContext presentRenderbuffer:]to a large extent, I have to make a copy that will take basically the same time regardless of the state of rotation. The overhead for other aspects of rotation (mainly general coordinate transformations) I would suggest that they are also negligible.

This is only my hypothesis, and I have only my lying eyes to support her! So whether there are cases when UIKit processes the rotation of the device, is it really of great importance? If so, then who are they?

+3
source share
1 answer

- : iPhone 3GS, iPhone 4, iPad, iPad 2, iPod touch 3G, iPod touch 4G iOS 4.2 .

iOS, OpenGL ES. , , , , OpenGL ES 2.0, , , OpenGL ES 1.1 .

, , ES 2.0, , , .

+1

Source: https://habr.com/ru/post/1784851/


All Articles