This is quite odd... have not had that behavior (at least not noticed it), by the way, running the update012.8 of Dec 20, 2016 5:59am? EDIT: JFTR, I've just done a quick test (stop after 1 profitable / 1 losing) and it is doing as expected on my ...

Dashboard EAX

I wish to everyone celebrating these days a happy holidays PS: I will try to sort and settle belated nor delayed stuff soon...

Dashboard EAX

Congratulations on your new thread Sam2x ........

My Eax Dash Pins

I don't recall making changes there lately, however I'll double-check just in case...

Dashboard EAX

It's kind of a "best practices" advice, setting something up at start, means clearing it at end, leaving no traces behind (unless otherwise specified). It doesn't mean that all Global Variables should be cleared, just those corresponding to the PIN ...

Dashboard EAX

Indeed, if levels are close enough, you could end with no room to place orders...

Dashboard EAX

Test-drive update of BRdash PIN: DBMASMEAXPIN_BRdash_v004b (20170130): + Hold state (per time-frame) based on current bar range. A bar has to move a certain amount of Pips (default to 1.0) to join the party. ► ...

Dashboard EAX

In your use case (only avoid around levels), you don't need to enable any of the LongsTZ/ShortsTZ or you'll be also restricted to their scopes.

Dashboard EAX

Quite odd... very same settings here... What are we missing? image image I only have that kind of issue if I set targets too close to spread, but it doesn't looks like your case...

Dashboard EAX

Is there anything in the Experts tab log regarding this? (further tests are showing as OK on my end) Try this: image From Changelog:

Dashboard EAX

I agree that we already have something to play with on that regard, see my following reply shortly after the previous one: OTOH, a benefit I can think off right now would be a better handling of the entry and exit states in the very same PIN slot... ...

Commercial talk with HP

In the mean time we have the exit scopes to play with (opposite,absent and lost signal), that can be optimized by i.e. defining two PIN ID's per PIN, one for entry and another one for exit, and then setting the PIN slot of the exit ID as exit on ...

Dashboard EAX

Now I got what you mean (and by re-reading your previous post it seems so obvious that I cannot get why I didn't got it before LOL). Indeed, the current PIN states are very elementary right now and are already deserving some improvements, and that's ...

Dashboard EAX

I hope so.. let's see how it does.. I expect to release a testdrive before next DO... I made some quick tests and both are properly working on my end.... perhaps if you could provide some additional details? It looks like I missed that one, and BTW, ...

Dashboard EAX

About adding more PINS blocks to the very same EAX... I'm not sure of its benefits.... in fact, I see the current block with 6 slots as more than enough for well designed PINS... Perhaps... instead of more PINS blocks, what you need is a sort of ...

Dashboard EAX

Just to clarify, it's most an FF policy... where commercial stuff must go in the Commercial Content section, and while those PINS aren't commercial, they use commercial products to collect data from, and can be understood as disguised ...

Dashboard EAX

I think that I finally have some good news regarding this annoying weakness, and I'll try to upload an update early next week to see how it does.... After evaluating some time based options (fixed to percentage of bar time, etc), I ended up finding ...

Dashboard EAX

I'll have this corrected in the next revision update...

Dashboard EAX

As long as local (FF) and origin (SHF) policies are being respected, I see no problem on that

Dashboard EAX

It seems that your trades were open by PINS (3,4,5), so It would be nice to know what PINS (and their presets) were you using there in order to have the full picture...

Dashboard EAX