but if we trace an image it should work so how can we make sure that the UI 
process is launched?

Stef

On Dec 2, 2011, at 12:15 PM, Igor Stasenko wrote:

> On 2 December 2011 10:00, Pavel Krivanek <[email protected]> wrote:
>> Well, so it works, I only had to remove line
>> 
>> SystemWindow wakeUpTopWindowUponStartup.
>> 
> yes, now i remember we were patching that (among other things).
> 
>> from the method SystemTracer2 processStartup.
>> 
>> Cheers,
>> -- Pavel
>> 
>> 
>> On Fri, Dec 2, 2011 at 9:09 AM, Stéphane Ducasse
>> <[email protected]> wrote:
>>> I published a new version in PharoTaskForces.
>>> Thanks!
>>> 
>>> stef
>>> 
>>> 
>>> 
>>> On Dec 1, 2011, at 10:52 PM, Pavel Krivanek wrote:
>>> 
>>>> What version of SystemTracer do you use, I would try Pharo-Kernel so
>>>> we can see if it is UI related.
>>>> 
>>>> -- Pavel
>>>> 
>>>> On Thu, Dec 1, 2011 at 10:32 PM, Stéphane Ducasse
>>>> <[email protected]> wrote:
>>>>> 
>>>>> On Dec 1, 2011, at 10:19 PM, Igor Stasenko wrote:
>>>>> 
>>>>>> On 1 December 2011 23:15, Stéphane Ducasse <[email protected]> 
>>>>>> wrote:
>>>>>>> Hi guys
>>>>>>> 
>>>>>>> I made sure that SystemTracer is not invoking deprecated method in 1.4
>>>>>>> Now when I execute
>>>>>>>        SystemTracer2 writeImage: 'clone.image'
>>>>>>> the process finishes, the image I obtain start but the UI is not 
>>>>>>> working.
>>>>>>> 
>>>>>>> Benjamin was it working when you tried with igor?
>>>>>>> 
>>>>>> 
>>>>>> Yes, we had a working image, but not without some voodoo dance.
>>>>>> But i don't remember what we did.
>>>>>> In Hazel we are replacing a process, so there is no UI thread. A
>>>>>> SystemTracer alone, however should copy stuff as it is.
>>>>> 
>>>>> I just tried in 1.3 and I get the same problem. The UI is damaged and no 
>>>>> interaction.
>>>>> We should have a look at that.
>>>>> BTW are you better or still sick?
>>>>> 
>>>>> Stef
>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Best regards,
>>>>>> Igor Stasenko.
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 
> 
> -- 
> Best regards,
> Igor Stasenko.
> 


Reply via email to