Hello,
Sorry for the slow reply, the weekend got in the way and then it slipped
through the cracks.
We've looked at the photos but can't quite figure out what is going on
(this is a good example of when you need to be staring at the screen). Is
this behaviour persisting? If it happened for more than this pair I would
have said this was perhaps the mouse location coming out wrong, but it
sounds like it is only this pair. And if they were in the same peaklist I
would have said this was perhaps the Python world and C world getting out
of sync, but that should be sorted with a re-start and can't really be
happening here if the other windows are ok. So a puzzle.
Wayne
On Fri, 7 Apr 2006, Murali Vadivelu wrote:
> I have noticed this strange behaviour just in one occasion but not
> getting any error message on the command line:
> 1. When I select a peak, either a HBHAcoNH peak (N - 106.2) or
> TOCSY-3D (105.5) peak, in a window with F1:H F2:H F3:N dimensions,
> the other one gets selected.
>
>
|