fix issue #585: the bug injected with previous fix has been fixed. Also...
fix issue #585: the bug injected with previous fix has been fixed. Also slightly improved messages from scheduler to user interface when a schedule is executed. (#596)
if((m_currentScan.backendProc!=_SCHED_NULLTARGET)&&(m_currentScan.duration>0.0)){// if the writing has not been disabled and data transfer is started only if the duration is bigger than zero......
// case 1 : the transfer is disabled, the procedure (if not NULL) retrieved, if it is different from the previous one , component are loaded(if necessary), bck configured and transfer enabled again
// case 4: we are in this case if the currentBackendProcedure is the same of the current subscan...so nothing to do
if(m_lastScanID!=0){//if this is the first scan...nothing to do
// otherwise if current scanid is different from the previous one, or the current scan is consequence of a schedule rewind (to deal with the case just one scan is present in the schedule and it will be executed continuously)
// otherwise if current scanid is different from the previous one, or the current scan is consequence of a schedule rewind
//(to deal with the case just one scan is present in the schedule and it will be executed continuously)