Posts made by fxDreema

I think it works now. There was a problem with one data type

It works now. Thank you for reporting this

There is also easy way to check the lot size of the latest closed trade, if this can be used: https://fxdreema.com/shared/RxENL906c

But when do you want to stop "Sell now". And I don't understand why, because obviously this is the only block able to make a trade over there. Maybe stop it for a while...

I don't know what to suggest. There is "Once per trades" (I neve really used it), there is a way to disable some blocks and then enable them, there are endless ways to prevent some block from running (putting conditions and filters above it).

When profit is reached... what profit? There are different profits. The profit of a single trade. The current unrealized profit (Equity-Balance). The profit of the last hour. The profit of the last 10 trades. The profit of the last 24 hours. The profit of today (until 00:00). That's why I said that it depends.

Well, as you can see in this forum people always ask me questions. It's more like a place for support, the communication is mostly between me and all the people. Very rarely someone answers to the question of another person. What can I say

"Sell now" is designed to always create a trade when it runs. MM settings only change the lot size, but not the fact that the block is gonna create some trade even if the requested lot size is 0.

So, detect that the profit is reached and don't run "Sell now". This is the approach, but how to do it'... it depends really. Maybe you can detect consecutive profits or losses, there are blocks like "Check consecutive profits" and "Check consecutive losses". It depends

Put "Delay" where you want to pause. I am doing this sometimes when I want to pause somewhere.

If you don't use stops and blocks to stop a trade and the EA is working live, then probably you also have another EA working in background that does that. I have no reports for problems in these blocks. I updated some other stuff, but not these functions, I just don't expect something to be wrong with Condition or Close Trades

Not working because of compile error or logically? Because I was updating some stuff and some compile errors appeared, but these are also easy to spot and fix. If there is something else, I must investigate

It was my fault, it looks that I missed something when I did some updates today. Sorry about that

My fault. I was doing some updates today and I missed smething

I will suggest to reorder blocks a little bit. There is no reason to have different "Close trades" at all places. Only 2 are enough - one for the Buy side and one for the Sell side.

Can you detect from which closing group was that Sell closed, so we can focus on the problematic one? I mean, there are 5 ways to close that Sell, but one of them was closing it... which one? To understand this, disable 4 of them and leave 1 enabled. Do this for each group and in 1-2 minutes the answer will appear

Also always expect weird looking results when you are working with the current candle. Because you know, it's values are temporary and at the end of the test on the chart you can only see the latest state of each candle. Work with "Visual mode" on the tester to catch those in-candle moments. And here is the moment to suggest little trick - try that block named "Delay" and for it turn on the delay for visualization. While the visualization is running you can use this block to pause at certain moments and observe what is going on more carefully.

Sorry, I was doing some updates. It should be ok now. But if you find that something does not work as expected, report it to me as well

There is also another way, to work with functions and local static variables in them. I'm actually using this way for the system blocks and functions I created. So you can have a function that contain local static variable => by calling the function you can get or modify that variable, and doing other stuff as well.

In the project when somewhere you write some function call, for example "MyFunction()", then this will refer to your custom function. Or, if such does not exists, to a system function (created by me).... but I don't recommend to anyone to use my functions, because I often change them.

Hopefully it will work. There are few scenarios:

• to create the variable with the block itself. I mentioned this additional field where things like global variables and imports can be defined. When generating the EA, the generator gets the information of all blocks that are used and decides what global variables to put.
• to create the Variable in the project and somehow to put it into the custom block.

The issue here is that I sometimes experiment with Constants and Variables. Right now they they are little complicated, they are two static classes - c:: and v:: - and these classes contain only variables. The idea is to separate Variables which are created in the fxDreema project with the real global variables. If you use a custom block and you define global variable "abc" and you use this block in a project where in Variables you have another variable with name "abc", both will be different things.

http://prntscr.com/a3xeo1

http://i.imgur.com/dysvgST.png

As you can see, both variables even have different data type.

I tested this now and of course there are no compile errors, because Variables and global variables in the custom block are different things. The question is what will happen if you write the word "abc" somewhere in the blocks... And what happens is that either "abc" or "v::abc" will be used, depending on what exists. If both exists, "v::abc" is used.

In short, do it in the first way - define the variable in the bottom of the custom blocks, then just use it in the project, do not define that as Variable in the project.

I don't know for MQL4/MQL5 function to do that

It's easy to get the highest price in 5 candles, the highest high. But the amplitude in all highs... The lowest high is missing here, I think there is no special place in fxDreema to get exactly that. Otherwise it's easy to check if candle 0 is 6 pips from candle 1. See the description for "Condition" and at the bottom there is something for "Adjust"

Blocks does not have outputs. I mean, in the code they are functions, but they does not return, they only call other functions.

You know, I think Ihave to see what can I do in the blocks like "For each Object" so an object from other subwindows or charts can be read.

It's not very intuitive to export global variales like that. There is an option to define global variable in the smaller field below the code, but I don't remember how this fits with Variables in the project. The thing is that when in any block you write the name of a Variable, this name is then prepended with v::, because Variables are coming from a class with name v. It's weird.

Isn't there a way to have that object on the current chart, so at least it's description can be get? Then it's not that hard to use StringSubstr in any block.

I think I fixed the problem. But this block is complicated and it's possible that this fix can break something else. Tell me if you find something that doesn't work as expected.

Search for blocks like "Time Bomb Up" and "Time Bomb Down". I made these long time ago, but I think they still work. But note that doing this in the Tester can only lead to wrong results.

Try "Bucked of Closed Trades" and then in "Condition" you will find the "Bucket... " option and inside you can select Lots.