|QuickAccess contribution and activities [message #911757]
||Wed, 12 September 2012 09:01
| Daniel KrÃ¼gler
Registered: July 2009
Presumably bug entry|
belongs to the most annoying things when you try to migrate to e4 from
an existing 3.x RCP application.
The bug entry also suggests a code pattern to get rid of the search
field but I would prefer an approach that does not depend on explicit e4
dependencies, because during migration I would like to easily switch
between a 3.x and a 4.x Eclipse runtime for easier testing the runtime
differences. I thought that activities could be a solution for this.
Now, usually, activities provide a good means to filter away unwanted
contributions. The usual idiom is to invent a special "exclusion
activity", lets do this via
and to list unwanted contributions like so:
I was trying to find a way to express a pattern that catches the quick
access search field "contribution" and after some code search I tried it
but that won't help alone because this only would deactivate the handler
that is performed for the quick search (as I understand it) and it also
seems not be considered by activity filtering (because I can still
activate the handler).
I also tried this one:
and this had unexpectedly very fundamental effects, in fact I get an
application state that does not have the search field but all views are
empty as well, there are no contributions, menus, just an empty window.
I wonder why this effect is so extreme and whether there exists a better
activity filter to realize the wanted effect.
Thanks for any help & greetings from Bremen,
Powered by FUDForum
. Page generated in 0.01885 seconds