Hi,

Thanks you both for your answers. I was still not be able to change
the logo. I discovered that most of the GUI creation is handled in the
org.mitk.gui.qt.ext plugin and not in org.mitk.gui.qt.extapplication.
To help me understand, I tried to change the logo of the MITK
workbench directly from the MITK source code but without luck. Can you
point me out to where I should place the code of my previous message
to modify the logo of the plain MITK workbench and most importantly,
why there? i'm having difficulties understanding the workbench
architecture (org.mitk.qt.ext.plugin VS
org.mitk.gui.qt.extapplication, etc).

Thanks,
-F

On Fri, Sep 21, 2012 at 6:07 PM, Miklos Espak <[email protected]> wrote:
> In the main() function you will find stg like this:
>
>   extConfig->setString(berry::Platform::ARG_PLUGIN_DIRS, pluginDirs);
>   std::cout << "ARG_PROVISIONING " << provFile.toString() << std::endl;
>   extConfig->setString(berry::Platform::ARG_PROVISIONING,
> provFile.toString());
> //  extConfig->setString(berry::Platform::ARG_APPLICATION,
> "org.mitk.qt.extapplication");
>   extConfig->setString(berry::Platform::ARG_APPLICATION,
> "it.unito.cim.kmaps");
>
>   // Preload the org.mitk.gui.qt.ext plug-in (and hence also QmitkExt) to
> speed
>   // up a clean-cache start. This also works around bugs in older gcc and
> glibc implementations,
>   // which have difficulties with multiple dynamic opening and closing of
> shared libraries with
>   // many global static initializers. It also helps if dependent libraries
> have weird static
>   // initialization methods and/or missing de-initialization code.
> //  extConfig->setString(berry::Platform::ARG_PRELOAD_LIBRARY,
> "liborg_mitk_gui_qt_ext");
>   extConfig->setString(berry::Platform::ARG_PRELOAD_LIBRARY,
> "libit_unito_cim_kmaps");
>
>
> Like in this example, you have to replace the extapp plugin with your one.
>
> Also, the directory where the main() is contains a 'target_libraries.cmake'
> file. You must add the plugin that contains your custom application to it.
>
> Here it looks like this:
>
> set(target_libraries
>   # Enable plug-ins from this project
>   it_unito_cim_kmaps
>
>   # Require external plug-ins
>   org_blueberry_compat
>   org_blueberry_ui_qt
>   org_blueberry_ui_qt_help
>   org_mitk_gui_qt_extapplication
>   org_mitk_gui_qt_datamanager
> )
>
>
>
>
> On Fri, Sep 21, 2012 at 10:56 PM, Miklos Espak <[email protected]> wrote:
>>
>> The code is correct, that worked for me a half year ago. (I have not tried
>> since then.)
>>
>> My suspicion is that the app is started with another workbench window
>> advisor, not the one you had modified. It's easy to check by printing out a
>> line.
>>
>> Also, there was an e-mail recently on this list, that the ExtApp had been
>> renamed to something else. This might be related.
>>
>> Regards,
>> Miklos
>
>



-- 
--
Félix C. Morency, M.Sc.
Plateforme d’analyse et de visualisation d’images
Centre Hospitalier Universitaire de Sherbrooke
Centre de recherche clinique Étienne-Le Bel
Local Z5-3031 | 819.346.1110 ext 16634

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to