URL:
  <http://savannah.gnu.org/bugs/?26414>

                 Summary: GNUstep can't deal with a missing services menu
                 Project: GNUstep
            Submitted by: hitterm
            Submitted on: Fr 01 Mai 2009 20:37:49 GMT
                Category: Base/Foundation
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

This is Windows XP in a virtual machine with GNUstep installed from the
current set of installers:

- gnustep-system-0.22.0
- gnustep-core-0.22.0
- gnustep-devel-1.0.0
- SystemPreferences-1.0.2.7
- gorm-1.2.8
- ProjectCenter-0.5.0

As I plan to make a standalone application running without further GNUstep
environment I use a main menu without a "Services" entry. Actually, it's a
menu created in InterfaceBuilder on Mac OS X, converted to a Gorm.

When running this app via "openapp ..." GNUstep complains over and over
again:

"... ... Services menu not in main menu!"

At the same time my application shows an alert window "critical error in
<name of the app>". The field for the text of the  error is empty, but there's
a scrollbar. I can't test wether both misbehaviours are related as I can't add
the services menu (see https://savannah.gnu.org/bugs/index.php?26413 ).

Anyways, clicking either "debug" or "abort" or anywhere else in the error
popup results in a crash: Windows complains with a generic "Visual C++ Runtime
Library, Runtime error! <path of the app's .exe>"




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26414>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

Reply via email to