Most relevant since last bundle/update... 

The most important update is related to resources usage, it is now much lighter in CPU usage.

~ Basket SL in $ changed it behaviour and to effectively work as SL, a negative number is required, otherwise it will work as an interactive profit lock.
~ Basket TP in $ allow negative numbers now.

TP or SL in Pips or %ADR are unchanged by now, thus positive numbers must be used for either one. 

~ Dashboard update time interval fixed.

+ Print slippage and time spent to place the order.

+ Time to end of daily session time.

+ Pivot container now shows warning when price is around PL or R3/S3 (it isn't a filter, only a visual by now).

+ Pivot container now shows R3, R2, R1, PL, S1, S2 and S3 values in tooltips.

+ Orders requiring TP/SL are opened with their corresponding stops now, so if an "invalid stops" error is returned by the server, the order is immediately rejected.
  This is a big improvement over previous revisions where this was a two steps procedure. (orders placed with no stops and TP/SL set afterwards, ending with some orders -due to TP/SL too close to price- with no stops where a stop should have been placed). This modification aims to fix the referenced issue, rejecting orders with invalid stops in real time.

Some cosmetic changes because I'm not really happy yet with it current design.

As usual ... many bug fixes and some new ones as well ...

-------------------------------------------------------------------------------------

New version of MADdash PIN (DBMultiASM_MADdash_PIN_v2.0) and template (MADdashPINv2).

MADdash can now be used for the 3 available PIN(s) at the same time (v2 of PIN required).
To do so, one chart per PIN is required, and each chart must have the MADdashPINv2 template loaded (the template includes MADdash itself and v2 of PIN).

The belonging PIN must be assigned in the DBMultiASM_MADdash_PIN_v2.0 properties (by default it has no PIN assignment).
In the dashboard preferences, under PIN section, compatibility must be set to Own (default in this revision), so there's no need to choose MADdash compatibility unless you want to stick to the previous version of the PIN.