Hi, this is not a static but a superclass call. berry::InternalPlatform overrides Poco::Util::Application::defineOptions(...), which is called by the at some point in time durine Poco::Util::Application "start-up".
There is the notion of "extended arguments" (berry::Platform::ARG_XARGS) which can be used to add arbitrary command line options to BlueBerry applications. They can be retrieved by calling berry::Platform::GetExtendedApplicationArgs(). However, for proper argument handling (validation, help output, etc.), we do not have an API yet. For that, we could maybe add a Poco::Util::OptionSet argument to the berry::Starter::Run() method, which gets later merged into the existing BlueBerry option set. This doesn't look too complicated. Defining new options from within plug-ins is a completely different issue (which we discussed but which would need more work) - just as a note. If you are interested in one of these approaches, please file a feature request! Best, Sascha On 07/31/2014 04:29 PM, Miklos Espak wrote: > Hi, > > It seems that I will need to introduce new command line options for > our application. I see that berry::InternalPlatform defines some > options using this call: > > Poco::Util::Application::defineOptions(options); > > Since this is a static call, I assume that I could define new options > in the similar way from our application. (From the main() function.) > However, I do not see any example for that. > > Has anybody tried this? > > Cheers, > Miklos > ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
