Problem with concurrent mode and overlapping programs

[cdesouza]

Hi,

I was experimenting with concurrent and sequential mode and work out that

• for sequential mode the running program has precedence and will stop other programs from starting
  
• for concurrent mode a scheduled program has precedence and will stop a running program, well sort of, see below
  

If this is the case then it would be good if it were documented in the Wiki.

And now to the well sort of bit, which I think is a bug. With the following setup:

• SIP Version: 5.1.19
  

• Mode: Concurrent
  
• Prog1: S1, 09:00, 4 mins
  
• Prog2: S1, 09:02, 6 mins 
  

I get the following results

1. 09:00 Prog1 will start (as expected)
   
2. 09:02 Prog2 will start, terminating Prog1 (as expected)
   
3. 09:04 Prog2 will terminate (this is not expected)
   

The log entry is as follows: 

• S1 04:00 67 % Prog2
  

I would have expected Prog2 to run until 09:08 and the following log entries

• S1 02:00 50% Prog1
  
• S1 06:00 100% Prog2
  

--Edit --
On a similar note with the following setup

• Prog1: S1, 09:00, 6 mins
  
• Prog2: S1, 09:02, 2 mins
  

Prog1 is terminated by Prog2 (09:02) and when Prog 2 ends (09:04) the UI show 00:00 until Prog 1 would have terminated (09:06)