Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 836 by [hidden email]: Bug in GLMMorphicBrowserRenderer
http://code.google.com/p/moose-technology/issues/detail?id=836


Hello, in the class GLMMorphicBrowserRenderer I had a out of bound problem  
the first time that a model was charged (click on model).

I changed the code of the render method (when activeEntity message on  
aBrowser object is sent)as follow:

aBrowser activeEntity: ((aBrowser panes at: (ann pageIndex max: aBrowser  
panes size)) port: #entity) value ].

It was ok for me.

So, I suggest this change to the Moose Developers.

Hugs,

Julio Ariel Hurtado

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

Tudor Girba-2
Hi,

Thanks for the report.

I cannot reproduce this problem. Could you provide step by step
instructions to reproduce it?

Cheers,
Doru


On Fri, Sep 14, 2012 at 4:12 PM,  <[hidden email]> wrote:

> Status: New
> Owner: ----
> Labels: Type-Defect Priority-Medium
>
> New issue 836 by [hidden email]: Bug in GLMMorphicBrowserRenderer
> http://code.google.com/p/moose-technology/issues/detail?id=836
>
>
> Hello, in the class GLMMorphicBrowserRenderer I had a out of bound problem
> the first time that a model was charged (click on model).
>
> I changed the code of the render method (when activeEntity message on
> aBrowser object is sent)as follow:
>
> aBrowser activeEntity: ((aBrowser panes at: (ann pageIndex max: aBrowser
> panes size)) port: #entity) value ].
>
> It was ok for me.
>
> So, I suggest this change to the Moose Developers.
>
> Hugs,
>
> Julio Ariel Hurtado
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

abergel
Hi Doru,

I pair programmed with Julio and we bumped into this strange problem.
To reproduce the problem, you need to install ProcessModel, and load an EMF .xml file. I guess the unit test contains a small .xml as example. I have tried with it, maybe you can reproduce the problem. Else Julio can send you a larger .xml

Here is our experience, maybe it is enough for you to understand what is going on:
The model gets loaded and is listed in the Moose panel. Clicking on the model for the first time will open many debuggers, all indicating that "ann pageIndex" goes above the number of "aBrowser panes".
Clicking a second time the problem does not show up.

Julio told me that larger our model is, and more debuggers we get.

Hope it helps

Cheers,
Alexandre



On Sep 14, 2012, at 11:16 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> Thanks for the report.
>
> I cannot reproduce this problem. Could you provide step by step
> instructions to reproduce it?
>
> Cheers,
> Doru
>
>
> On Fri, Sep 14, 2012 at 4:12 PM,  <[hidden email]> wrote:
>> Status: New
>> Owner: ----
>> Labels: Type-Defect Priority-Medium
>>
>> New issue 836 by [hidden email]: Bug in GLMMorphicBrowserRenderer
>> http://code.google.com/p/moose-technology/issues/detail?id=836
>>
>>
>> Hello, in the class GLMMorphicBrowserRenderer I had a out of bound problem
>> the first time that a model was charged (click on model).
>>
>> I changed the code of the render method (when activeEntity message on
>> aBrowser object is sent)as follow:
>>
>> aBrowser activeEntity: ((aBrowser panes at: (ann pageIndex max: aBrowser
>> panes size)) port: #entity) value ].
>>
>> It was ok for me.
>>
>> So, I suggest this change to the Moose Developers.
>>
>> Hugs,
>>
>> Julio Ariel Hurtado
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

Tudor Girba-2
How do I install the ProcessModel?

Doru

On Fri, Sep 14, 2012 at 4:31 PM, Alexandre Bergel
<[hidden email]> wrote:

> Hi Doru,
>
> I pair programmed with Julio and we bumped into this strange problem.
> To reproduce the problem, you need to install ProcessModel, and load an EMF .xml file. I guess the unit test contains a small .xml as example. I have tried with it, maybe you can reproduce the problem. Else Julio can send you a larger .xml
>
> Here is our experience, maybe it is enough for you to understand what is going on:
> The model gets loaded and is listed in the Moose panel. Clicking on the model for the first time will open many debuggers, all indicating that "ann pageIndex" goes above the number of "aBrowser panes".
> Clicking a second time the problem does not show up.
>
> Julio told me that larger our model is, and more debuggers we get.
>
> Hope it helps
>
> Cheers,
> Alexandre
>
>
>
> On Sep 14, 2012, at 11:16 AM, Tudor Girba <[hidden email]> wrote:
>
>> Hi,
>>
>> Thanks for the report.
>>
>> I cannot reproduce this problem. Could you provide step by step
>> instructions to reproduce it?
>>
>> Cheers,
>> Doru
>>
>>
>> On Fri, Sep 14, 2012 at 4:12 PM,  <[hidden email]> wrote:
>>> Status: New
>>> Owner: ----
>>> Labels: Type-Defect Priority-Medium
>>>
>>> New issue 836 by [hidden email]: Bug in GLMMorphicBrowserRenderer
>>> http://code.google.com/p/moose-technology/issues/detail?id=836
>>>
>>>
>>> Hello, in the class GLMMorphicBrowserRenderer I had a out of bound problem
>>> the first time that a model was charged (click on model).
>>>
>>> I changed the code of the render method (when activeEntity message on
>>> aBrowser object is sent)as follow:
>>>
>>> aBrowser activeEntity: ((aBrowser panes at: (ann pageIndex max: aBrowser
>>> panes size)) port: #entity) value ].
>>>
>>> It was ok for me.
>>>
>>> So, I suggest this change to the Moose Developers.
>>>
>>> Hugs,
>>>
>>> Julio Ariel Hurtado
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

abergel
Gofer new
        squeaksource: 'ProcessModel';
        package: 'ConfigurationOfProcessModel';
        load.
(Smalltalk at: #ConfigurationOfProcessModel) perform: #loadDefault

Alexandre

On Sep 14, 2012, at 11:43 AM, Tudor Girba <[hidden email]> wrote:

> How do I install the ProcessModel?
>
> Doru
>
> On Fri, Sep 14, 2012 at 4:31 PM, Alexandre Bergel
> <[hidden email]> wrote:
>> Hi Doru,
>>
>> I pair programmed with Julio and we bumped into this strange problem.
>> To reproduce the problem, you need to install ProcessModel, and load an EMF .xml file. I guess the unit test contains a small .xml as example. I have tried with it, maybe you can reproduce the problem. Else Julio can send you a larger .xml
>>
>> Here is our experience, maybe it is enough for you to understand what is going on:
>> The model gets loaded and is listed in the Moose panel. Clicking on the model for the first time will open many debuggers, all indicating that "ann pageIndex" goes above the number of "aBrowser panes".
>> Clicking a second time the problem does not show up.
>>
>> Julio told me that larger our model is, and more debuggers we get.
>>
>> Hope it helps
>>
>> Cheers,
>> Alexandre
>>
>>
>>
>> On Sep 14, 2012, at 11:16 AM, Tudor Girba <[hidden email]> wrote:
>>
>>> Hi,
>>>
>>> Thanks for the report.
>>>
>>> I cannot reproduce this problem. Could you provide step by step
>>> instructions to reproduce it?
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On Fri, Sep 14, 2012 at 4:12 PM,  <[hidden email]> wrote:
>>>> Status: New
>>>> Owner: ----
>>>> Labels: Type-Defect Priority-Medium
>>>>
>>>> New issue 836 by [hidden email]: Bug in GLMMorphicBrowserRenderer
>>>> http://code.google.com/p/moose-technology/issues/detail?id=836
>>>>
>>>>
>>>> Hello, in the class GLMMorphicBrowserRenderer I had a out of bound problem
>>>> the first time that a model was charged (click on model).
>>>>
>>>> I changed the code of the render method (when activeEntity message on
>>>> aBrowser object is sent)as follow:
>>>>
>>>> aBrowser activeEntity: ((aBrowser panes at: (ann pageIndex max: aBrowser
>>>> panes size)) port: #entity) value ].
>>>>
>>>> It was ok for me.
>>>>
>>>> So, I suggest this change to the Moose Developers.
>>>>
>>>> Hugs,
>>>>
>>>> Julio Ariel Hurtado
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

Tudor Girba-2
I tried. First, there is no loadDefault.

Then I loaded loadBleedingEdge, but I get a DNU on XMLDocument>>//. I
guess that I am missing some XML extension. Which one is it?

Doru

On Fri, Sep 14, 2012 at 4:57 PM, Alexandre Bergel
<[hidden email]> wrote:

> Gofer new
>         squeaksource: 'ProcessModel';
>         package: 'ConfigurationOfProcessModel';
>         load.
> (Smalltalk at: #ConfigurationOfProcessModel) perform: #loadDefault
>
> Alexandre
>
> On Sep 14, 2012, at 11:43 AM, Tudor Girba <[hidden email]> wrote:
>
>> How do I install the ProcessModel?
>>
>> Doru
>>
>> On Fri, Sep 14, 2012 at 4:31 PM, Alexandre Bergel
>> <[hidden email]> wrote:
>>> Hi Doru,
>>>
>>> I pair programmed with Julio and we bumped into this strange problem.
>>> To reproduce the problem, you need to install ProcessModel, and load an EMF .xml file. I guess the unit test contains a small .xml as example. I have tried with it, maybe you can reproduce the problem. Else Julio can send you a larger .xml
>>>
>>> Here is our experience, maybe it is enough for you to understand what is going on:
>>> The model gets loaded and is listed in the Moose panel. Clicking on the model for the first time will open many debuggers, all indicating that "ann pageIndex" goes above the number of "aBrowser panes".
>>> Clicking a second time the problem does not show up.
>>>
>>> Julio told me that larger our model is, and more debuggers we get.
>>>
>>> Hope it helps
>>>
>>> Cheers,
>>> Alexandre
>>>
>>>
>>>
>>> On Sep 14, 2012, at 11:16 AM, Tudor Girba <[hidden email]> wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks for the report.
>>>>
>>>> I cannot reproduce this problem. Could you provide step by step
>>>> instructions to reproduce it?
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>> On Fri, Sep 14, 2012 at 4:12 PM,  <[hidden email]> wrote:
>>>>> Status: New
>>>>> Owner: ----
>>>>> Labels: Type-Defect Priority-Medium
>>>>>
>>>>> New issue 836 by [hidden email]: Bug in GLMMorphicBrowserRenderer
>>>>> http://code.google.com/p/moose-technology/issues/detail?id=836
>>>>>
>>>>>
>>>>> Hello, in the class GLMMorphicBrowserRenderer I had a out of bound problem
>>>>> the first time that a model was charged (click on model).
>>>>>
>>>>> I changed the code of the render method (when activeEntity message on
>>>>> aBrowser object is sent)as follow:
>>>>>
>>>>> aBrowser activeEntity: ((aBrowser panes at: (ann pageIndex max: aBrowser
>>>>> panes size)) port: #entity) value ].
>>>>>
>>>>> It was ok for me.
>>>>>
>>>>> So, I suggest this change to the Moose Developers.
>>>>>
>>>>> Hugs,
>>>>>
>>>>> Julio Ariel Hurtado
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Every thing has its own flow"
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel  http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

abergel
You need to load Pastell.
ConfigurationOfProcessModel does not load Pastell, no idea why. I could not find an obvious reason...

Alexandre


On Sep 14, 2012, at 12:08 PM, Tudor Girba <[hidden email]> wrote:

> I tried. First, there is no loadDefault.
>
> Then I loaded loadBleedingEdge, but I get a DNU on XMLDocument>>//. I
> guess that I am missing some XML extension. Which one is it?
>
> Doru
>
> On Fri, Sep 14, 2012 at 4:57 PM, Alexandre Bergel
> <[hidden email]> wrote:
>> Gofer new
>>        squeaksource: 'ProcessModel';
>>        package: 'ConfigurationOfProcessModel';
>>        load.
>> (Smalltalk at: #ConfigurationOfProcessModel) perform: #loadDefault
>>
>> Alexandre
>>
>> On Sep 14, 2012, at 11:43 AM, Tudor Girba <[hidden email]> wrote:
>>
>>> How do I install the ProcessModel?
>>>
>>> Doru
>>>
>>> On Fri, Sep 14, 2012 at 4:31 PM, Alexandre Bergel
>>> <[hidden email]> wrote:
>>>> Hi Doru,
>>>>
>>>> I pair programmed with Julio and we bumped into this strange problem.
>>>> To reproduce the problem, you need to install ProcessModel, and load an EMF .xml file. I guess the unit test contains a small .xml as example. I have tried with it, maybe you can reproduce the problem. Else Julio can send you a larger .xml
>>>>
>>>> Here is our experience, maybe it is enough for you to understand what is going on:
>>>> The model gets loaded and is listed in the Moose panel. Clicking on the model for the first time will open many debuggers, all indicating that "ann pageIndex" goes above the number of "aBrowser panes".
>>>> Clicking a second time the problem does not show up.
>>>>
>>>> Julio told me that larger our model is, and more debuggers we get.
>>>>
>>>> Hope it helps
>>>>
>>>> Cheers,
>>>> Alexandre
>>>>
>>>>
>>>>
>>>> On Sep 14, 2012, at 11:16 AM, Tudor Girba <[hidden email]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks for the report.
>>>>>
>>>>> I cannot reproduce this problem. Could you provide step by step
>>>>> instructions to reproduce it?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> On Fri, Sep 14, 2012 at 4:12 PM,  <[hidden email]> wrote:
>>>>>> Status: New
>>>>>> Owner: ----
>>>>>> Labels: Type-Defect Priority-Medium
>>>>>>
>>>>>> New issue 836 by [hidden email]: Bug in GLMMorphicBrowserRenderer
>>>>>> http://code.google.com/p/moose-technology/issues/detail?id=836
>>>>>>
>>>>>>
>>>>>> Hello, in the class GLMMorphicBrowserRenderer I had a out of bound problem
>>>>>> the first time that a model was charged (click on model).
>>>>>>
>>>>>> I changed the code of the render method (when activeEntity message on
>>>>>> aBrowser object is sent)as follow:
>>>>>>
>>>>>> aBrowser activeEntity: ((aBrowser panes at: (ann pageIndex max: aBrowser
>>>>>> panes size)) port: #entity) value ].
>>>>>>
>>>>>> It was ok for me.
>>>>>>
>>>>>> So, I suggest this change to the Moose Developers.
>>>>>>
>>>>>> Hugs,
>>>>>>
>>>>>> Julio Ariel Hurtado
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> [hidden email]
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "Every thing has its own flow"
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel  http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

moose-technology
In reply to this post by moose-technology

Comment #1 on issue 836 by [hidden email]: Bug in  
GLMMorphicBrowserRenderer
http://code.google.com/p/moose-technology/issues/detail?id=836

Thanks, but I cannot reproduce this bug.

Please provide a more detailed explanation of how to reproduce it.  
Otherwise, I will simply close it.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 836 in moose-technology: Bug in GLMMorphicBrowserRenderer

moose-technology
Updates:
        Status: Invalid

Comment #2 on issue 836 by [hidden email]: Bug in  
GLMMorphicBrowserRenderer
http://code.google.com/p/moose-technology/issues/detail?id=836

Unfortunately, I could not reproduce the problem, so I will close the  
issue. If you can provide more details, we can reopen it.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev