Help! Two Help Menus? (X-Code Project)

Discussion in 'Mac Programming' started by Cybernanga, Jun 20, 2005.

  1. Cybernanga macrumors regular

    Joined:
    Oct 27, 2004
    Location:
    Essex, United Kingdom
    #1
    I have a app developed in AppleScript Studio (X-Code 2.0), This is the first time I've compiled it since upgrading to Tiger (Erase and Install).

    For some bizzarre reason, my app now has 2 help menu's.

    I had read about an issue with QT 7 having 2 help menu's but I've never experienced it myself.

    Does anyone have any idea what may be causing this, and how I can get rid of it? I have checked the nib in Interface Builder, and that only has the one help menu.
     
  2. chameeeleon macrumors 6502

    Joined:
    Jan 11, 2004
    #2
    Yeah, it's caused by the DivX component in your Quicktime library folder. Delete it and all is well.
    A lot of OS X Tiger problems are the result of that component, I've found (minimizing Quicktime movies causing freezing being another one).
     
  3. Cybernanga thread starter macrumors regular

    Joined:
    Oct 27, 2004
    Location:
    Essex, United Kingdom
    #3
    I removed the DivX component, restarted, and recompiled my Application, but alas, it still has 2 Help Menu's.

    On further checking, it seem's like everything I build with X-Code 2.0 seems to suffer from this problem.

    I'm not using any quicktime related stuff in my app's so I'm not sure why the DivX component would have been the issue. Quicktime itself opens fine with one help Menu, and I've never had it freeze on me.

    Could it be anything else that's causeing the 2help menu issue in my Application?
     
  4. chameeeleon macrumors 6502

    Joined:
    Jan 11, 2004
    #4
    Sorry, I'm out of ideas. I just remember I had two help menus in Quicktime, Pages and Keynote, and whenever I minimized movies in Quicktime I wouldn't be able to unminimize them, and the DivX component's removal solved all of these (and they've since put a thing on their site saying it isn't Tiger compatible).
    I guess the culprit behind the two in XCode is something else though...
     

Share This Page