|Re: [AGR] focus command generation [message #70139 is a reply to message #68635]
||Tue, 09 May 2006 14:47
| No real name
Registered: July 2009
You're right, the composite is the high level composite that contains the|
In the majority of cases, you actually don't need a focus command and I have
put in some code to try to avoid producing unneeded focus commands. Some
test cases, of course are dependent on a container to first be given focused
(e.g. giving the console view focus before using position based recording to
send user input). The majority of focus commands are generated when
explicitly a view/editor is given focus or an item is selected while the
view/editor is unfocused.
"Barbara Rosi-Schwartz" <Barbara.Rosi-Schwartz@Etish.org> wrote in message
> Barbara Rosi-Schwartz wrote:
> > Hello everybody.
> > I am wondering under what circumstances the focus command is generated
> > in a test macro. I always see it following an item-select command, but
> > not all item-select commands are followed by a focus one. Typically the
> > widgetId associated with the focus command is a Composite. Is this the
> > Composite underlying the widget (tree, list, etc.) in which the
> > selection is made?
> > TIA
> > B.
> After a little playing around, I concluded that the Composite in the
> focus command is the highest level composite, f.i. in a View, it is the
> Composite that is passed into the view's createPartControl() method.
> Is this accurate?
> I still have the question about the circumstances under which the focus
> command is generated though...
Powered by FUDForum
. Page generated in 0.01630 seconds