On Sun, Jan 18, 2009 at 3:14 AM, Thomas Moschny <
address@hidden> wrote:
> Derek Scherger wrote:
>> - after a reconstruction path is loaded it is scanned in forward order
>> looking for a cached roster to start from. if one is found, the
>> reconstruction path is truncated at that point and reconstruction will
>> start from the closest cached roster.
>
> Somehow I always thought the code that searches for the reconstruction
> patch would do this already: not only stop at base rosters but also at
> cached rosters - seems I was wrong.
Err, yeah, it definitely should be doing that! And if it isn't, it