>
> Is it possible that opening Spotter has corrupted the image?

Yes, Spotter corrupts image :( I thinks it is somehow connected with usage
of defer: by Spotter to schedule code execution in UI thread from
background thread (to perform callback in UI thread) that is not compatible
in Bloc world. Bloc introduces new Alarm mechanism, so defer: is
depreciated and I suppose Alarm are not completely compatible with old
morphic mechanism.

Sadly, but Spotter must not be opened in Bloc otherwise image dies

Cheers,
Alex

On Sat, Aug 29, 2015 at 12:56 PM, Peter Uhnák <[email protected]> wrote:

> I did use it and I know it froze after that...
> but now it happens even without using Spotter.
>
> Is it possible that opening Spotter has corrupted the image?
>
> Peter
>
> On Sat, Aug 29, 2015 at 12:35 PM, Aliaksei Syrel <[email protected]>
> wrote:
>
>> Hi Peter,
>>
>> Do you use Spotter while in Bloc?
>>
>> Cheers,
>> Alex
>>
>> On Sat, Aug 29, 2015 at 12:32 PM, Peter Uhnák <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> I've been playing with the latest Brick tools, however after about a
>>> minute or two the UI always becomes completely unresponsive. I cannot move
>>> anything nor do anything. If I press <cmd>+<dot>
>>> this shows in my terminal... but the UI is still unresponsive.
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> User Interrupt
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMorphicCompatibleBlocSpace(BlBlocSpace)>>handleEvent:
>>> BlMorphicCompatibleBlocSpace(BlBlocSpace)>>sendEventToSpace:
>>>
>>> BlMorphicEventListenerRecord(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>>
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>privateRemoveEventListener:fromOwner:previousInChain:
>>> BlMorphicCompatibleBlocSpace(BlBlocSpace)>>removeEventListener:
>>> [ :sp | sp removeEventListener: self ] in
>>> BlMorphicEventListenerRecord(BlGlobalEventListener)>>unplug in Block: [ :sp
>>> | sp removeEventListener: self ]
>>> BlockClosure>>cull:
>>> BlMorphicEventListenerRecord(BlGlobalEventListener)>>spaceDo:
>>> BlMorphicEventListenerRecord(BlGlobalEventListener)>>unplug
>>> BlMorphicEventListenerRecord>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent:
>>> BlMouseButtonOutsideEventListener(BlEventListener)>>handleEvent
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> Anyone has any idea? This is the original image I've been playing with
>>> https://drive.google.com/file/d/0B-bMBVDOi3oTdll3dGJValVIenc/view
>>>
>>> Thanks,
>>> Peter
>>>
>>
>>
>

Reply via email to