Hi Tomas,
I get all this (it sticks with what I had suspected). And I agree about
keeping development side simple.
About your last suggestion, well, I'm not sure. It is not such painful
for the user to select files correctly for the very first step the
SetupDialog rather than from selection tr
Hi Gauthier,
I really didn't like the previous design of batch mode, for several reasons:
1) Some modules are simply not supposed to take the previous module's output as
their input. A typical example is the alignment module, which may require a
combined output of several previous steps.
2) In
Hi Tomas,
I understand that this is important to have it work this way for better
compatibility in Headless Mode, but wouldn't it be more practical to
have the choice of using pattern or using the result of the previous
step (as it used to be), at least in GUI mode? That was very handy that
wa
Thomas
From: TFRD (Thomas Franck Dyrlund) [mailto:t...@steno.dk]
Sent: 15. december 2014 08:24
To: Developer discussion
Subject: Re: [Mzmine-devel] Recent commits
Hi Tomas
The changes to the PeakListParameter (and possibly also the
RawDataFileParameter?) causes the previous selected peak list
: TFRD (Thomas Franck Dyrlund) [mailto:t...@steno.dk]
Sent: 15. december 2014 08:24
To: Developer discussion
Subject: Re: [Mzmine-devel] Recent commits
Hi Tomas
The changes to the PeakListParameter (and possibly also the
RawDataFileParameter?) causes the previous selected peak list to be
Hi Tomas
The changes to the PeakListParameter (and possibly also the
RawDataFileParameter?) causes the previous selected peak list to be remembered
and selected when opening a MZmine instance. This means that I have a peak list
available under the parameters even though I don't have any peak
