Posts made by jstap

@talalkhan A cross happens on a candle, > happens after a cross and stays like it until the opposite cross occurs.

@barsa1211 Most things on FX are simple as long as logic is correct.

@thedisliked This is when things start to get complicated, you could have something like candle is above BB, under MA crosses BB. Otherwise you need to use variables to record when a cross happens, reset this variable once no longer valid so, when the next cross happens it works like a trigger so trade activates, then likely reset the variable so conditions can happen again.

@haikel Put a stop on with the buy/sell block, use the same pips as trail. Possible that stop can't be moved if there's not 1 to start with.

@haikel Put a shared link here and ask specific question for what you can't achieve, I am struggling to see what you want to do.

@talalkhan

@santhoshabraham Like this.

@fideld003 Miros zigzag advanced contains all you need to do this, download the MQ file, import back into FX so you can add/amend. You can add mote points like l4, l5, l6 etc but things may start to not work correctly, you can also get this from a standard condition block but only Miros code will give you whether the current leg is on the way UP or DN.

@barsa1211 In the picture you will see how to check if price is above MA but below MA + 100.

@haikel This SL will trail by PSAR, I have used this many times and never had a problem, if you want to trail by price then you need to use the blue trail block. You can use condition blocks to activate/deactivate different trails when required.

@ontradingx I am not sure how to do this but you could create constants to select the corner and X/Y pixels from inputs.

@andrewfrank https://fxdreema.com/forum/topic/12802/atr-pips, is handy if pips are required. In a formula block take the ma price and + or- ATR put into a variable and you'll have the price level to reference, in your buy/sell tree put a condition of market properties=<> variable, this will allow the blocks beneath to activate but only once condition is true.

@thedisliked You had nearly done it, candle ID1 means cross happened on the previous candle

@haikel In the trail block you can set a start point, use the same number to use the same parameter, you can also use a condition block above to only alloe trail to start once condition is met.

@haikel You can just check previous candle level is <> recent, quite rudimentary but could work if fits your requirements, if you check the distance on different MA's then when there close range is likely unless it is crossing or changing. In HERE is something I was doing recently, there should be enough to find all you need.

@nopthankyou Your welcome

@talalkhan Yes yellow is just for if not condition.

@talalkhan The modify variables are now correct, if <0 is what you want to set variable to false then all is logicily correct.

@pipsmagnet In HERE is a few options to create an EA, you should see all you need.

@talalkhan But it is a bool variable!