- Search Crypto Craft
-
aeseme replied Feb 18, 2016image By the way.. I wonder how do you managed to have two instances on different BQ time-frames not knowing how or where to set it?

Dashboard EAX
-
aeseme replied Feb 18, 2016You forgot to enable the Close[C] button................................................ From the ChangeLog included in the package:

Dashboard TZ
-
aeseme replied Feb 17, 2016Deja-Vu!
Too much ROFL LMAO LOL 
!!! But it's simpler than it seems at first glance.. I wrongly answered to you in the post right above yours, and then you quoted that post just before I managed to correct it. When I corrected that ...Dashboard EAX
-
aeseme replied Feb 17, 2016image If you have the trail settings like in the picture, the trailing distance will be the last (or higher) lock level. The video doesn't show your trail settings nor all your lock levels, but it seems that you have the trail settings like in the ...
Dashboard EAX
-
aeseme replied Feb 17, 2016From the ChangeLog text file included in the package: Just let me know if that's not clear enough so I can try to make it better.

Dashboard Trading
-
aeseme replied Feb 16, 2016This was just coincidence... there were alerts for that set file at that time. This is really odd.. I don't have a coherent answer for that. If I understood you correctly, by doing this you will end up with 2 DBMultiASM_MADdash_PIN_v2.0's on each ...
Dashboard EAX
-
aeseme replied Feb 16, 2016PINS direction is 100% based on PINS own settings. I cannot get what you mean with all these statements.
Dashboard EAX
-
aeseme replied Feb 16, 2016Everything seems fine, all MADdash's with their corresponding PIN enabled as per their labels at their top left corner. PINS are not showing anything just because no alerts are being generated by MADdash (see the ALTERS labels in each MADdash chart, ...
Dashboard EAX
-
aeseme replied Feb 16, 2016It is just like you said some posts above.... coding, debugging, testing, tuning, etc... and the day has only 24 hours... Users committed to the idea and ready to cooperate to the extent possible makes the difference (IMHO).
Dashboard TZ
-
aeseme replied Feb 16, 2016You have "One order per candle bar" as a Hold[H] filter scope and M15 as candle time-frame. By looking at these orders times: 2016.02.16 14:43:17 (Opened in M15 candle bar from 2016.02.16 14:30:00 to 2016.02.16 14:44:59) 2016.02.16 14:48:46 (Opened ...
Dashboard EAX
-
aeseme replied Feb 16, 2016Users have a very important role on this
This would be like adding strong and weak levels to the actual [BQ] (Base|Quote) filter/trigger that is currently based in currencies opposite direction only. I will have that in mind but no ...Dashboard EAX
-
aeseme replied Feb 16, 2016I see that you have hidden some modules. Chances are that you have any of them also enabled for triggering/filtering? Please check it out if you have any of the hidden modules still enabled in preferences, this can be the cause of that long trigger ...
Dashboard EAX
-
aeseme replied Feb 16, 2016Latest update: (A fresh install requires the current revision bundle here) !! Fixed an issue found in the new and experimental filter on previous candle bar direction check that won't properly update in some cases. ► DBMultiASMdevX006f2.update.zip ...
Dashboard Trading