Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Help

Home

Home » Archived » Test and Performance Tools Platform (TPTP) » When AGR resolvers are not used....

Show: Today's Messages :: Show Polls :: Message Navigator

When AGR resolvers are not used.... [message #106750]

Thu, 26 July 2007 19:13

Eclipse User

Originally posted by: joel_patterson.verizon.net

I was experimenting with resolvers and removed the entry from plugin.xml
for the NonTrivialWidgetResolver. I expected everything to be forced
through the AdaptiveResolver (or just not work) but when working with a
Tree I saw:

<command descriptive="NORMAL (289)" type="item-select"
contextId="view/com.agitar.eclipse.outcomes.views.OutcomesView "
widgetId="org.eclipse.swt.widgets.Tree#1">
<item path="com.agitar.result.outcome.r0|0||0|"/>
</command>

Since a resolver wasn't used here, how did this value get created -- and
if I wanted to use something like this for a Tree instead of the
NonTrivialWidgetResolver, what would I call? Obviously the method to
get this value exists somewhere...

Report message to a moderator

Re: When AGR resolvers are not used.... [message #106765 is a reply to message #106750]

Thu, 26 July 2007 20:30

Liz Dancy

Messages: 77
Registered: July 2009

Member

Hi Joel,

The widgetId in this case comes from the 'defaultControlId' which is
computed when the widgetId returned from the widget resolvers is null.

The item path comes from the 'defaultItemAttributes', computed when the
widget is not found with a resolver.

If you want to use these methods in a custom widget resolver, the method
findTreeItemInx can be found in the AbstractStructuredCommand class and the
computeDefaultControlId method is found in the MacroUtil class.

I hope this helps.

Sincerely,

Liz Dancy

"Joel Patterson" <joel_patterson@verizon.net> wrote in message
news:f8aros$1cg$1@build.eclipse.org...
>I was experimenting with resolvers and removed the entry from plugin.xml
>for the NonTrivialWidgetResolver. I expected everything to be forced
>through the AdaptiveResolver (or just not work) but when working with a
>Tree I saw:
>
> <command descriptive="NORMAL (289)" type="item-select"
> contextId="view/com.agitar.eclipse.outcomes.views.OutcomesView "
> widgetId="org.eclipse.swt.widgets.Tree#1">
> <item path="com.agitar.result.outcome.r0|0||0|"/>
> </command>
>
> Since a resolver wasn't used here, how did this value get created -- and
> if I wanted to use something like this for a Tree instead of the
> NonTrivialWidgetResolver, what would I call? Obviously the method to get
> this value exists somewhere...

Report message to a moderator

Previous Topic:	AGR suites in JUnit
Next Topic:	TPTP profiler using SSH tunnel

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 05:30:33 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter