To fix this, all you need to do is add the following line of code – I placed this in the applicationDidFinishLaunching method:
// Required so UIAlertView shows in the correct orientation in landscape mode
[application setStatusBarOrientation:
UIInterfaceOrientationLandscapeRight animated:NO];
Prepares the receiver for service after it has been loaded from an Interface Builder archive, or nib file.
- (void)awakeFromNib
The nib-loading infrastructure sends an awakeFromNib message to each object recreated from a nib archive, but only after all the objects in the archive have been loaded and initialized. When an object receives an awakeFromNib message, it is guaranteed to have all its outlet and action connections already established.
You must call the super implementation of awakeFromNib to give parent classes the opportunity to perform any additional initialization they require. Although the default implementation of this method does nothing, many UIKit classes provide non-empty implementations. You may call the super implementation at any point during your own awakeFromNib method.
Note: During Interface Builder’s test mode, this message is also sent to objects instantiated from loaded Interface Builder plug-ins. Because plug-ins link against the framework containing the object definition code, Interface Builder is able to call their awakeFromNib method when present. The same is not true for custom objects that you create for your Xcode projects. Interface Builder knows only about the defined outlets and actions of those objects; it does not have access to the actual code for them.
During the instantiation process, each object in the archive is unarchived and then initialized with the method befitting its type. Objects that conform to the NSCoding protocol (including all subclasses of UIView and UIViewController) are initialized using their initWithCoder: method. All objects that do not conform to the NSCoding protocol are initialized using their initmethod. After all objects have been instantiated and initialized, the nib-loading code reestablishes the outlet and action connections for all of those objects. It then calls the awakeFromNibmethod of the objects. For more detailed information about the steps followed during the nib-loading process, see Nib Files and Cocoa in Resource Programming Guide.
Important: Because the order in which objects are instantiated from an archive is not guaranteed, your initialization methods should not send messages to other objects in the hierarchy. Messages to other objects can be sent safely from within an awakeFromNib method.
Typically, you implement awakeFromNib for objects that require additional set up that cannot be done at design time. For example, you might use this method to customize the default configuration of any controls to match user preferences or the values in other controls. You might also use it to restore individual controls to some previous state of your application.
#import
uint64_t start = mach_absolute_time();
// do stuff to be timed
uint64_t end = mach_absolute_time();uint64_t elapsed = end - start;
mach_timebase_info_data_t info;if (mach_timebase_info (&info) != KERN_SUCCESS) { printf ("mach_timebase_info failed\n");}
uint64_t nanosecs = elapsed * info.numer / info.denom;uint64_t millisecs = nanosecs / 1000000;[[UIApplication sharedApplication] setStatusBarHidden:YES animated:NO];
Ez viszont onmagaban meg nem eleg, mert a View teteje ugyan felkerul a Status bar helyere, de letakarja egy darab a Root View Controllerbol. Akkor mukodik jol, ha az xx-Info.plist-ben felvesszuk a "Status bar is initally hidden" kulcsot es kipipaljuk. Ezutan persze ahol latni szeretnenk a Status bart, ott kulon meg kell adni a fenti hivassal, hogy NE legyen hidden, de ahol azt adjuk meg, hogy legyen hidden ott tenyleg az lesz.
A masik lehetoseg, ha nem nyulunk az Info.plist-hez, hanem az AppDelegate-ben az applicationDidFinishLaunching-ban allitjuk be YES-re mielott a window-hoz hozzaadnank a Sub View-t. Ezutan akar vissza is allithatjuk NO-ra es csak ott valtoztatunk rajta ahol kell.
A lenyeg, hogy miutan egy Sub View-t mar hozzaadtunk a window-hoz, akkor mar hiaba rejtjuk el a Status Bar-t, ha elotte nem tettuk meg akkor hibas lesz. Ez valami bug lehet, a 3.1.2-ben amit gondolom kesobb majd javitanak.
Defining a category is identical to defining the interface for a class, with one small exception: you add a category name inside a set of parenthesis after the interface declaration..."
Categories and Extensions leiras az iPhone OS Reference Libraryban