Hello Matteo,

are you using the ProtocolBrowser class that comes default with Pharo 5? (In 
the Spec-Examples package). This is different from what is in the booklet, the 
code in Pharo 5 is not up to date. For now, you should define a new protocol 
browser class (MyProtocolBrowser for example) and the other classes that are in 
that section. Sorry for that...

--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please 
see http://emailcharter.org <http://emailcharter.org/> .

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
Chile

> On Sep 7, 2016, at 18:57, Matteo via Pharo-users 
> <pharo-users@lists.pharo.org> wrote:
> 
> 
> From: Matteo <matte...@yahoo.it>
> Subject: SpecBooklet: Strange behavior of ProtocolBrowser
> Date: September 7, 2016 at 18:56:08 GMT-3
> To: pharo-users@lists.pharo.org
> 
> 
> Hi,
> I'm playing with the ProtocolBrowser class, as coded in the
> "SpecBooklet.pdf" document (release of the 3rd August 2016).
> I'm using Pharo 5.
> 
> I'm experiencing a strange behavior of the  ProtocolBrowser instance:
>       -if I open a ProtocolBrowser instance, and I click on a "api"   item, I
> do not get any code in the text pane.
>       -If I open another ProtocolBrowser instance then I do not see any code,
> even in the "api" protocol than the "api-events" one.
>       -If I open a further instance then the widget works correctly, showing
> the "api" or "api-events" code in the text pane.
> 
> Please note that the ProtocolBrowser is instantiated as follow:
>       (ProtocolBrowser    new)  openWithSpec
> 
> Could my Pharo image be faulty?
> Is there some problem with ProtocolBrowser>>initializePresenter?
> 
> Thanks,
> Matteo Bellotto
> 
> 
> 
> 
> 

Reply via email to