The default condition of the Permanent SL and TP is "Relative". It corresponds to the older FSB versions and the current FST. Basically it means that any modification of an open position (adding, reducing ...) changes also the SL and TP levels. SL and TP are relevant to the last modification order.

Contrary to that behaviour, the "Absolute" type of SL or TP makes them unchengiable until the position is closed. In that way, the TP and SL are set when we open a position and further adding or reducing doesn't change them.

Actually you can see the difference between both options only when the strategy adds or reduces a position. Reversing a position is equal to close and open a new one in the opposite direction, therefore FSB applyes new TP and SL levels.

"Absolute" option is not compativble with the current FST.

FSB stores the backtest in the array static Session[] session;.
Each session is one backtested bar.
The actual activities from the backtest are stored as Way_Points in the session.
Each Way_Point contains the activity price, type, order and position (if any).
All available activities are:

public enum WayPointType
{
    None, Open, High, Low, Close, Entry, Exit, Add, Reduce, Reverse, Cancel
}

Open, High, Low, Close waypoints shows when the backtester reaches the corresponding price levels.

Entry, Exit, Add, Reduce, Reverse are the transactions.

Cancel shows when the backtester cancels orders.

...

You can see all this represented in the "Bar Explorer".

When drawing schedules unpleasant blinking are observ.
I offers small changes in visual components (smallbalancechart, etc.). 3rd lines of a code + my class. Blinking are not present. If interested, inform where to lay out a code.