Hi,
in any plug-in, you could register a BlueBerry Part Listener, which gets
notified of part state changes (Views/Editors being
activated/deactivated/shown/hidden/etc.). So you could get either the
active stdmultiwidget, if there is one, and/or register a part listener.
Best,
Sascha
On 09/09/2011 10:15 AM, Clarkson, Matt wrote:
> Thanks Miklos, and everyone else who replied.
>
> I think that replacing it would work best, because as you say, the code to
> enable/disable it has to be in a plugin to get the active page, and active
> editor. THen, if your plugin is not Activated by the default perspective,
> the first editor to show, which may be the QStdMultiWidget one will have the
> default logo.
>
> So, putting a different logo should be easier than disabling it.
>
> Thanks
>
> Matt
>
>
>
>
> On 9 Sep 2011, at 08:12, Miklos Espak wrote:
>
>> Did this help for you, Matt?
>>
>> This code has to be put in a plugin as well, but into which? I tried
>> to add a code like this to the workbench initialization, but it
>> crashed when I referred to the active editor. (Since no editor was
>> active that time.)
>>
>> Actually, I would prefer to replace the logo, not to disable it. I
>> found that there is a preference called "DepartmentLogo". This can
>> work for you if you specify an empty transparent image. I use the
>> following code to set it:
>>
>> berry::IPreferencesService::Pointer prefService =
>> berry::Platform::GetServiceRegistry()
>>
>> .GetServiceById<berry::IPreferencesService>(berry::IPreferencesService::ID);
>>
>> Poco::Path logoPath(berry::Platform::GetInstancePath(), "logo.png");
>> berry::IPreferences::Pointer logoPref =
>> prefService->GetSystemPreferences()->Node("DepartmentLogo");
>> logoPref->Put("DepartmentLogo", logoPath.toString().c_str());
>>
>> The logo must be in the same directory where the executable is. I
>> added a few lines to the CMake files to copy the file to the right
>> places.
>>
>> Best,
>> Miklos
>
>
> ------------------------------------------------------------------------------
> Why Cloud-Based Security and Archiving Make Sense
> Osterman Research conducted this study that outlines how and why cloud
> computing security and archiving is rapidly being adopted across the IT
> space for its ease of implementation, lower cost, and increased
> reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
> _______________________________________________
> mitk-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
computing security and archiving is rapidly being adopted across the IT
space for its ease of implementation, lower cost, and increased
reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
