* Bug: In Kite, in TrackSegment::_postDogleg() when called through
TrackSegment::moveUp(), if no dogleg are created, that is the
segment is "pivoted up" (for example a M3 connected to only
M4 that is pivoted to M5), the segment was *not* rescheduled as
it ough to be. The end result was a M5 in a M3 track...
* Change: In Kite, in Track::checkOverlaps() in case of further
problems, also check that TrackSegments and Track are in the
same layer.