The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
As Shaggy Frog said, define a macro in your YourAppDelegate.h file, an example like this:
ReplyDelete#define AppDelegate (YourAppDelegate *)[[UIApplication sharedApplication] delegate]
Then you can get the app delegate in your code like this:
[AppDelegate ......];
Since your app delegate never really changes, you can create an external that you define in the app delegate code, very similar to the NSApp external for Mac OS X Cocoa applications.
ReplyDeleteSo, define the external in your AppDelegate header (or something else that you would include everywhere):
extern AppDelegate* appDelegate;
Then create it and set it in your implementation file:
AppDelegate* appDelegate = nil;
// later -- i can't recall the actual method name, but you get the idea
- (BOOL)applicationDidFinishLaunchingWithOptions:(NSDictionary*)options
{
appDelegate = self;
// do other stuff
return YES;
}
Then other classes can just access it:
#import "AppDelegate.h"
// later
- (void)doSomethingGreat
{
NSDictionary* mySettings = [appDelegate settings];
if( [[mySettings objectForKey:@"stupidOptionSet"] boolValue] ) {
// do something stupid
}
}
You could just create a C-style macro and put it in a header file somewhere.
ReplyDelete(As for using your app delegate as a giant global variable catch-all, that's another rant for another day.)
I create a category called UIApplication+delegate with some convenience messages in it. Getting my specific delegate being one of the convenience messages. So, for instance, if my app delegate was called MyAppDelegate, it would look like this:
ReplyDeleteUIApplication+delegate.h
#import "MyAppDelegate.h"
@interface UIApplication(delegate)
+ (MyAppDelegate *)thisApp;
@end
and UIApplication+delegate.m
#import "UIApplication+delegate.h"
@implementation UIApplication(delegate)
+ (MyAppDelegate *)thisApp {
return (MyAppDelegate*)[[UIApplication sharedApplication] delegate];
}
@end
In a class that needs the delegate, I do this:
#import "UIApplication+delegate.h"
...
- (void)doStuff {
MyAppDelegate *app = [UIApplication thisApp];
// use "app"
}
I also created a category, except that I applied mine to NSObject so any object in the application can easily get to the delegate.
ReplyDelete#import "MyAppDelegate.h"
@interface NSObject(delegate)
- (MyAppDelegate *) appDelegate;
@end
#import "NSObject+delegate.h"
@implementation UIApplication(delegate)
- (MyAppDelegate *)appDelegate {
return (MyAppDelegate *)[[UIApplication sharedApplication] delegate];
}
@end