This isn't necessarily an Entity Modeler problem ... It's like looking
for an OutOfMemoryError. That it's dying in one place doesn't mean
that's to blame. So this could be anything in Eclipse leaking
resources and it just happens that Entity Modeler is the one that you
have open when it happens. This is not saying it's NOT EM, just
saying it's not NECESSARILY em.
ms
On May 8, 2008, at 12:14 PM, Ken Anderson wrote:
> Sometimes I dismiss it and everything works fine afterwards. Other
> times, strange things start to occur (like the entity modeler
> property inspector not drawing), which gets fixed with a restart.
>
> On May 8, 2008, at 12:11 PM, Jake Fisher wrote:
>
>> "No More Handles" as an error refers to the underlying SWT graphics
>> components loading native ui resources(particularly on OSX). You
>> shouldn't run out. When I have had it happen, I have just restarted
>> and it has gone away fine. It may be an issue with disposing
>> resources
>> in the entity modeler code if it is a common problem (don't think it
>> is though) but yeah should just go away I think?
>>
>> ~jake
>>
>> On Wed, May 7, 2008 at 3:58 PM, Ken Anderson
>> <kenlist..nderhome.com> wrote:
>>> Everyone,
>>>
>>> I'm using WOLips 3.3.4763, and when using entity modeler I am
>>> constantly
>>> getting Eclipse errors saying 'no more handles'. Any idea what's
>>> going on?
>>> Has anyone else experienced this?
>>>
>>> Thanks,
>>> Ken
>>>
>>
>>
>>
>> --
>> Jacob Fisher
>> fisherj..mail.com
>> www.jakeandlisa.com
>
This archive was generated by hypermail 2.0.0 : Thu May 08 2008 - 12:21:35 EDT