I solved it. My workbench window was a copy of QmitkExtAppWorkbenchWindow, with a few modifications. I do not know what the problem was, but now I took the current version of QmitkExtAppWorkbenchWindow, reintroduced my changes and it works.
A few month ago I added an analogue class to the project template, that you merged to the upstream. If it has not been updated since then, I am afraid that it will crash on Mac. Best, Miklos On Fri, Dec 9, 2011 at 3:29 PM, Miklos Espak <[email protected]> wrote: > Hi, > > I had a look at the problem again. For me, it seems to be a bug in BlueBerry. > > I have a custom application that starts a custom WorkbenchWindowAdvisor: > > int KMapsApplication::Start() > { > berry::Display* display = berry::PlatformUI::CreateDisplay(); > > // int code = berry::PlatformUI::CreateAndRunWorkbench(display, new > QmitkExtAppWorkbenchAdvisor()); > int code = berry::PlatformUI::CreateAndRunWorkbench(display, new > KMapsWorkbenchAdvisor()); > > // exit the application with an appropriate return code > return code == berry::PlatformUI::RETURN_RESTART > ? EXIT_RESTART : EXIT_OK; > } > > If I switch back to the QmitkExtAppWorkbenchAdvisor then for the first > try the application crashes with the same error then above, but for > the second try (and later on) it starts. This happens also on Windows. > > If the application has once started, I can switch back to my custom > WorkbenchAdvisor, rebuild the app, and it starts also with that. > > However, if I start the app with the -BlueBerry.clean option, it crashes > again. > > Another question: > Is it intentional that the plugins' icon does not appear on the > toolbar on Mac? They are available from the Window menu. > > Thanks as always, > Miklos > > On Fri, Nov 11, 2011 at 8:53 PM, Miklos Espak <[email protected]> wrote: >> I generated a project with a view and it also starts. So the bug must >> be in my app, indeed. >> >> On Fri, Nov 11, 2011 at 7:55 PM, Miklos Espak <[email protected]> wrote: >>> On Fri, Nov 11, 2011 at 6:34 PM, Sascha Zelzer >>> <[email protected]> wrote: >>>> I guess it has something to do with smart-pointer misuse in your code. If >>>> you try (directly or indirectly) to delete a berry::Object instance which >>>> has referencing smart pointers, you will get this kind of problem. This is >>>> usually triggered by class members or locals of type berry::Object (or >>>> subclasses) instead of berry::Object::Pointer. ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
