Posts made by drayzen

Hi @roar ,
Thanks so much for this, incredibly useful!
I'm sure I'll use this for many projects...
I had an idea of the blocks required but couldn't get it sorted in my head how to connect them.
I never would have thought about the limiter either, nice how it's path is also a double redundancy.

Though does the value in Block 7 need to be '+1'?
...or does that need to be done by the Adjust field?
Do the Condition blocks 2 & 3 looking at the candles also need to be '+1' so they head backwards through the candles?

I'll need to increment the start points of everything anyway because my trade indicator appears at ID1.

cheers!

Hi @Ali-1 ,
Have a look at "Add to Volume (every 10 pips)" here to get you started:
https://fxdreema.com/examples#Loop-(For each...)
(Click image for details)

So have you guys been complaining about it not working on the home page...?
A LOT of time would have been saved if you'd said so.
If you are going to report problems you need to be more specific than "It doesn't work."
Everyone here would expect you were having problems in the Builder page, the homepage is just a preview, not for doing actual systems.

Hi @roar & @miro1360 ,
I'm hoping one of you guys can help me with this one as you seem to be the resident Variable experts, which I'm sure will be needed to solve this one.

I'm wanting to find the recent high, but only when both preceding candles have highs that are <= their following candle.
I then need to get the value of that high to set SL at.

I thought I could do it with many many pairs of conditions that work back through the candles then put out that candle number to a variable, but I'm sure there must be a more elegant way to get the job done...

cheers!

Hi @eray-dursun ,
You need to click on the numbers on the left of each block and make them in sequence.
https://fxdreema.com/tutorial/builder/builder-basic-rules

You currently have: 10 > 8 > 3 > ? > 22 > 1

Update: Incorrect, see fxDreema post below.

Hi @eray-dursun ,
What @ekanters showed you is correct, Condition > Once per bar > Buy/Sell.
This is basically limiting your Condition result so that it can only complete once for each candle.
Without this it would perform the assigned trade action on every tick.

Note that if you click on the '?' next to each block title in the menu it will open a detailed description of it's function, and there's often useful tips in there.

There are some examples of it here: https://fxdreema.com/examples#Tips-and Tricks
Be sure to take note of what happens if you put it before your Condition(s), it gets activated on the first tick after Open of each candle and if your condition doesn't pass with that first tick then nothing can happen until the first tick within the next candle.
This caught me out initially, generally it's best to put it just before your trade action to have it behave in a sensible and useful way.

tip: Use an @ to tag people, I only found this by chance...

Hi @fxDreema ,
For the attached project that uses </> in Condition blocks, if I open 2+ block details they display the Cross width option.

Changing it between < or > does not remove the Cross width option.
The only way I can see it without the Cross width option is to open only a single block's details.

I'm thinking possibly because the Custom Indicator has no Inputs, I'm only referencing it's Buffers to use it.
EasyTrend.mq4
EasyTrend LITE.ex4

@eklonsousa ,
For me it's pretty simple, we're creating tools to work with our finances, so why take a chance with something that might not work correctly.
My initial Firefox issue was with importing a custom indicator.
Then after reading this in the fxDreema Features documentation I decided to only use it with Chrome.
"- fxDreema works best with Chrome and there is a plugin for easy downloads for Chrome as well. Firefox and Opera are also ok, only God knows about Internet Explorer..."

While I've been a long time Firefox user, ... only after the death of Opera 12.xx ;( ... and continue to be for my daily usage, there are times when you find a specific use case like this and have to use what's appropriate and not try to force something that's just never going to work 100% correctly.

@mawas70 ,
What do you mean by 'desktop version' it's online only... ?:\

Some interesting things in the recent AU federal budget.
My govt. is making cash transactions >AUD$10k illegal after 1st July 2019.
In the same budget they have allocated AUD$700k for blockchain research.

I won't be at all surprised if in the next few years there's an official government blockchain version of the AUD...
Once that happens it's only a matter of time before the other Five Eyes members will also have their own.

That's why I'm mining Monero. Once all the governments have their own cryptocurrency it will only be the truly anonymous ones that will retain their value and continue to grow...

Hi @gsmtricks ,
Would Trace do what you're after?
https://fxdreema.com/examples#Tips-and Tricks

Hi @jtex555 ,
I actually just used the Indicator falls within limits block for the first time and it sounds like what you're after.
https://fxdreema.com/shared/SwJ2mrNPc
In this example the Condition block is for C0 and the Indicator falls within limits is for C1+n.
You can even specify a number of candles in the range that can be out of your limits.

@eray-dursun yes, I was editing and compiling to .ex5 only a few hours ago.

@eray-dursun ,
What was your solution? ...sharing is caring

Hi @jtex555 ,
Sorry, I'm not sure if you're meaning the Stoch lines cross one another, or both cross something else.

• If crossing one another you only need x1 of the first Condition blocks where you specify Signal x>/x< Main then in the More Settings section specify the Timeframe for each side, or only one if you prefer...
  You might like to link your Timeframe settings as Constants or Variables for testing other timeframes.
  Though the variable inputs in MT4/5 are a little cumbersome (https://fxdreema.com/forum/topic/5289/timeframe-as-input)
• If you're checking if both Main and Signal have crossed something else, then you'll need to use x2 Condition blocks, one for each.
  For all blocks, the yellow output is the FALSE condition you mention if you need to direct processing flow somewhere.
  Note that you'd only use the yellow outputs if you actually have something you want to do if your conditions aren't met.

Hi @olmo ,
Sorry, not really. I didn't mention above, but I'd assume you've already tried restarting your computer.
If you haven't made any other changes since it was working like adding browser plugins etc..?
Otherwise, just have to wait for @fxDreema to advise...

Hi @eray-dursun ,
Knok knock... ;D

Are you still having problems, it's working ok for me...

Couple of things I'd suggest:

1. If you aren't using Chrome (https://www.google.com/chrome/) switch to it.
   I normally use Firefox but came across a few quirks using it with fxDreema.
   This is developed on Chrome so best to stick with that.
   (If you're using IE/Edge go give yourself a slap!)

2. If you're already using Chrome, I came across this cache clearing trick recently.
   a) Press F12 and you'll see the DevTools panel appear.
   b) With the DevTools Panel open, Right-Click on the Reload button and you'll see a few more aggressive page Reload options.

   

   https://superuser.com/questions/220179/how-can-i-do-a-cache-refresh-in-google-chrome

Should this work? (Virtual Stops = TRUE)

It keeps putting the TP on the ASK line instead of higher.
I also tried *5000 pips, but still didn't work.

Also, should I be able to reference *n pips from a 'string' Constant?

Can the Spread Meter output be referenced?

ok, so it's function is essentially 'Cross on any of n Candles'.
... still trying to think of anything I would want that for, it is obscure.

So if I'm understanding you this means a setting of 4 = C3 OR C2 OR C1 OR C0 = TRUE
I could actually see an inverse use for this to filter out low volume "noise" crosses by it returning FALSE for n > C0, while still returning TRUE for only C0 = x>/x<.
e.g. Cross Width (Filter) = 4
C1 OR C0 = FALSE
C3 OR C2 OR C1 OR C0 = FALSE
C0 = TRUE
But again, it's would still be a bit quirky, I'm guessing finding a separate filter method would be more efficient, or could a Cross Width (Filter) = 20+ work efficiently?

Forget all that, just found the Indicator moves within limits block which covers that application.

Yep, you were right, watched it back in slow motion and they did briefly cross.
I made a .gif of it so I could see exactly what happened: i_Trend Cross.gif
(There's also something a bit dodgy near the end where the Open price of the last bar changes!!!)
btw, I just found this .gif recorder which is a really nice little app: screentogif.com

Should that be triggering given I'm using x< / x> ?
Is the Cross Width setting the point distance between the two indicator values? i.e. (-0.0007 - -0.0008 = 0.0001)
... though I did already try 4 and it didn't correct it and the trade triggered when the values were both -0.0008, hrm... ?:
Maybe does this need support for negative numbers added?

If I use 'Candle ID 1' that means that it won't get any false signals like that correct?
Are there any other ways to work around "temporary" crosses?

• I was having another read of the Crossover documentation and some of the example blocks are giving error:
  TypeError: Cannot read property 'cross_width' of undefined

cheers, d