Is there a way to handle idle time in an NSApplication? In Win32 or
Carbon, since you manually write the actual while loop that processes
the events, this is pretty easy to do. Is there anything like this in
Cocoa? I've got some objects whose state (possibly) needs to be
updated, and I was
Is it possible to create a custom event for an apps internal usage and
have it posted to the NSApp, and then processed later on? If so, how
would one do this? I'm not sure how to
a) create the event
b) get notified when the event is recv'd and ready for processing
The event loop is whatever is
Your application's menu isn't that big of a deal, but your application's
integration with Mac OS X is a very big deal and that is most of the battle
of doing nib less development. It is much more than just populating the
main menu. Specifically, the application wrapper -- the .app --
Actually, reading the docs for +loadNibNamed:owner:, I think it is even
easier (but you'll want to test it). The owner is used to determine where
to look for the NIB.
If you were to create a subclass of NSApplication that lives within the
framework that has your generic MainMenu.nib and
I'd like to be able to create an application's menu from scratch,
without a nib file. I'm having problems doing so, I've looked around
and seen some different code samples but nothing seems to work
correctly.
The simplest case:
int main(int argc, char *argv[])
{
NSAutoreleasePool *pool =
You cannot throw C++ exceptions across Objective-C functions. If you want to
catch this exception, you will have to catch it in drawRect, and decide
there what to do with it.
The earlier emails seem to mention that for 64bit apps this will not
be a problem. Is that the case or did I
Is it possible to use NSWorkspace to open a file and pass in command
line arguments? I can't see anything in the docs about this and I
haven't found anything with google either.
Thanks
Jim
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please
I have found stuff on the internet about issues with throwing C++
exceptions, and I've run into something which I think is what these
articles are talking about but I'm not 100% sure so I thought I'd ask.
I have some C+ code that is being called as a result of the AppKit
framework updating a view
I'm developing this on 10.5, Xcode 3.0. Is that considered the newer
version, or is there an Xcode setting that I need to explicitly adjust
for this?
On Fri, Jul 4, 2008 at 3:45 PM, Bill Bumgarner [EMAIL PROTECTED] wrote:
In the 32 bit [legacy] Mac OS X runtime, C++ and Objective-C exceptions Do
64-bit is the sticking point. If you build for 64-bit, they're unified, but
Apple can't change the 32-bit runtime on the Mac for compatibility reasons.
So the switch would be setting the architecture to 64-bit and removing the
32-bit architecture. But of course then your app won't run on Macs
10 matches
Mail list logo
