Create an Xcode / Interface Builder Application Written In AppleScript

Hi.
I've got what's probably a stupid and easy question.
I have some AppleScript programs that I'd like to create custom interfaces for.
I've read about AppleScript Studio.
I've read that to create an Xcode project written in AppleScript, you can just select 'AppleScript Application' from the New Project window.
However, the New Project window that I get looks entirely different (newer) and the closest thing that I can find is 'Cocoa-AppleScript application', which doesn't work.
So, is there a way for me to use Interface Builder and Xcode with my AppleScript programs, short of learning Objective-C and converting everything?
I'm using 10.6.2, Xcode & Interface Builder 3.2.1.
Thanks in advance!

You don't really need to know Objective-C, although it does help a bit with understanding the examples and code snippets in the Cocoa documentation. See my reply to your other topic.

Similar Messages

  • Xcode: Create An Application Written in AppleScript

    Hi.
    I've got what's probably a stupid and easy question.
    I have some AppleScript programs that I'd like to create custom interfaces for.
    I've read about AppleScript Studio.
    I've read that to create an Xcode project written in AppleScript, you can just select 'AppleScript Application' from the New Project window.
    However, the New Project window that I get looks entirely different (newer) and the closest thing that I can find is 'Cocoa-AppleScript application', which doesn't work.
    So, is there a way for me to use Interface Builder and Xcode with my AppleScript programs, short of learning Objective-C and converting everything?
    I'm using 10.6.2, Xcode & Interface Builder 3.2.1.
    Thanks in advance!

    One possible explanation for the lack of Apple provided documentation is that AppleScriptObjC revolves around knowing, or at least, understanding some Objective-C. To write application in AppleScriptObjC, you must know how to read and understand existing Objective-C code and the developer documentation for Objective-C.
    There is a learning curve, but there was also a learning curve to AppleScript Studio and it was a tremendous pain in the rear to use. The more you use AppleScriptObjC, the more you will begin to understand Objective-C and the easier both will become.
    It is very exciting the direction Apple has taken AppleScript with AppleScriptObjC. It may be difficult to see this now but once you are comfortable using it, you will see its power, flexibility and ease of use.
    *Videos on YouTube*
    http://www.youtube.com/user/AllanCraigTutorials?feature=mhw4
    *Apple's Release Notes.*
    http://developer.apple.com/mac/library/releasenotes/ScriptingAutomation/RN-Apple ScriptObjC/index.html
    *Resources with AppleScriptObjC examples.*
    http://www.scriptingmatters.com/ASObjC
    http://www.tidbits.com/matt/
    http://allancraig.net/
    http://macscripter.net/
    *Resources for Learning Objective-C*
    http://allancraig.net/index.php?option=com_content&view=article&id=92:sources-fo r-learning-objective-c&catid=39:objective-c&Itemid=86

  • Can I upload apps made with xcode Interface Builder to the App Store

    Like my title says Can I upload apps made with xcode Interface Builder to the App Store? I'm currently making an app with the interface builder from xcode and I was wondering if I could upload it like that to the App Store.
    Please help me with this.

    Hi seba,
    In order to be able to submit apps to the App Store, you need these things:
    1. An Apple ID
    2. Join the Mac developer program ($99) https://developer.apple.com/programs/mac/
    Once you've got these, you're free to submit your created applications to the App Store. It should walk you through the process

  • Make a button do something Xcode/interface builder

    How can i make a button placed in interface builder do something

    Well, that isn't much better - I am going to guess that your application is for Mac OS X in Objective-C.  Since something like a button is pretty basic, you either need some help with Xcode, or a conversion from some other programming language you know, or both.
    There is a basic button tutorial here that uses the older Xcode (there shouldn't be much difference), although you should look at getting Xcode 4.2 (free from the AppStore), since that is what is current.
    I don't do much in Obj-C so I can't help with good books, but Apple has a few documents on its developer site that should get you started (although most of their documentation has moved on to Xcode 4.

  • DELETE or make TITLE BAR INVISIBLE in XCODE INTERFACE BUILDER

    Im trying to figure out how to make the title menu invisible or to simple delete it all together, it serves no purpose in my app, and i would really like it to be gone, any ideas?

    >The only trick is that you have to load the NIB file manually. Here's the code to put up your >dialog:
    >
    >IBNibRef dialogNibRef = NULL;
    >WindowRef windowRef = NULL;
    >CFBundleRef bundle = CFBundleGetBundleWithIdentifier(kMyBundleIdentifier);
    >CreateNibReferenceWithCFBundle(bundle, kMyNIBName, &dialogNibRef);
    >CreateWindowFromNib(dialogNibRef, kMyWindowName, &windowRef);
    >DisposeNibReference(dialogNibRef);
    >
    >Having done this, you can show the window using RunAppModalLoopForWindow.
    Could you please explain these steps more in detail Aaron. I've setup a UI using the Interface Builder and have put the above mentioned code into DissolveUIMac.cpp but i am getting the following errors:
    error: 'kMyBundleIdentifier' was not declared in this scope
    error: expected constructor, destructor, or type conversion before '(' token
    error: expected constructor, destructor, or type conversion before '(' token
    error: expected constructor, destructor, or type conversion before '(' token

  • Yet another cocoa without interface builder post

    I am sure its been brought up before. I would like to know if its possible to write Cocoa apps without Xcode, Interface Builder, or NIB files in general; another words, write Cocoa programs programmatically using ONLY Objective C. Before you ask me why I would want to do such a thing and that I am crazy, please hear me out.
    I come from a Win32 background, and my primary languages are C and C++. I am getting used to Objective C (though I wish I could use C++ to program in Cocoa). I picked up a copy of Cocoa(R) Programming for Mac(R) OS X (3rd Edition) by Aaron Hillegass, and have been trying to learn cocoa from it for the last few months. Basically, I am having big trouble wrapping my mind around cocoa via the very conceptual high level approach this book takes. I can not for the life of me begin to understand this whole making connections with interface builder.
    I do NOT plan to write production applications in cocoa by hand, but if I could just write a few trivial applications in cocoa by hand without interface builder or nib files, perhaps when I do use interface builder, I won't have such a hard time understanding whats going on.
    Thanks in advance for the help.

    __mikem wrote:
    I am sure its been brought up before.
    I don't care. Your question isn't about learning how to program and learning via the iPhone SDK. I'll do anything I can for you
    I would like to know if its possible to write Cocoa apps without Xcode, Interface Builder, or NIB files in general; another words, write Cocoa programs programmatically using ONLY Objective C.
    Certainly. You can write command-line Cocoa apps. Xcode is just an IDE like Visual Studio.
    Before you ask me why I would want to do such a thing and that I am crazy, please hear me out.
    I come from a Win32 background, and my primary languages are C and C++. I am getting used to Objective C (though I wish I could use C++ to program in Cocoa). I picked up a copy of Cocoa(R) Programming for Mac(R) OS X (3rd Edition) by Aaron Hillegass, and have been trying to learn cocoa from it for the last few months. Basically, I am having big trouble wrapping my mind around cocoa via the very conceptual high level approach this book takes. I can not for the life of me begin to understand this whole making connections with interface builder.
    You specifically asked to avoid the topic, but I'm sure there are several of us who are really tired of iPhone questions who would be happy to try our hand at explaining the User Interface architecture in Cocoa - if you want to try.
    I do NOT plan to write production applications in cocoa by hand, but if I could just write a few trivial applications in cocoa by hand without interface builder or nib files, perhaps when I do use interface builder, I won't have such a hard time understanding whats going on.
    You can write Objective-C programs using whatever editor and IDE/makefile you want. You can even work with all the non-UI parts of Cocoa to get a feel of how it works. Technically, you could write code using only Carbon and never use Objective-C, but that is really a dead-end.
    A good idea might be start looking at doing writing MacOS X kernel extensions. You should still use Xcode, but only as an IDE. The code would all be C++ (or a subset thereof) with no user interface or NIB files. Realistically, that is probably harder than learning Interface Builder, but it is probably the most productive path available to you for developing MacOS X and avoiding Interface Builder.

  • UITableViewCell and the Interface Builder

    I'm trying to use the Interface Builder to create a UITableViewCell but am having problems.
    I can create the UITableViewClass in my .xib file, connect the reference outlet and reuseIdentifier using the inspector. The problems occurs when I try and render the cell with this method...
    - (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath
    Since the interface builder creates the TableViewCell automatically, I should be able to call...
    UITableViewCell *cell = [[[UITableViewCell alloc] initWithFrame:CGRectZero reuseIdentifier:@"priceCell"] autorelease];
    ..from inside the tableView:cellForRowAtIndexPath method and get that cell instance. But none of changes (Color, accessory view, etc...) I made to the table view come through.
    Has anyone got UITableViewCells created in the interface builder to work?

    Just an update to inform people of some of my findings.
    I had originally, before gkstuart's post, had added a UITableViewCell instance as a child of my view in IB. I then tried to use the cell via an IBOutlet in the UITableView in my view. This is when I was getting a completely blank screen when running my application. I then adopted gkstuart's idea and created a cell factory class, but without thinking, I used the same cell instance on each call to my 'newCell' method. Once I updated the 'newCell' method to load the nib file on each call to 'newCell' everything seems to work fine. As a note, the nib file loaded by 'newCell' is a simple nib file containing only my custom cell definition. It does not contain any views. Gkstuart's method of loading custom cells is unfortunate, because you can't seem to use the reusable cell theory when working with cells defined in IB. This is obviously something that needs work on Apple's side.
    As a test, I removed my custom cell definition from my original view nib. I then added a new top level instance of UITableViewCell, by dragging the UITableViewCell item to the window with the File Owner icon. After updating the custom cell definition with the appropriate class and outlets, I tried my original method again. I no longer get a completely blank screen, but it still doesn't work right. I now get a single cell in my table view, which happens to be the last cell in the list. When looking at it with the debugger, dequeueReusableCell never returns my cell instance so I am reusing and returning the same cell for each call to 'cellAtIndexPath'. I tried to manually call the cells 'prepareForReuse' method but this didn't seem to have any affect.
    So at this point, I am going to continue with the cell factory methodology until Apple either fixes the current problem or informs people on the proper way to use IB with custom UITableViewCell's.
    As a side note, I am going to start blogging about my experiences with the iPhone SDK over at iphonesdktrialsandtribulations.blogger.com.

  • Range of Variable in Web Interface Builder

    Hi,
    I have created a Web Interface Builder in BW-BPS. I have created Cost Center as a Variable. However, I am unable to get this range of cost centers say 1001 to 1005 in Web Inteface Builder.
    Whereas, in the Planning Folder, this works fine and I am able to select the range of Cost Centers from 1001 to 1005.
    The issue is only with WEB INTERFACE BUILDER.
    Looking forward for some valueable inputs.
    Regards,
    Ravi

    Hi Mayank,
    Thanks for your reply.
    I will also look at the different options given.
    I also found the following thread is more useful.
    BSP Value Help Input Field and Select-Options Ranges
    I will let you know on this.
    Regards,
    Ravi

  • Interface Builder Bug?

    I have a cocoa program that I have I am writing on a 10.6 system, but targeting to 10.5.
    On the 10.6 system, it works fine. However, when I run it on the 10.5 machine, I get:
    The sender of menu item actions is now the NSMenuItem, not an NSMatrix. A menu item action method appears to be trying to send the NSMatrix method 'accessibilityIsIgnored' to its sender. This is no longer valid. Please change the code.
    I looked this up online and found that one place implies that I'm calling "accessibilityIsIgnored" in my code, which I am not, or that there are multiple copies of the InterfaceBuilder library on the system, which there are not.
    has anyone else seen this?

    Actually, that looks like a very, very old error message. It seems to have been encountered only by you and one other person back in 2003. Do you have some old versions if the interface Builder application? Are you linking some ancient libraries?
    Can you reproduce the error in a new, template-based HelloWorld application?

  • Trying to create first iPhone app, use Interface Builder or Xcode first?

    I'm trying to create my first iPhone App, do I start with Interface Builder or Xcode first? And how do I link the two together?

    It's not really that simple -- you'll be working with both. Interface Builder is used to design the GUI (graphical user interface, which consists of the windows and buttons and text fields and so forth, the parts of the application that your user interacts with). Xcode, on the other hand, is used to write the code that tells that GUI what it's supposed to do, and how to do it. So, to answer your question as best I can -- generally, I would imagine you would want to start by creating the basic form of your GUI in Interface Builder and then start coding where appropriate in Xcode, then you'll move back and forth between the two (Xcode and Interface Builder) as needed.
    If you're new to programming and want to start with iPhone apps, I recommend picking up a book on the topic (Apress publishing has a book called "Beginning iPhone 3 Development: Exploring the iPhone SDK" that is a good one, and don't forget to take advantage of Apple's iOS Dev Center, which has lots of good documentation on most any topic that will be helpful in supplementing the information in the book you buy -- click [here|http://developer.apple.com/iphone/index.action] to go there).
    Keep in mind, however, that trying to learn to program iPhone apps will be difficult (to say the least) if you don't already know Objective-C, and the Apress book I recommended above will not be easy to follow without understanding Objective-C first. Objective-C an object-oriented extension of C, and it is the programming language that is used to develop iOS apps (apps for the iPhone, iPod touch, or iPad). I would definitely recommend learning Objective-C on the Mac before jumping in to iPhone development in specific. Apress has another book called "Learn Objective-C on the Mac" that I would recommend for this.
    Furthermore, since Objective-C is an extension of C, you won't have an easy time learning it without a prior understanding of the C programming language. Again, Apress has a book for this, called "Learn C on the Mac."
    Put simply, learning to program for the iPhone is not something that comes overnight -- it's a step-by-step process that takes patience, and you have to be willing to go through these steps if you want to learn to program properly for the iPhone.
    Step 1 -- learn the C programming language
    Step 2 -- learn the Objective-C programming language
    Step 3 -- apply your knowledge to developing for iOS (iPhone's operating system) with the Cocoa Touch framework
    Anyways, that's just my advice -- I definitely recommend taking the time to do it right and not jumping straight into the deep end, but in the end only you know what works best for you. Also, like I said, I definitely think investing in a book on the subject is worth the time and money, so let me know if you want any other recommendations for books beyond the ones listed above.
    Hope this was helpful to you, and best of luck with your journey toward programming for iOS.

  • I am new to xCode and SDK Disks. My Interface Builder will not work and 'quit's unexpecteldy'. What can I do? I really want to create an applicaiton. Thanks

    Hi, I am a new user to xCode and just recently downloaded a SDK Disk image and also an older version of xCode from the Apple Developer site. I opened the 'Interface Builder' for the first time and it worked. Next, when I tried to open it again (with and without the xCode 'Mainmenu.xib' attachment file from xCode) it kept showing the message "it quit unexpectedly".
    I need to create an application for a project I am working on. If anyone who can resolve my problem of why the Interface Builder is not working, that will be great.
    If you need additional details (like which versions etc.) please ask, for I am desperate to find an adequate solution to this problem.
    Thanks.

    If you need additional details (like which versions etc.) please ask, for I am desperate to find an adequate solution to this problem.
    Without intending any disrespect, if you had suspected these would be questions and if you're in a hurry for an answer, then why did you exclude the information?  And yes, knowing the Mac OS X version (preferably Mac OS X 10.5.8 or 10.6.7) , as well as the Xcode version might shed some light on this.  Might.  And I'll presume there's a specific reason you downloaded what I will assume is an Xcode3 version.
    Was this an existing Xcode project, or did you start with a new project here?  If it's an existing project, it could well have a corruption or an incompatibility.
    Initially, I'd probably start with a new project, and load in newly-copied source files.  On the off chance the project is corrupted.
    Failing that, I'd deinstall Xcode using the documented procedures, and would then reload it.  If there was an old version of Xcode around on the system, sometimes wonky stuff can happen with an installation.
    And FWIW, the Apple Developer Forums and the Apple mailing lists tend to see far more developer-related traffic than do these particular forums.  (There's an Xcode users' mailing list around which sees regular traffic, too.)

  • Cannot open nib - The application Interface Builder quit unexpectedly

    Just installed the iPhone SDK and installed sample code. The Interface Builder will not start. At startup, the following message is displayed: "The application Interface Builder quit unexpectedly."
    I've tried the standard Xcode SDK and it has the same problem. I've repaired permissions on the disk, to no avail. I'm stumped on this. Thanks for any suggestions.
    Here's the first section of the crash report, showing the builds for Interface builder and Mac OS X (10.5.6).
    Process: Interface Builder 8090
    Path: /Developer/Applications/Interface Builder.app/Contents/MacOS/Interface Builder
    Identifier: com.apple.InterfaceBuilder3
    Version: 3.1.2 (677)
    Build Info: InterfaceBuilder-6770000~1
    Code Type: X86 (Native)
    Parent Process: launchd 137
    Date/Time: 2009-01-03 19:29:24.618 -0700
    OS Version: Mac OS X 10.5.6 (9G55)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000011
    Crashed Thread: 0
    Thread 0 Crashed:
    0 com.apple.CoreFoundation 0x910272b4 CFRetain + 36
    1 com.apple.HIToolbox 0x911ff566 TThemeFont::SetCTFont(__CTFont const*) + 62
    2 com.apple.HIToolbox 0x911ff4f4 TThemeSpecifiedFont::Init(THIThemeTextInfo const*) + 32
    3 com.apple.HIToolbox 0x9110ccb3 ThemeFontCreate(THIThemeTextInfo const*) + 239
    4 com.apple.HIToolbox 0x9110cb85 TThemeText::ConstructThemeFontWithFontID(__CFString const*, THIThemeTextInfo const*) + 79
    5 com.apple.HIToolbox 0x9110ca49 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 159
    6 com.apple.HIToolbox 0x9110c781 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 177
    7 com.apple.HIToolbox 0x9110c659 ThemeTextCreate(void const*, THIThemeTextInfo const*) + 33
    8 com.apple.HIToolbox 0x9110c3b5 DataEngine::GetTextDimensions(void const*, float, HIThemeTextInfo*, float*, float*, float*) + 289
    9 com.apple.HIToolbox 0x9110c250 HIThemeGetTextDimensions + 202
    10 com.apple.HIToolbox 0x912abbad HIClockView::CalculateTextDimensions() + 133
    11 com.apple.HIToolbox 0x912abd82 HIClockView::GetOptimalSizeSelf(CGSize*, float*) + 118
    12 com.apple.HIToolbox 0x9114852d HIView::SendGetOptimalBounds(CGRect*, float*) + 151
    13 com.apple.HIToolbox 0x9114846d HIView::GetOptimalSize(CGSize*, float*) + 53
    14 com.apple.HIToolbox 0x9119bd85 GetBestControlRect + 105
    15 ...terfaceBuilder.CarbonPlugin 0x162f127a IBWindowForHostingCarbonControls + 9638
    16 ...terfaceBuilder.CarbonPlugin 0x162f1b1f IBWindowForHostingCarbonControls + 11851
    17 ...terfaceBuilder.CarbonPlugin 0x162f2766 IBWindowForHostingCarbonControls + 14994
    18 ...terfaceBuilder.CarbonPlugin 0x162f37c8 IBWindowForHostingCarbonControls + 19188
    19 ...terfaceBuilder.CarbonPlugin 0x162eb17a 0x162e5000 + 24954
    20 com.apple.InterfaceBuilderKit 0x002c65e0 -IBLibraryObjectTemplate classesOfPasteboardObjects + 194
    21 com.apple.InterfaceBuilderKit 0x002c64b9 -IBLibraryController typeSummaryForObjectTemplate: + 106
    22 com.apple.InterfaceBuilderKit 0x002c5fc4 -IBLibraryController createAssetForTemplate:inNamespace: + 554
    23 com.apple.InterfaceBuilderKit 0x002c4fe3 -IBLibraryController createAssetsFromTemplatesInNibNamed:forPlugin: + 746
    24 com.apple.InterfaceBuilderKit 0x002c499e -IBLibraryController loadLibraryObjectsForPlugin: + 287
    25 com.apple.InterfaceBuilderKit 0x002c414e -IBPlugin didLoad + 480
    26 ...terfaceBuilder.CarbonPlugin 0x162ea66f 0x162e5000 + 22127
    27 com.apple.InterfaceBuilderKit 0x002c389f -IBPluginController loadPluginAtPath:error: + 2809
    28 com.apple.InterfaceBuilder3 0x00002345 0x1000 + 4933
    29 com.apple.AppKit 0x91f983a3 -NSApplication run + 83
    30 com.apple.AppKit 0x91f658a4 NSApplicationMain + 574
    31 com.apple.InterfaceBuilder3 0x00004eca 0x1000 + 16074

    Thanks for asking. It happens when I click the "Interface builder.app" name in finder and when I double-click an .xib file name in finder.
    As I mentioned, I have repaired permissions on the drive to no avail. I have also read older posts on the web referring to various preference plist files but those don't exist with this build of xcode.
    I have also had older builds of xcode on this mbp and worked thru a couple of tutorials. Interface Builder from those older builds worked. I'm not sure were to get them, now, and I doubt they would have the iphone sdk included.

  • Xcode 4.2.1 crashes when using a QCView in Interface Builder

    Hi, I have been trying to use a QCView in one of my projects but I get a crash everytime. I tried loading the QuartzComposerChart sample application but if I compile the project I get a crash, it just seems to crash when it wants to but I was able to get it compiled if I didn't click on the .nib file. It seems to be related to interface builder anyway.
    Adding a QCView to a new project results in a .xib file not being able to be saved I get this error
    The document “MainMenu.xib” could not be autosaved. -[NSConcreteMapTable state]: unrecognized selector sent to instance 0x402d47420
    Heres my crash log:
    UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[NSKeyValueUndefinedSetter state]: unrecognized selector sent to instance 0x4026f43a0
    UserInfo: (null)
    Hints: None
    Backtrace:
      0  0x00007fff8963726a __exceptionPreprocess (in CoreFoundation)
      1  0x00007fff83bb2d5e objc_exception_throw (in libobjc.A.dylib)
      2  0x00007fff896c34ce -[NSObject doesNotRecognizeSelector:] (in CoreFoundation)
      3  0x00007fff89624133 ___forwarding___ (in CoreFoundation)
      4  0x00007fff89623f48 _CF_forwarding_prep_0 (in CoreFoundation)
      5  0x00007fff88c829b2 _PatchToComposition (in QuartzComposer)
      6  0x00007fff88c5bd47 -[QCPatchController encodeWithCoder:] (in QuartzComposer)
      7  0x00007fff8a60559d _encodeObject (in Foundation)
      8  0x00007fff8dc72814 -[NSNibConnector encodeWithCoder:] (in AppKit)
      9  0x00007fff8dc72599 -[NSNibBindingConnector encodeWithCoder:] (in AppKit)
    10  0x00007fff8a60559d _encodeObject (in Foundation)
    11  0x00007fff8a60678e -[NSKeyedArchiver _encodeArrayOfObjects:forKey:] (in Foundation)
    12  0x00007fff8a606e56 -[NSArray(NSArray) encodeWithCoder:] (in Foundation)
    13  0x00007fff8a60559d _encodeObject (in Foundation)
    14  0x00007fff8dbe5ab7 -[NSIBObjectData encodeWithCoder:] (in AppKit)
    15  0x00007fff8a60559d _encodeObject (in Foundation)
    16  0x000000010aaf0938 -[IBCocoaDocument compiledKeyedObjectsData:] (in IDEInterfaceBuilderCocoaIntegration)
    17  0x000000010aaf10e0 -[IBCocoaDocument fileWrapperOfType:error:] (in IDEInterfaceBuilderCocoaIntegration)
    18  0x00007fff8db59801 -[NSDocument writeToURL:ofType:error:] (in AppKit)
    19  0x000000010a681231 -[IBDocument writeToURL:ofType:error:] (in IDEInterfaceBuilderKit)
    20  0x00007fff8db58769 -[NSDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] (in AppKit)
    21  0x000000010a6846ff -[IBDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] (in IDEInterfaceBuilderKit)
    22  0x00007fff8db58b68 -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:forceTemporaryDirectory:error:] (in AppKit)
    23  0x00007fff8db4285d -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:error:] (in AppKit)
    24  0x00007fff8db58911 -[NSDocument writeSafelyToURL:ofType:forSaveOperation:error:] (in AppKit)
    25  0x0000000107ad664a -[IDEEditorDocument writeSafelyToURL:ofType:forSaveOperation:error:] (in IDEKit)
    26  0x00007fff8db61ea7 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_8 (in AppKit)
    27  0x00007fff8db61327 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_14 (in AppKit)
    28  0x00007fff8db61c80 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_7 (in AppKit)
    29  0x00007fff8a7a5a8d -[NSFileCoordinator(NSPrivate) _invokeAccessor:orDont:thenRelinquishAccessClaimForID:] (in Foundation)
    30  0x00007fff8a7a8e65 -[NSFileCoordinator(NSPrivate) _coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] (in Foundation)
    31  0x00007fff8db5725c -[NSDocument _fileCoordinator:coordinateReadingContentsAndWritingItemAtURL:byAccessor:] (in AppKit)
    32  0x00007fff8db45702 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_1 (in AppKit)
    33  0x00007fff8db5ab75 -[NSDocument performAsynchronousFileAccessUsingBlock:] (in AppKit)
    34  0x00007fff8db453af -[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in AppKit)
    35  0x0000000107b8b66b -[IDEEditorDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in IDEKit)
    36  0x000000010a6811fd -[IBDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in IDEInterfaceBuilderKit)
    37  0x00007fff8db46d40 __-[NSDocument autosaveWithImplicitCancellability:completionHandler:]_block_invoke_1 (in AppKit)
    38  0x00007fff8db40898 -[NSDocument continueFileAccessUsingBlock:] (in AppKit)
    39  0x0000000107b898db -[IDEEditorDocument continueFileAccessUsingBlock:] (in IDEKit)
    40  0x00007fff8db40cad __-[NSDocument performAsynchronousFileAccessUsingBlock:]_block_invoke_6 (in AppKit)
    41  0x00007fff8db71333 __-[NSDocumentController(NSInternal) _onMainThreadInvokeWorker:]_block_invoke_3 (in AppKit)
    42  0x00007fff882cc8ba _dispatch_call_block_and_release (in libdispatch.dylib)
    43  0x00007fff882ce72a _dispatch_main_queue_callback_4CF (in libdispatch.dylib)
    44  0x00007fff895cc4dc __CFRunLoopRun (in CoreFoundation)
    45  0x00007fff895cbae6 CFRunLoopRunSpecific (in CoreFoundation)
    46  0x00007fff8c1283d3 RunCurrentEventLoopInMode (in HIToolbox)
    47  0x00007fff8c12f63d ReceiveNextEventCommon (in HIToolbox)
    48  0x00007fff8c12f4ca BlockUntilNextEventMatchingListInMode (in HIToolbox)
    49  0x00007fff8d7a23f1 _DPSNextEvent (in AppKit)
    50  0x00007fff8d7a1cf5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit)
    51  0x00007fff8d79e62d -[NSApplication run] (in AppKit)
    52  0x00007fff8da1d80c NSApplicationMain (in AppKit)
    53  0x0000000107165eec (in Xcode)
    54  0x0000000000000002
    This also happens when I try loading a composition into a QCView. Does anyone know how to fix this?
    Thanks
    Ed

    Glad you posted... I am getting similar messages in xcode 4.2.1
    The document “MainMenu.xib” could not be saved. -[DVTFileSystemVNode state]: unrecognized selector sent to instance 0x40540f920
    I didn't make the connection with QCView until I saw your post. I have several .xib in the project with QCViews and all of them have this same problem.  .xib files without QCViews in them are fine.
    However, my application does not crash, but runs fine. (The xib's and application were written with xcode 3.2, and I can't edit them now in 4.2.1, because I can't save them.  )
    Any other clues would be welcome.
    Thanks
    Keith

  • [HELP] * The application Interface Builder quit unexpectedly

    Process: Interface Builder [533]
    Path: /Developer/Applications/Interface Builder.app/Contents/MacOS/Interface Builder
    Identifier: com.apple.InterfaceBuilder3
    Version: 3.1.2 (677)
    Build Info: InterfaceBuilder-6770000~1
    Code Type: X86 (Native)
    Parent Process: launchd [113]
    Date/Time: 2009-05-03 08:36:21.061 -0700
    OS Version: Mac OS X 10.5.6 (9G55)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000008
    Crashed Thread: 0
    Thread 0 Crashed:
    0 ??? 0x1f420636 0 + 524420662
    1 ??? 0x1f3e5a18 0 + 524179992
    2 ??? 0x1f3e70fe 0 + 524185854
    3 ??? 0x1f3c2276 0 + 524034678
    4 ??? 0x1f20d05d 0 + 522244189
    5 ??? 0x05325948 0 + 87185736
    6 ??? 0x0532523e 0 + 87183934
    7 ??? 0x00caece7 0 + 13298919
    8 ??? 0x05e85023 0 + 99110947
    9 ??? 0x05e84135 0 + 99107125
    10 ??? 0x05e50997 0 + 98896279
    11 ??? 0x05e51aaa 0 + 98900650
    12 ??? 0x017ea580 0 + 25077120
    13 ??? 0x017ec00d 0 + 25083917
    14 ??? 0x017ec489 0 + 25085065
    15 ??? 0x017ea580 0 + 25077120
    16 ??? 0x017e9ef5 0 + 25075445
    17 ??? 0x00aa4ef1 0 + 11161329
    18 ??? 0x00aa63a4 0 + 11166628
    19 ??? 0x017ea580 0 + 25077120
    20 ??? 0x017e9ef5 0 + 25075445
    21 ??? 0x00aa6080 0 + 11165824
    22 ??? 0x00aa4e16 0 + 11161110
    23 ??? 0x002660e4 0 + 2515172
    24 ??? 0x017ea580 0 + 25077120
    25 ??? 0x017e9ef5 0 + 25075445
    26 ??? 0x00a9f1ba 0 + 11137466
    27 ??? 0x00aa3cbb 0 + 11156667
    28 ??? 0x017ea580 0 + 25077120
    29 ??? 0x017ec00d 0 + 25083917
    30 ??? 0x017ec489 0 + 25085065
    31 ??? 0x017ea580 0 + 25077120
    32 ??? 0x017e9ef5 0 + 25075445
    33 ??? 0x00a9e042 0 + 11132994
    34 ??? 0x017ea580 0 + 25077120
    35 ??? 0x017e9ef5 0 + 25075445
    36 ??? 0x00a9d61d 0 + 11130397
    37 ??? 0x00a9cfe8 0 + 11128808
    38 ??? 0x00c84455 0 + 13124693
    39 ??? 0x0035345c 0 + 3486812
    40 ??? 0x00265d58 0 + 2514264
    41 ??? 0x0026599e 0 + 2513310
    42 ??? 0x0026514e 0 + 2511182
    43 ??? 0x0026489f 0 + 2508959
    44 ??? 0x0026b5e3 0 + 2536931
    45 ??? 0x0026b519 0 + 2536729
    46 ??? 0x000023db 0 + 9179
    47 ??? 0x00acf3a3 0 + 11334563
    48 ??? 0x00a9c8a4 0 + 11126948
    49 ??? 0x00004eca 0 + 20170
    Thread 1:
    0 ??? 0x005241c6 0 + 5390790
    1 ??? 0x0052b9bc 0 + 5421500
    2 ??? 0x008de0ae 0 + 9298094
    3 ??? 0x008decd8 0 + 9301208
    4 ??? 0x030a05dc 0 + 50988508
    5 ??? 0x030a0464 0 + 50988132
    6 ??? 0x00555095 0 + 5591189
    7 ??? 0x00554f52 0 + 5590866
    Thread 2:
    0 ??? 0x00524226 0 + 5390886
    1 ??? 0x005561ef 0 + 5595631
    2 ??? 0x00557a73 0 + 5601907
    3 ??? 0x0182575c 0 + 25319260
    4 ??? 0x01825570 0 + 25318768
    5 ??? 0x018254d5 0 + 25318613
    6 ??? 0x1c4e21a2 0 + 474882466
    7 ??? 0x1c4e1959 0 + 474880345
    8 ??? 0x017df7ed 0 + 25032685
    9 ??? 0x017df394 0 + 25031572
    10 ??? 0x00555095 0 + 5591189
    11 ??? 0x00554f52 0 + 5590866
    Thread 3:
    0 ??? 0x00554906 0 + 5589254
    1 ??? 0x00555095 0 + 5591189
    2 ??? 0x00554f52 0 + 5590866
    Thread 4:
    0 ??? 0x005241c6 0 + 5390790
    1 ??? 0x0052b9bc 0 + 5421500
    2 ??? 0x008de0ae 0 + 9298094
    3 ??? 0x008decd8 0 + 9301208
    4 ??? 0x041a3052 0 + 68825170
    5 ??? 0x00555095 0 + 5591189
    6 ??? 0x00554f52 0 + 5590866
    Thread 5:
    0 ??? 0x005241c6 0 + 5390790
    1 ??? 0x0052b9bc 0 + 5421500
    2 ??? 0x008de0ae 0 + 9298094
    3 ??? 0x008ded34 0 + 9301300
    4 ??? 0x027d14c6 0 + 41751750
    5 ??? 0x017df7ed 0 + 25032685
    6 ??? 0x017df394 0 + 25031572
    7 ??? 0x00555095 0 + 5591189
    8 ??? 0x00554f52 0 + 5590866
    Thread 6:
    0 ??? 0x0052b3ae 0 + 5419950
    1 ??? 0x00555d0d 0 + 5594381
    2 ??? 0x0545bb32 0 + 88455986
    3 ??? 0x00555095 0 + 5591189
    4 ??? 0x00554f52 0 + 5590866
    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x00000000 ebx: 0x1f3e5a04 ecx: 0x00000012 edx: 0x00000000
    edi: 0xbfffd67c esi: 0x070f6be0 ebp: 0xbfffd578 esp: 0xbfffd578
    ss: 0x0000001f efl: 0x00010202 eip: 0x1f420636 cs: 0x00000017
    ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
    cr2: 0x00000008
    Binary Images:
    0x8fe00000 - 0x8fe298a3 dyld 0.0 (???) <d1092af4e89e77aa121dd5fb0c855cd9> /usr/lib/dyld
    console:
    5/3/09 8:36:25 AM [0x0-0x11011].com.apple.Xcode[206] Xcode(206,0xb0103000) malloc: free_garbage: garbage ptr = 0xa19e220, has non-zero refcount = 1
    5/3/09 8:37:36 AM [0x0-0x11011].com.apple.Xcode[206] Xcode(206,0xb0103000) malloc: free_garbage: garbage ptr = 0x9768920, has non-zero refcount = 1
    5/3/09 8:37:36 AM [0x0-0x11011].com.apple.Xcode[206] Xcode(206,0xb0103000) malloc: free_garbage: garbage ptr = 0x97e8790, has non-zero refcount = 1
    5/3/09 8:37:37 AM [0x0-0x65065].com.apple.InterfaceBuilder3[551] Couldn't open shared capabilities memory GSCapabilities (No such file or directory)
    5/3/09 8:37:38 AM com.apple.launchd[113] ([0x0-0x65065].com.apple.InterfaceBuilder3[551]) Exited abnormally: Bus error
    I try to fix it by http://discussions.apple.com/thread.jspa?threadID=1850735&tstart=0

    zoujinhe wrote:
    thanks.
    let me try this(Mac OS in home, I at office now).
    but CHESS had same problem, is my system problem?
    Ni Hao
    Take note of the permissions repairs and if those are extensive, it may indicate a general health issue. Repairing permissions should help if there are many files in need of repair. Try the repairs first - step-by-step.
    Be sure that your OS install is 'normal', meaning do not move and/or rename basic folders/directories created when the OS is first installed.
    Shouldn't you be on holiday?

  • The application Interface Builder quit unexpectedly

    Just installed the iPhone SDK and installed sample code. The Interface Builder will not start. At startup, the following message is displayed: "The application Interface Builder quit unexpectedly." I've tried the standard Xcode SDK and the interface builder has the same problem. I've repaired permissions on the disk, to no avail. I'm stumped on this.
    Here's the first section of the crash report, showing the builds for Interface builder and Mac OS (10.5.6).
    Process: Interface Builder [8090]
    Path: /Developer/Applications/Interface Builder.app/Contents/MacOS/Interface Builder
    Identifier: com.apple.InterfaceBuilder3
    Version: 3.1.2 (677)
    Build Info: InterfaceBuilder-6770000~1
    Code Type: X86 (Native)
    Parent Process: launchd [137]
    Date/Time: 2009-01-03 19:29:24.618 -0700
    OS Version: Mac OS X 10.5.6 (9G55)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000011
    Crashed Thread: 0
    Thread 0 Crashed:
    0 com.apple.CoreFoundation 0x910272b4 CFRetain + 36
    1 com.apple.HIToolbox 0x911ff566 TThemeFont::SetCTFont(__CTFont const*) + 62
    2 com.apple.HIToolbox 0x911ff4f4 TThemeSpecifiedFont::Init(THIThemeTextInfo const*) + 32
    3 com.apple.HIToolbox 0x9110ccb3 ThemeFontCreate(THIThemeTextInfo const*) + 239
    4 com.apple.HIToolbox 0x9110cb85 TThemeText::ConstructThemeFontWithFontID(__CFString const*, THIThemeTextInfo const*) + 79
    5 com.apple.HIToolbox 0x9110ca49 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 159
    6 com.apple.HIToolbox 0x9110c781 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 177
    7 com.apple.HIToolbox 0x9110c659 ThemeTextCreate(void const*, THIThemeTextInfo const*) + 33
    8 com.apple.HIToolbox 0x9110c3b5 DataEngine::GetTextDimensions(void const*, float, HIThemeTextInfo*, float*, float*, float*) + 289
    9 com.apple.HIToolbox 0x9110c250 HIThemeGetTextDimensions + 202
    10 com.apple.HIToolbox 0x912abbad HIClockView::CalculateTextDimensions() + 133
    11 com.apple.HIToolbox 0x912abd82 HIClockView::GetOptimalSizeSelf(CGSize*, float*) + 118
    12 com.apple.HIToolbox 0x9114852d HIView::SendGetOptimalBounds(CGRect*, float*) + 151
    13 com.apple.HIToolbox 0x9114846d HIView::GetOptimalSize(CGSize*, float*) + 53
    14 com.apple.HIToolbox 0x9119bd85 GetBestControlRect + 105
    15 ...terfaceBuilder.CarbonPlugin 0x162f127a IBWindowForHostingCarbonControls + 9638
    16 ...terfaceBuilder.CarbonPlugin 0x162f1b1f IBWindowForHostingCarbonControls + 11851
    17 ...terfaceBuilder.CarbonPlugin 0x162f2766 IBWindowForHostingCarbonControls + 14994
    18 ...terfaceBuilder.CarbonPlugin 0x162f37c8 IBWindowForHostingCarbonControls + 19188
    19 ...terfaceBuilder.CarbonPlugin 0x162eb17a 0x162e5000 + 24954
    20 com.apple.InterfaceBuilderKit 0x002c65e0 -[IBLibraryObjectTemplate classesOfPasteboardObjects] + 194
    21 com.apple.InterfaceBuilderKit 0x002c64b9 -[IBLibraryController typeSummaryForObjectTemplate:] + 106
    22 com.apple.InterfaceBuilderKit 0x002c5fc4 -[IBLibraryController createAssetForTemplate:inNamespace:] + 554
    23 com.apple.InterfaceBuilderKit 0x002c4fe3 -[IBLibraryController createAssetsFromTemplatesInNibNamed:forPlugin:] + 746
    24 com.apple.InterfaceBuilderKit 0x002c499e -[IBLibraryController loadLibraryObjectsForPlugin:] + 287
    25 com.apple.InterfaceBuilderKit 0x002c414e -[IBPlugin didLoad] + 480
    26 ...terfaceBuilder.CarbonPlugin 0x162ea66f 0x162e5000 + 22127
    27 com.apple.InterfaceBuilderKit 0x002c389f -[IBPluginController loadPluginAtPath:error:] + 2809
    28 com.apple.InterfaceBuilder3 0x00002345 0x1000 + 4933
    29 com.apple.AppKit 0x91f983a3 -[NSApplication run] + 83
    30 com.apple.AppKit 0x91f658a4 NSApplicationMain + 574
    31 com.apple.InterfaceBuilder3 0x00004eca 0x1000 + 16074

    I had customized the date & time formats in the International settings. Once I set those back to the default formats, Interface Builder runs just fine.

Maybe you are looking for