Commercial talk with HP

Quoting vinvlad

Disliked

Hi Hotpotato. Tests of the last version EAX_DWMRangesv1.02 are very different from the tests of the previous version (the name of Pin is the same EAX_DWMRangesv1.02 ). Is it possible to put the version 1.02 with the settings as shown to test both settings at the same time? {image}

Ignored

Quoting Hotpotato

Disliked

{quote} I'll do my best but what don't you like about the latest version ?

Ignored

Quoting Hotpotato

Disliked

There are a couple of reasons why developers put expiry dates in there code. The first is a simple one and that is ...

Ignored

Quoting Hotpotato

Disliked

Aeseme Starting outside market hours with open trades and EAX seems to want to close them on a lost pin (or other signal). Can't close of course but EAX keeps trying up to the extend that even the screen isn't updated any further. {image}

Ignored

Quote

Disliked

Just a shocker... whilst trying to scalp using your STOCHASTIC PIN alone on M5

Quoting Hotpotato

Disliked

Recompiled without BDM stuff in it. {file} {file} {file} {file} {file} {file} {file} {file} {file} {file}

Ignored

Quoting jenbols

Disliked

{quote} Im Aware Hp cannot answer on other threads, so I posted here Is anyone still using cDash2Eax as Pin? Also does it do only Buys like the EAX_DWMRangesv1.01 ? I know that the DwmRanges v1.02 is versatile and can open orders both ways even though does not trade often. Tried using the version before sep 2016 (cDash2Eax) 7kb http://www.forexfactory.com/showthre...98#post9137898 Now Iam using the cDash2EAX.ex4 posted in post...

Ignored

Quoting Hotpotato

Disliked

{quote} CsDsah and cDash2EAX go on a different chart (than EAX) for every cDash you use. Important for cDash2EAX are the last two parameters, they have to match the CsDash settings exactly.

Ignored

Quoting proctor

Disliked

hey hp, didnt see that you have now here your little corner, of course it would be better when you where in the origin eax thread but this way is also ok, i mean better then completely blocked or something..... so nice to see you back man

Ignored

Quoting Hotpotato

Disliked

@danapster (if you ever pass by here) {quote} The shocker is that you have 3.28 lots open for $46 profit...... The risk is enormous.

Ignored

Quoting Hotpotato

Disliked

DWMRangeas1.02 over the last days. I changed the settings to not add trades on retracements but on continuations so linear adds. Further the takeprofit was set to halfway, stoploss at 1/4, trailing .............. {image}

Ignored

Quoting jenbols

Disliked

{quote} Ah well thanx for the update... that clarifies a bit more the Dwm1.02 functions... I had "full take profit", which basically means = too greedy trail step 1/8 which means = Fear .. Will change something and still keep the old settings to see some differences, but that will be from Monday of course. Take care

Ignored

Quoting Hotpotato

Disliked

There are a couple of reasons why developers put expiry dates in there code. The first is a simple one and that is because i use my BDM header and tools in the code and there is indeed an expiry date in there due to the testing lab releases. Second it will make a fool of the people who are trying to sell what you have build (and that happens more than you think). Third it will force people to always use the latest version so you as a coder do not have to maintain multiple version of the indicator or EA. I think that it is not more than fair to the...

Ignored

Quote

Disliked

Indeed, the current PIN states are very elementary right now and are already deserving some improvements, and that's not a bad one, however, at least at first glance IMHO a close status would require 3 states, Close Short(s), Close Long(s) and Close Any/All... or I'm overthinking it perhaps?

Quoting Hotpotato

Disliked

Quoting aeseme

Disliked

Indeed, the current PIN states are very elementary right now and are already deserving some improvements, and that's not a bad one, however, at least at first glance IMHO a close status would require 3 states, Close Short(s), Close Long(s) and Close Any/All... or I'm overthinking it perhaps?

Ignored

I don not this was a very well thought trough proposal.

A box (pin) can have three states none-buy-sell what will be the forth state ?
Who will be responsible for monitoring the close, the pin setter or EAX ?
Don't think it should be EAX because than you make EAX responsible for managing the pin.
If it is the pin setter (indicator) the pin setter should maintain and monitor trades.

I really do not see any advantages over the current loss of signal, opposite signal etc posibilities.

I would leave this until someone can give an example in...

Ignored

Quoting aeseme

Disliked

In the mean time we have the exit scopes to play with (opposite,absent and lost signal), that can be optimionezed 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 opposite signal...

Ignored