Yes,
You were right,
the version i posted conflicted with ParenBlinking.
I fixed this so now hopefully both additions may coexist peacefully.
Note though that filing in ParenBlinking after ShrinkingSelection
will most probably severely break things.
I think this would be easily avoided with a little bit more granularity
in the class definition.
In lieu of saving a whole class definition with each change it would
be really helpful to only save the changes (i.e a set of change identifiers along the lines of:
- addInstanceVariableNamed:
- removeInstanceVariableNamed:
- renameInstanceVariable: toBe:
[same for class variables and maybe Pools]
- ChangeSuperclass:toBe: (or with only one parameter if you don't count on finding conflicts)
- ChangeSystemCategora:toBe:

And of course some kind of compatiblity fileOut package (maybe a bit more sophisticated than my
last attempt on such a beast)

I attached the corrected (but not tested) version.

Regards,
Torge

Am 18.11.2002 13:43:35 schrieb Markus Fritsche <Fritsche.Markus at gmx.net>:

>Torge.Husfeldt said:
>> Hallo Joern,
>>
>> Thank you very much for catching this one.
>> Do you think this would be a good candidate for putting on
>> SqueakMap? Do you find the code helpful? Does it break anything else?
>
>Can it be that it interferes with ParenBlinking by Avi Bryant?
>
>Regards, Markus
>
>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: shrinkingSelection.4.zip
Type: application/zip
Size: 18786 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20021118/951f96ba/shrinkingSelection.4.zip