I investigated PluggableListMorph and ListMorph, the problem you
describe is there (likely this should be fixed in Pharo). In
Name: OB-Morphic-lr.149
Author: lr
Time: 11 October 2010, 10:17:53 am
UUID: 285339d9-f9da-4c6d-98b9-e09ea154c91e
Ancestors: OB-Morphic-lr.148
- more efficient fix for list updating
I try to remember the current scroll position before updating any OB
list, so I guess this works around the problem (indeed the UI feels
better after the change).
I am not sure if this fix is safe. It works well in my images, but it
might break some assumption of Morphic and destroy your image in the
worst case.
Lukas
On 10 October 2010 18:39, Lukas Renggli <
[hidden email]> wrote:
> I am not sure if I understand your question correctly, but presumably
> your method is too long or you have too many methods in one class or
> protocol. OB punishes you for this :-)
>
> Lukas
>
> 2010/10/10 Mariano Martinez Peck <
[hidden email]>:
>> Hi. Me again. Not sure if it is a bug but I don't like it. If you do, no
>> problem then ;)
>>
>> Suppose you are working with a method that it is in the half of the method
>> pane of OB. Once you save it or run test on it for example, the "scroll" and
>> the method pane is updated so that THAT method is first, above. And
>> sometimes this is quite annoying for me.
>>
>> Cheers
>>
>> Mariano
>>
>> _______________________________________________
>> Pharo-project mailing list
>>
[hidden email]
>>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project>>
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>
--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
