sorry, no, i can't reproduce it.
thanks
On Wed, Sep 21, 2016 at 4:22 PM, Tudor Girba wrote:
> Hi,
>
> No, this was not at all a stupid question. It might be that we have a
> memory leak.
>
> Could you reproduce the problem?
>
> Cheers,
> Doru
>
> > On Sep 21, 2016, at 4:34 PM, Bernardo Ezequiel
Hi,
No, this was not at all a stupid question. It might be that we have a memory
leak.
Could you reproduce the problem?
Cheers,
Doru
> On Sep 21, 2016, at 4:34 PM, Bernardo Ezequiel Contreras
> wrote:
>
> everything was closed, i was using the simple workspace. but anyways there
> were ref
everything was closed, i was using the simple workspace. but anyways there
were references.
it was a stupid question, i solved it starting from a fresh image.
thanks
On Wed, Sep 21, 2016 at 1:16 AM, Tudor Girba wrote:
> Hi,
>
> You should close the respective Glamour browser. Could it be that
Hi,
You should close the respective Glamour browser. Could it be that you have an
opened inspector? If so, try closing it and see what happens.
Doru
> On Sep 21, 2016, at 3:28 AM, Bernardo Ezequiel Contreras
> wrote:
>
> Hi,
> is there a way to tell to GLMPanePort to release my stupid obj
Hi,
is there a way to tell to GLMPanePort to release my stupid objects and
classes?
because i want to change a class and i can't. there's another bug when
migrating
instances (not easy to reproduce). so im trying to release all the
references.
is it possible??
thanks.
example:
Port (pane=#evalu
