Tim Stevens schrieb:
>
> The advantage of having the table selection in general for peaks (i.e.
> those highlighted blue) separate from the selection of peaks in spectrum
> windows is so that you can apply separate operations to separate sets of
> peaks, i.e. freedom and control.
>
> People would be very annoyed if they had some peaks selected in the
> spectrum windows ready for some operation then clicked on a peak in a
> table only to find that the selection in the window had been reset.
>
> Analysis does offer synchronisation between the Selected Peaks popup table
> specifically and the window selected peaks. However to extend this to the
> Peak List Editor popup would be hideously restrictive. You could only
> consider one set of peaks at once.
>
The point that I would like to stress here is that some sets of peak
selections are more easily accessible through the Peak List Editor than
through the spectrum windows (e.g. all peaks related to a given
residue). It would be nice to be able to run batch operation also on them.
For some reason, I can't pass
top.popups['edit_peak_list'].table.currentObjects which (seems to be
roughly the equivalent of argServer.getCurrentPeaks() ) into a python
function.
Christoph
--
--------------------------------------------------------------------
Dr. Christoph Brockmann
Leibnitz-Institut fuer Molekulare Pharmakologie (FMP)
Robert Roessle Str. 10
D-13125 BERLIN, Germany
phone: +49-30-94793-223
email: [log in to unmask]
--------------------------------------------------------------------
|