On Sun, Mar 30, 2014 at 10:14 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
> What I am trying to achieve is a way to test the number of menu items on the element in the example above and to trigger the action blocks for each menu item to test its behaviour. Something like:
>
> self assert: element menuItems size equals:2.
> element menuItems do: [:each | self shouldnt: (each actionBlock value: element) raise: Error ]
>
> It'll be helpful because I'm trying to adapt my tests to Roassal 2.

Ah okay. In that case, I guess you should directly talk to the announcer. For example:
        self assert: element announcer numberOfSubscriptions equals: 2.

Yes. That was easy to find.
 

I haven’t checked, but I guess you can easily access to the callback.

The access to the callback is not evident because the element does not know about its callbacks; the callbacks are only known by the announcer and announcer provides very limited API to its internal information. Hence my question: how should I gain access to the callbacks of an element to trigger them and test that they do not raise errors.

tx.
usman

 
Let me know how it goes.

Alexandre


>
> tx.
>
>
> Thanks Juraj for having introduced the class RTMenuActivable!
>
> Cheers,
> Alexandre
>
>
> On Mar 29, 2014, at 6:05 PM, Usman Bhatti <usman.bhatti@gmail.com> wrote:
>
> > Hi Alex,
> >
> > How do you trigger the menu action of an RTElement programmatically?
> >
> > In Roassal one, I could do:
> >
> > menuActivable := (anElement getInteraction: ROMenuActivable).
> > actionBlock := (menuActivable actionNamed: 'my action').
> > actionBlock value value: anElement.
> >
> >
> > In Roassal 2, I cannot get the menu actions because everything is happening with announcements. How can I trigger the RTMenuActivable for my elements in the view because when generating my events programmatically by simulating mouse-clicks, my image becomes non-responsive after a few tries.
> >
> > tx,
> >
> > usman
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev@iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev@iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev@iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev