Posts made by fxDreema

Fix something, break another thing.... fixed and reuploaded.

Do you understand "on Chart" event? This event is fired when there is some chart event, and there are many different chart events - you clicked on the chart, you created or deleted new object, you drag an object or just moving your mouse. Any of these events must be filtered - the first thing to do under "on Chart" is to detect the event type, then do something else.

Now what you have is something that will most probably put the CPU at 100% when you move the mouse over the chart.

Otherwise I don't think that it's a good idea to run blocks in one event from another event, but there is a block named "Run blocks"... if it appears to you

Condition -> Market properties. There are things like "Digits count" and "Point size" and they depend on the market. As you know, fxDreema has some options to play with the point format, which basically makes the EA to believe that these values (Digits count and Point size) are the ones you specified, not the original ones. That's why you will find select menu with 2 options - Original and Customized.

It is not impossible to draw the average current profit, the little problem is that this value cannot be get from the tools in "Condition". It can be calculated using few blocks and variables, or with a custom block.

These: http://prntscr.com/4wg2n2 are options for the name of the object. By default text object names looks like this: fxd_text_%some numbers here% but you can define your own object name in "Draw Text" - look at the third option from the top.

I have no problems with it: http://prntscr.com/4wfvw9
The value looks weird, but all the dots are there, which means that the indicator is successfully added. Do you use the local version? If yes, make sure the indicator is added like this: http://prntscr.com/4wfx93

How is it now?

Wow, now this looks bad. This is PHP warning, not MQL4 or MQL5. I will reupload this build after a while...

Never expect from me to know what is in your mind. Every time you (anyone) show me some project, it's something new for me. I don't know what you want to do, especially when you don't tell me!

"ones per object" is not properly used anyway.

You can try something like "+50pips". The word "pips" is then converted to something that depends on the market and the point settings of the EA. Also, I think it can be done with "Formula" -> Value -> Pips (as price fraction)

This looks beautiful, but I will suggest to remove those AND blocks and connect conditions one after another. Now each one is checked. If they are one after another and the first one is false, the next one will not be checked, which means that the EA will be backtested much faster. Also, you will be able to put some "Draw Arrow" after some of the conditions and see if it passes, find where the positive signals ends, and easily find bad condition block that way.

Aaah, I forgot that there is a block like this. It seems that the input parameters are strings, so a little trick can be used. Try this: ""+Symbol()+""

It should work fine, this is nothing fatal

Maybe something went wrong when adding it to fxDreema, but I will check that later. I added it for you on the web fxDreema. I didn't tested it, but it should work... I can see 7 inputs and 7 buffers, everything looks normal. Well, one of the inputs has fancy datatype, maybe this is what creates the importing problem. Otherwise you are doing it good by using "Indicator tester" blocks.

Ummm what?

In this project you have 2 variabled (1 is not used) already set with price valued. The one that is used is not modified at all, it stays 1.267 forever. Then, that variable is used in the condition before closing trades, and also as a price level for a horizontal line. As expected, the horizontal line stays at this level because the variable is nowhere updated.

Maybe you want to read the price value from the horizontal line? Or move the line sometimes. I don't see nothing from both cases, but it is possible.
To move the line up-down, modify that variable somewhere. Or move it manually.
To read it's price value, one of these situations - the two blocks on the left or the single block on the right: https://fxdreema.com/shared/VAIPQGHHd

Well, things are getting complex when searching for something is involved. As I explained, there are 2 ways of working with this:

1. Not searching at all, but using some variables to set some values when certain events happen and then check those variables before doing something. This is intuitive and fast (because you don't search for something in the history), but when you close the EA - it's all gone (sometimes you may prefer this).
2. Searching the past data for whatever you need. But there are not many blocks for this. Those that are available are pretty simple, for example "No trade is running" is a block that searches for a trade that is currently running.

There is no block to search for a trade that was closed today on TP, but here is something alternative: https://fxdreema.com/shared/IesEuQiyd The only thing is... if you don't get how variables work, then I think you will not get this as well

For the first trade I will suggest to do it with "Once a day" connected after the main conditions. The second output of this block will be active otherwise (in any other moment after the first and only pass for the day), so the second trade can be created from there. You can use some Variable to set it to 1 when the blue arrow appears, and then check that variable before entering the second trade. The variable must be reset after another "Once a day" block in order to start with value 0 for the day, or after the second block is created if you don't want more trades for the day.

This was the "soft" method, which will work in backtest and on live, but the problem is that the variables are reset when the EA is reloaded, and the "Once a day" block as well, so everything will start again if you reload the EA. To make things more "hard" and ea-reload-proof, then times must be used instead of variables, and things are going to be a little bit complex. You will need to check the Open (or Close) time of the last closed trade and compare that time with the time of 00:00 for the current trade before entering new one. Then you will need to get the time when the blue arrow was appeared and also compare it to the time of 00:00... well, getting the time of the arrow is not really easy to do in fxDreema, it's probably easier to make it in plain code.

Is it working on your PC in this offline chart, or you want to say that regular EA is working on your PC, which is expected?

Then I have to try this again, but these renkos... do you have easy to set up renko?

Go to Options -> Project options and play with these: http://prntscr.com/4vpipo

What is specific in Sell 1 and Sell 5? It looks that the conditions for Sell 5 are quite different.

With the same block that is used to create the line. Once a line is created, it can then be modified(updated). When and how often - depends on the two options at the top. Play with "Draw Line" at a separate temporary project to see how it's working.