Posts made by fxDreema

Variables explained at 0:20 - 1:25 in https://www.youtube.com/watch?v=aeoGGabJhAQ

At the moment I work for a new thing that will probably help many people with debugging the project, and Library Studio is with lower priority. I can't give you a promise when I will take care of it, also because this thing is still not really clear in my mind

Something like this? http://fxdreema.com/shared/CJjPtOxyb
This Signals block is a little bit hard to explain, but you can see it's description (hold your mouse over it in the list)

Crossovers are also hard to explain in simple words, but you can see here: http://fxdreema.com/documentation/proje ... er%20works

By the way I could move this topic to the first sub forum on the top.

Because you want to check MAs for a period of 5 minutes and to take action at the end of that period, you have to use variable to store the temporary state. Let's say value "true" of that variable means to close all trades and "false" means to do nothing. At the beginning of the period the value must be "false", in the middle of the period it can become "true" (depending on MAs) and at the end of the perood you will ask if it is "true" or "false". If it is "true", you will close trades and modify the variable back to "false". Then the new period begins and the same procedure starts again...

I just added negative output of "Once per minutes" because it was not there and I think it will be needed, but my mind is almost asleep right now, so I will continue tomorrow... meanwhile you can try something.

Stupid block, you can't, but you can try with "Custom MQL4 code" (the very last block of all) in these ways:

Print("message to print");
Print("My variable is "+variableName);
Print("My variable is ",variableName);

There is a slight difference when you separate members with "+" and ",". Using "+" makes numbers to be printed with more digits after the point, while "," makes them to look short and friendly.

By the way I lied. "Print message" can be used as well with a trick - you have to add "+ or ", at the beginning and +" or ," at the end

This block "Once per minutes", if executed and passed now, can pass again after 20 minutes or more. If you access it after 30 minutes, it will pass and will start to count new 20 minutes from that time. This logic can lead to irregular periods, shifting of the next 20-minutes period, because it's all depending on when the block is executed (and passed).
What do you need - regular periods (like Once per bar) or not?

There is a category named "Flags" and these blocks are very similar to using normal variables in the project. The idea is... let's say you have variable named "CanDoIt" with value "true". If the variable is "true", you can go to close all trades, but if it is "false", you can't. And you can make it "true" or "false" anytime, anywhere.

This is hard coded, I didn't add option to change it. But now I doubled it as well, so I hope it will work. Now it is 1 MB.

Try it now.

I think that in the moment fxDreema is not capable to connect trade to a certain pending order in this way. I think this requires a list (array) with relationships between trades and orders, for example - when Trade#5 is closed, also close Order#6.

If you define global variable for some block, it will be included at the top of the EA automatically, and it will be available for all the blocks, similar to Constants and Variables. But you have to remember it's name. Just write it's name somewhere, like it is a number. Instead of "10" -> "ResultPipValue". If this is what you ask for...

I think I must rewrite many things
I got your idea, it is to make possible for the custom block to induct something into the project. I actually started something like this, but I don't like the way I made it, so it is still not included I just don't feel "That's it!" sensation.
I must say that I can't promise you some time to make new things in Library Studio, basically because it really needs to be rewritten and some things to be optimized. But if there are 3 things I think about all the time, they are:

• Damn, I must update this documentation...
• How to make debugging process faster and easier in MT
• How to increase flexibiliy of blocks - working with variables, custom code, strong and good API...

Now 5 pips works sometimes, 6 pips - not at all

TeamViewer?

http://fxdreema.com/shared/SVoHH5JFb

Guys, I really want to know how do you work with indicators that changes behaviour multiple times per bar. Most of custom indicators are like this, are they made to be used with at least 1 bar shift?

I think I don't understand you

1. What is the minimum SL size in pips that you can put to a trade? The real one, not what the broker says.
2. If you say that you are using 5 pips, but sometimes you get 50 pips, is the similar thing happens when you are using 6 pips -> 60 pips over there?
3. What do you mean by "emergency SL"? In fxDreema this term is used only when Virtual stops are used. Do you work with Virtual stops?
4. Backtest or demo?

for slippage troubles I think I can't help much, because I am not an active trader, not a scalper, I never cared about this parameter, and I can admit that I don't get how slippage affects trading

Global variables can be used in every MQL function. Well, there is a small problem when a local variable with the same name is defined inside the function - in this case you work with the local one, global variable remains untouched.

Any MQL global variable name can be used in Condition, in "Value (Numeric)" if it is "double" or "int" or "bool", for example.

I understand that working with variables is easy thing in MQL and not so easy in fxDreema, so I'm still searching for better ways to do it. In one hand, those who don't understand programming must be able to get it, and in the other hand programmers must have good and flexible control. In one hand a variable is something so small that does not deserve a whole block dedicated only for it, and in the other hand it can be one of the most important things in the project.

I'm a little bit stuck in this zone, so I'm probably not able to get a good idea of how to work with variables anymore. That's why I asked you what is your expectation of how things should be. What do you want to define, where do you want to define it, and then how do you want to use it in the same block or in others? I mean, visually.

Ready to test => http://fxdreema.com/shared/dOqT3hwEd
Take a look at the logs. This method seems to be a little bit complex, so I added special Print messages for it.
And here is how it look in the code: http://fxdreema.com/documentation/colle ... ynamiclots
This is the function that returns lot size depending on the MM method and input parameters. "value" is unit size (lot size), "sl" is delta (I will rename "sl" later...)

Global variable defined in block is automatically included in the final EA, but it is not included to Constants or Variables. You can see where it is placed if you open the .mq4 file, it's somewhere on the top where all global variables are

I never tried this, but for the trading blocks there is a gray output that is active in case of error (in this situation the orange one is not active), so if you connect it to the input of the same block, it should go into cycle until it finally opens the trade... somewhere.

The process of opening a pending order to trade happens on the server, I don't know if there is a way for the EA to know that something wrong happened. I mean, when the EA tells the server to trade, it waits for an answer. But in this case the EA is sitting there and doing something else.

No, no... I mean... you start the EA, it trades and everything is ok, when suddenly the PC crashes or something like that. When you start the EA again, initial balance is different, delta calculations are lost, and you have to start clear. Is that ok?

Yes, this is valid for other MMs as well, but they are somehow easily restartable. Martingale for example, it doubles the lot of the last bad trade, and whenever you start the EA, you know everything for the last trade. This one (Ryan James method) looks to me that when started, there is no way back. But the easiest thing for me is to make it in a way that after MT4 restart, everything starts again

Aah,.. well, in case of projects with use of optimization parameters, I can't help much. I see 100 pips, you tell that you use 5 pips, but who knows what MT4 uses, because MT4 writes temporary .ini file to save the last version of input parameters.

5 pips -> 50 pips can be caused because of incorrect calculations inside the EA. Using point format 0.001 instead of 0.0001. In this case, if you setup the EA for 6 pips, it should place 60 pips sometimes (10 times larger). Is that happen? Because if not, then the problem comes from the "TCF CBBP EA Tony 1.2.ini" file.