Ok but normally cr does this job.

Stef

On May 29, 2009, at 5:44 PM, François Tanguy wrote:

> See below my answer.
>
> Le 29 mai 09 à 17:34, Stéphane Ducasse a écrit :
>
>> Thanks francois.
>>
>>
>> On May 29, 2009, at 11:55 AM, François Tanguy wrote:
>>
>>> Stef,
>>>
>>> I loaded the ThreadSafeTranscript package from squeaksource and  
>>> found
>>> out one problem.
>>>
>>> The stream is not correctly reset after each access.
>>
>> why should it be reset after each access?
>
> If you do something like this
> STranscript show: 'a very longggggggggggg message'.
> STranscript show: 'a normal message'
>
> The result in the transcript will be : a very longggggggggggg messagea
> normal messageggggg message
>
> The reason is because the readLimit instance variable from
> PositionableStream is not reset to 0 after the first message.
>
>>
>>
>>> Original code uses "stream reset" but using "stream resetContents"
>>> works much better.
>
> resetContents makes the same job than reset but it also set readLimit
> to 0.
>
>>>
>>
>> ok I will check
>> I published a new version with << (= show: to be compatible with the
>> other streams)  support
>>
>> stef
>>
>>>
>>>
>>> Cheers.
>>>
>>> François
>>>
>>> Le 28 mai 09 à 23:52, Stéphane Ducasse a écrit :
>>>
>>>> Not this one.
>>>> ThreadSafeTranscript is on squeaksource same name.
>>>> Now I just check and I do not know why is shown
>>>> Argh
>>>>
>>>> Stef
>>>>
>>>>
>>>> On May 28, 2009, at 11:27 PM, François Tanguy wrote:
>>>>
>>>>> Name: Nile-Clients-damiencassou.101
>>>>> Author: damiencassou
>>>>> Time: 17 February 2009, 6:29:21 pm
>>>>> UUID: c84dacab-8c7e-48b4-b9ff-31f712051122
>>>>> Ancestors: Nile-Clients-damiencassou.99, Nile-Clients- 
>>>>> damiencassou.
>>>>> 100
>>>>>
>>>>> François
>>>>>
>>>>> Le 28 mai 09 à 23:19, Stéphane Ducasse a écrit :
>>>>>
>>>>>> Which version of threadSafeTrasncruipt do you have
>>>>>>
>>>>>> I have
>>>>>>
>>>>>>
>>>>>> clear
>>>>>>  "Clear all characters and redisplay the view"
>>>>>>  
>>>>>>  self changed: #clearText.
>>>>>>  accessSemaphore
>>>>>>          critical: [ stream reset ]
>>>>>>
>>>>>> Stef
>>>>>>
>>>>>>
>>>>>> On May 28, 2009, at 11:06 PM, François Tanguy wrote:
>>>>>>
>>>>>>> Yes I already tried but a DNU showed up when trying to execute
>>>>>>> "STranscript clear".
>>>>>>> The method reset does not exist. See the implementation below.
>>>>>>>
>>>>>>> clear
>>>>>>>         "Clear all characters and redisplay the view"
>>>>>>>         
>>>>>>>         accessSemaphore critical:
>>>>>>>                                 [ self changed: #clearText.
>>>>>>>                                 self reset ]
>>>>>>>
>>>>>>> François
>>>>>>>
>>>>>>> Le 28 mai 09 à 22:56, Stéphane Ducasse a écrit :
>>>>>>>
>>>>>>>> francois
>>>>>>>>
>>>>>>>> on squeaksource there is a threadsafeTranscript
>>>>>>>> can you try it?
>>>>>>>> The idea is to get it to replace the non thread safe (= defult
>>>>>>>> one).
>>>>>>>>
>>>>>>>> Stef
>>>>>>>> On May 28, 2009, at 10:49 PM, François Tanguy wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> try this in a workspace (image 10319) :
>>>>>>>>>
>>>>>>>>> "First open a Transcript via the world menu"
>>>>>>>>> Transcript clear.
>>>>>>>>> 5 timesRepeat: [ [Transcript show: 'Hello'] fork ]
>>>>>>>>>
>>>>>>>>> Behavior is bad.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Now, try the following:
>>>>>>>>>
>>>>>>>>> Transcript clear.
>>>>>>>>> Transcript open.
>>>>>>>>> 5 timesRepeat: [ [Transcript show: 'Hello'] fork ]
>>>>>>>>>
>>>>>>>>> It is always working.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Is it a known problem ? Should we open an issue ?
>>>>>>>>>
>>>>>>>>> François
>>>>>>>>> _______________________________________________
>>>>>>>>> Pharo-project mailing list
>>>>>>>>> [email protected]
>>>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-
>>>>>>>>> project
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Pharo-project mailing list
>>>>>>>> [email protected]
>>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-
>>>>>>>> project
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Pharo-project mailing list
>>>>>>> [email protected]
>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-
>>>>>>> project
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Pharo-project mailing list
>>>>>> [email protected]
>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-
>>>>>> project
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Pharo-project mailing list
>>>>> [email protected]
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- 
>>>>> project
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [email protected]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to