Is there any way to cause the system to re-read
com.apple.symbolichotkeys.plist.plist in Cocoa (or anywhere else)? I want to
programmatically change a shortcut (which is no problem), but I want it to
take effect immediately. System Preferences obviously signals the system to
do this -
Hi list,
Is there any way to cause the system to re-read
com.apple.symbolichotkeys.plist.plist in Cocoa (or anywhere else)? I want to
programmatically change a shortcut (which is no problem), but I want it to take
effect immediately. System Preferences obviously signals the system to do this
I tightened up the code a bit:
#Obj-C version: - (id)initWithContentsOfURL:(NSURL *)nibFileURL
nib_file = NSNib.alloc.initWithContentsOfURL NSURL::fileURLWithPath(@@NibPath)
#Obj-C version: -
(BOOL)instantiateNibWithOwner:(id)ownertopLevelObjects:(NSArray
**)topLevelObjects
#The Ruby bridge
Really, the external name table is for referring to objects in nibs, rather
than pushing objects into nibs.
Thanks. That's what I wanted to know - I thought the docs suggested maybe you
could pass objects in (other than owner)
Furthermore, from your further description it sounds like what
Hi list!
I'm writing a RubyCocoa app, but my question is on the Cocoa API...
I'm trying to unit test a view class. As it is very thin (just delegates all
work to the controller), all I want to check is that my connections (e.g.
outlets and actions) are hooked up correctly.
I've been trying
H, my NSAppleScript Class Reference documentation does not list
any such method. It does list -executeAppleEvent:error: and -
executeAndReturnError:, both of which return The result of
executing the event, which implies that they must wait for the
script to complete.
Ha ha, yes,
When I use [NSAppleScript executeAppleEvent] to call handlers in a
compiled script, it returns immediately.
Is there a way to get it to block until the script is finished? Maybe
there a notification I can listen for?
Thanks!
Sean DeNigris
s...@clipperadams.com
In main.m:
NSUserDefaults *args = [NSUserDefaults standardUserDefaults];
int x = [args integerForKey:@x];
int y = [args integerForKey:@y];
If the command line is MyApp -x -100 -y 100, NSUserDefaults does
not recognize the -100 as the value of the x argument - it sets x
to 0.
What Alastar said; you have free reign over argv/argc prior to
calling NSApplicationMain().
Duh! You're right, I will just process them myself! I don't know why
I was so attached to making NSUserDefaults do what I wanted it too -
probably lack of sleep and frustration with the
When using NSUserDefaults to get command line arguments, it doesn't
seem to handle negative numbers correctly.
In main.m:
NSUserDefaults *args = [NSUserDefaults standardUserDefaults];
int x = [args integerForKey:@x];
int y = [args integerForKey:@y];
If the command line is
10 matches
Mail list logo
