- Pharo-users - lists.pharo.org

Re: [Pharo-users] Problem with Spec icon

by Tommaso Dal Sasso

On 14/12/14 21:44, stepharo wrote: > I got the same problem when I put an Halt pressing on any button leads > to the opening of the same UI. > I wonder if there is not an interaction between spec and the UI modal > opening. > I read the code of ImageModel and I did not find anything special. > Yes, I thought as well that could be something regarding modal UI, but I have so little knowledge of Spec and the way it interacts with Morphic that I could not tell more. OK, it works correctly if I put the dialog code inside a block and i fork it, so probably the modal window blocks the way the action of the icon is triggered. I'll try to investigate more. Thanks for the feedback, Tommaso > Stef. > Le 14/12/14 20:26, Tommaso Dal Sasso a Ã©crit : >> I have a weird behavior building an interface with Spec. >> >> I have a window built with Spec, and I want to add a button that >> shows a dialog with some text. >> To display the dialog I use the following line: >> >> UIManager default longMessage: 'a text message' title: 'some title'. >> >> And I hooked this code to a widget through the #action: method. >> The problem is: If I use a ButtonModel, the code behaves correctly >> showing the dialog. >> If I use an instance of the class ImageModel to display an icon, the >> dialog is displayed but the interface "hangs", in the sense that the >> "ok" button won't close the dialog and every click would spawn a new >> dialog. >> >> I would like to use an icon because it integrates better with the >> interface. >> Do you know if it is a bug or if I am doing something wrong? >> >> Thanks, >> Tommaso >> >> >> P.s.: Steps to reproduce >> >> If you need a working example you can inspect the code on the >> bleeding edge version of ShoreLine Reporter by following these >> instructions: >> 1. download a recent Pharo 4 image; >> 2. open a workspace and run: ConfigurationOfShoreLineReporter >> loadBleedingEdge >> 3. trigger an exception (for example by running 3/0 in a workspace). >> 4. click 'Report' >> 5. click the '?' button on the right side of the window. >> >> >> > >

Dec. 14, 2014

Re: [Pharo-users] Problem with Spec icon

by stepharo

I got the same problem when I put an Halt pressing on any button leads to the opening of the same UI. I wonder if there is not an interaction between spec and the UI modal opening. I read the code of ImageModel and I did not find anything special. Stef. Le 14/12/14 20:26, Tommaso Dal Sasso a Ã©crit : > I have a weird behavior building an interface with Spec. > > I have a window built with Spec, and I want to add a button that shows > a dialog with some text. > To display the dialog I use the following line: > > UIManager default longMessage: 'a text message' title: 'some title'. > > And I hooked this code to a widget through the #action: method. > The problem is: If I use a ButtonModel, the code behaves correctly > showing the dialog. > If I use an instance of the class ImageModel to display an icon, the > dialog is displayed but the interface "hangs", in the sense that the > "ok" button won't close the dialog and every click would spawn a new > dialog. > > I would like to use an icon because it integrates better with the > interface. > Do you know if it is a bug or if I am doing something wrong? > > Thanks, > Tommaso > > > P.s.: Steps to reproduce > > If you need a working example you can inspect the code on the bleeding > edge version of ShoreLine Reporter by following these instructions: > 1. download a recent Pharo 4 image; > 2. open a workspace and run: ConfigurationOfShoreLineReporter > loadBleedingEdge > 3. trigger an exception (for example by running 3/0 in a workspace). > 4. click 'Report' > 5. click the '?' button on the right side of the window. > > >

Dec. 14, 2014

Re: [Pharo-users] Problem with Spec icon

by stepharo

I tried to reproduce the problem by invoking directly the longMessage: with a really long text but it did not work. I will try to find where you invoke the code. Le 14/12/14 20:26, Tommaso Dal Sasso a Ã©crit : > I have a weird behavior building an interface with Spec. > > I have a window built with Spec, and I want to add a button that shows > a dialog with some text. > To display the dialog I use the following line: > > UIManager default longMessage: 'a text message' title: 'some title'. > > And I hooked this code to a widget through the #action: method. > The problem is: If I use a ButtonModel, the code behaves correctly > showing the dialog. > If I use an instance of the class ImageModel to display an icon, the > dialog is displayed but the interface "hangs", in the sense that the > "ok" button won't close the dialog and every click would spawn a new > dialog. > > I would like to use an icon because it integrates better with the > interface. > Do you know if it is a bug or if I am doing something wrong? > > Thanks, > Tommaso > > > P.s.: Steps to reproduce > > If you need a working example you can inspect the code on the bleeding > edge version of ShoreLine Reporter by following these instructions: > 1. download a recent Pharo 4 image; > 2. open a workspace and run: ConfigurationOfShoreLineReporter > loadBleedingEdge > 3. trigger an exception (for example by running 3/0 in a workspace). > 4. click 'Report' > 5. click the '?' button on the right side of the window. > > >

Dec. 14, 2014

Re: [Pharo-users] Problem with Spec icon

by stepharo

I'm trying to understand, could you see if you can reproduce the problem with just the LongMessageDialog? Le 14/12/14 20:26, Tommaso Dal Sasso a Ã©crit : > I have a weird behavior building an interface with Spec. > > I have a window built with Spec, and I want to add a button that shows > a dialog with some text. > To display the dialog I use the following line: > > UIManager default longMessage: 'a text message' title: 'some title'. > > And I hooked this code to a widget through the #action: method. > The problem is: If I use a ButtonModel, the code behaves correctly > showing the dialog. > If I use an instance of the class ImageModel to display an icon, the > dialog is displayed but the interface "hangs", in the sense that the > "ok" button won't close the dialog and every click would spawn a new > dialog. > > I would like to use an icon because it integrates better with the > interface. > Do you know if it is a bug or if I am doing something wrong? > > Thanks, > Tommaso > > > P.s.: Steps to reproduce > > If you need a working example you can inspect the code on the bleeding > edge version of ShoreLine Reporter by following these instructions: > 1. download a recent Pharo 4 image; > 2. open a workspace and run: ConfigurationOfShoreLineReporter > loadBleedingEdge > 3. trigger an exception (for example by running 3/0 in a workspace). > 4. click 'Report' > 5. click the '?' button on the right side of the window. > > >

Dec. 14, 2014

Re: [Pharo-users] Problem with Spec icon

by stepharo

As soon as you scroll the list then the ok button works. This is strange. Did you check a bit the code of ImageModel? Stef Le 14/12/14 20:26, Tommaso Dal Sasso a Ã©crit : > ConfigurationOfShoreLineReporter loadBleedingEdge

Dec. 14, 2014

Re: [Pharo-users] Problem with Spec icon

by Nicolai Hess

2014-12-14 20:26 GMT+01:00 Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com>: > > I have a weird behavior building an interface with Spec. > > I have a window built with Spec, and I want to add a button that shows a > dialog with some text. > To display the dialog I use the following line: > > UIManager default longMessage: 'a text message' title: 'some title'. > > And I hooked this code to a widget through the #action: method. > The problem is: If I use a ButtonModel, the code behaves correctly showing > the dialog. > If I use an instance of the class ImageModel to display an icon, the > dialog is displayed but the interface "hangs", in the sense that the "ok" > button won't close the dialog and every click would spawn a new dialog. > > I would like to use an icon because it integrates better with the > interface. > Do you know if it is a bug or if I am doing something wrong? > > Thanks, > Tommaso > > > P.s.: Steps to reproduce > > If you need a working example you can inspect the code on the bleeding > edge version of ShoreLine Reporter by following these instructions: > 1. download a recent Pharo 4 image; > 2. open a workspace and run: ConfigurationOfShoreLineReporter > loadBleedingEdge > 3. trigger an exception (for example by running 3/0 in a workspace). > 4. click 'Report' > 5. click the '?' button on the right side of the window. > > This is a known problem, if a modal dialog is opened from a "mouse clicked" event.

Dec. 14, 2014

Problem with Spec icon

by Tommaso Dal Sasso

I have a weird behavior building an interface with Spec. I have a window built with Spec, and I want to add a button that shows a dialog with some text. To display the dialog I use the following line: UIManager default longMessage: 'a text message' title: 'some title'. And I hooked this code to a widget through the #action: method. The problem is: If I use a ButtonModel, the code behaves correctly showing the dialog. If I use an instance of the class ImageModel to display an icon, the dialog is displayed but the interface "hangs", in the sense that the "ok" button won't close the dialog and every click would spawn a new dialog. I would like to use an icon because it integrates better with the interface. Do you know if it is a bug or if I am doing something wrong? Thanks, Tommaso P.s.: Steps to reproduce If you need a working example you can inspect the code on the bleeding edge version of ShoreLine Reporter by following these instructions: 1. download a recent Pharo 4 image; 2. open a workspace and run: ConfigurationOfShoreLineReporter loadBleedingEdge 3. trigger an exception (for example by running 3/0 in a workspace). 4. click 'Report' 5. click the '?' button on the right side of the window.

Dec. 14, 2014

Re: [Pharo-users] Roassal configuration missing Glamour dependency

by Yuriy Tymchuk

It depends. GTInspector is present by default in Pharo4, but in Pharo3 you have to load it. Maybe this blogpost can be useful. http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… <http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe…> Uko > On 14 Dec 2014, at 17:32, Daniel Lyons <fusion(a)storytotell.org> wrote: > > It's worse than that anyway, now it's missing GTInspector. What package provides that class? > >> On Dec 14, 2014, at 3:06 AM, stepharo <stepharo(a)free.fr> wrote: >> >> I think that roassal packaging is naive. >> Roassal core should not depend from Glamour >> and there should be a RoassalGlamour configuration >> >> Stf >> Le 14/12/14 07:21, Daniel Lyons a Ã©crit : >>> I loaded Roassal2 from the Configuration Browser and it added some menu items, one of which produces a debug statement about GLMPager. The problem is easily remedied by installing Glamour. I suggest there is a missing dependency in ConfigurationOfRoassal2. >>> >>> â >>> Daniel Lyons >>> >>> >>> >>> >>> >>> >> >> > > â > Daniel Lyons > > > >

Dec. 14, 2014

Re: [Pharo-users] Roassal configuration missing Glamour dependency

by Daniel Lyons

It's worse than that anyway, now it's missing GTInspector. What package provides that class? > On Dec 14, 2014, at 3:06 AM, stepharo <stepharo(a)free.fr> wrote: > > I think that roassal packaging is naive. > Roassal core should not depend from Glamour > and there should be a RoassalGlamour configuration > > Stf > Le 14/12/14 07:21, Daniel Lyons a Ã©crit : >> I loaded Roassal2 from the Configuration Browser and it added some menu items, one of which produces a debug statement about GLMPager. The problem is easily remedied by installing Glamour. I suggest there is a missing dependency in ConfigurationOfRoassal2. >> >> â >> Daniel Lyons >> >> >> >> >> >> > > â Daniel Lyons

Dec. 14, 2014

Re: [Pharo-users] How to create a custom slot class in Pharo?

by Marcus Denker

> On 14 Dec 2014, at 16:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 14 Dec 2014, at 11:38, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> >> http://stackoverflow.com/questions/27468465/how-to-create-a-custom-slot-cla… >> > > This is not yet in a shape for usersâ¦ I need to continue to work on it, but I did not find the time > the last weeks. > > When it is finished I will make a tutorial. > (this means that it is uncomplete and buggy, maybe even for the most trivial examples.) Marcus

Dec. 14, 2014