Posts made by fxDreema

Hello,

".ex4" is a file extension. ".ex4" files are those that MT4 uses to run the strategy. Those are files compiled from ".mq4" source code files.

In MT4, expert advisors are used basically to trade, that's the idea. Indicators are used to draw something.
Well, expert advisors can draw objects if needed, for the idea to help you to understand what's happen with trades and orders... with trading. There is a block named "Draw arrow" that can draw simple arrow when it is executed, so you can use it if you want.

Just to mention, if you want to make indicator of indicator, maybe it is not the best way to make expert advisor for this. Instead, make another version of that indicator, new custom indicator. Unfortunately I can't help here, but this is what it's normal to do in this situation

Yes, of course. Just made it negative for Sell type. Thank you for pointing this and for being able to understand some problem in detail.

Via "Variables >>" link, but now I don't like this way so much. My initial idea was to be able to get and use parameters from blocks, combine them with other variables or constants and set the result of these calculations into the variable.
I'm still thinking for the best way to work with variables.

I think you don't need variables. There is another "problem" with Fractals - for the current candle this indicator always returns 0. For the previous - the same story. Fractals shows up on the 2'nd candle, so you can set "Candle ID" to 2 in order to get value from Fractals.

Variables (defined from Options -> Set Variables) cannot be updated in this way... still. I should create a special block for that probably, but now Variables are updated in a different way (via "Variables >>").

Formula itself creates a new global variable (with MQL4 scope), so you can name it FRUP ("Result:" field) and use it later.

No, no, no...

Global Variables are something very special in MetaTrader itself. Hit "F3" and you will see a window named "Global Variables" with variables which are global for all EA's running into MetaTrader now. They are defined in MQL4 with a special functions, and they are NOT global variables in MQL4.

There are global variables in MQL4 as well, and they exists in fxDreema in some ways:

1. When you hit the checkbox for some parameter to become an input parameter for quick optimization in MT4, this creates a global variable at the top of MQL4 code.
2. Using "Formula" block. This automatically creates a global variable with the same name as it is written in Result fileld. The result of Formula block is actually saved in a normal global variable in MQL4. Again, defined at the top of the file.
3. Constants (Options -> Set Constants). Again, global variables. In addition with automatic "extern" keyword to make them input parameters in MT4.
4. Variables (Options -> Set Variables). Almost the same like Constants, normally without "extern" keyword.

I created all of these in a different phases of fxDreema for different purposes, but in the end they all serve to the same idea - to hold values.

Now I start to think that global MQL4 variables are not the best choise to be used for all these in the same time. The problem comes when one wants to use the same variable name for Formula result and Variables, and MQL4 just cannot do that - it is not possible to have two different variables with the same name.

But now the point is, Global Variables in fxDreema and MetaTrader IS NOT the same as global variables in MQL4. Global variables in MQL4 are variables global into the scope of the MQL4 code. Global Variables in MetaTrader are variables, global into the scope of all EA's running at the moment, and they are used to share information between EA's. In addition, they stay into the memory for 4 weeks.

And to answer the question - right click on any field that you normally can see as field for typing numbers or text. Or directly type the name of the Constant/Variable (if it is without blank spaces or starting with digit)

Magic Start is magic number basically. There is a case when magic number can be little different that magic start, but if you are not touching Group# in blocks - magic star is always the same as magic number

So, adding to volume on lose without closing previous trade. Good way to make some broker lucky

I guess the way to build this depends on the distance between trades - is it fixed (linear, every X pips), is it non-linear, or is it indicator-dependent. There is no single block for this kind of operation, but using pink blocks (Loop) many things can be done. You can check Examples to see some examples using loops.

Using custom functions from inside the project... hmmm, I have to make some deep changes to the project in order to make this possible. Well, it's not impossible now at all, but not a good idea. I can't promise that I will do than soon, because it requires some deeper changes, but I can think of it.

Now I got another idea. To make block buffers, very similar to those of custom indicators. In some way each block will be able to hold it's own set of values that can be received from next block (or all the other blocks). If such feature exists you can for example build a block to calculate some things and put the result into buffer to be read from next blocks. And you can call this block "Calculator..." or something, and it will be clearly visible as a module. Writing functions somewhere in some field is not the purpose of this platform I think.

You can enter in Chat when you are ok to check if I am online. But actually I think you are smart enough to understand what happens in Library Studio even without my explanations.

Adjustment or shortly Adjust sounds good. There were many people asking me what is that Correction field and I always wonder why. Well, I'm not native english and maybe I use not the best words sometimes

Wow, lots of things you mention here.

Normally I don't use global variables inside blocks. I prefer each block to be independent. This makes global variables free to use from people for custom reasons.

Custom block can be made without assingning input parameters to it, just by placing source code and nothing more. But blocks are not designed to return values, because they are not capable of reading values from other blocks (today). They comuunicate each other with logical connections. This word is used in a block's source code to make possible the execution of next blocks that are connected:

~next~

and this one to use the opposite output

~inext~

These words are later replaced with another code depending on what connections are made in fxDreema.

When you want to return values you can create custom functions (lower right part of the screen).

You are right that Library Studio is not well documented. The same with the main part of the platform, which is highest priority and now I started to make more examples of it. But I can show you how I create blocks with Library Studio via TeamViewer, if you want.

You can place those codes in a custom block, only the "return" part will have no meaning, because the code will be finally located outside init().

In Buy now and Sell now, you can define lot size as dynamic value or even to write "MyLotSize" instead of "0.1", if "MyLotSize" is a global variable. And that variable can be modified before going to open a new trade in a few ways, one of them is by using custom block or custom function.

Other things you mention are also good, I like new ideas. I will add them to my mental list of features for later

Indicators communicate with EA's via buffers, and buffers are simply holders of values. No more than 8 buffers for an indicator are allowed. Those buffers can represents OR NOT the objects drawn by indicator (lines, arrows, histograms and others)

Normally, if the indicator is written with all the best rules, each object of the indicator will be represented with it's own buffer. If there is a line that shows value 55 on the screen, then there will be buffer named like "LineBuffer" with the same value of 55. As we already know, EA's can read buffers, they does not search for objects actually.

An indicator can show line, histogram, arrow or other objects. While the line is normally continuous with each value very close to the others, arrows are not the same nature. Arrows are either exists or not exists. So, in case there is a buffer that represents arrow, while the arrow is visible, the buffers holds value of the level where the arrow is positioned - price value like 1.2683. But, when we have no arrow on chart, what is the vaule inside the buffer?

Buffers that represents signals drawn by arrows normally holds a value like the price level where the arrow is located. And there are many possible variants when there is no signal/no arrow. In such case the buffer can be 0, 2147483647 or negative value like -1. Why is that? It depends on how the indicator is written, it depends on the developer's work. But in order to work with that indicator, you MUST know what happens in it's buffers.

As I said before, buffers can represent objects, or can return values that are no "visible". And it's not that rare situation where you can find an indicator with broken buffers, where you will not find any logical meaning in what the buffers says. This can happen if the indicator is written by someone, then updated from another one who is not as good programmer as he believes he is.

%(#FF8000)[Now, to make things a lot easier I just made a new block named "Levels tester (for indicators and more)". Use it to check custom indicator's buffers when you are not sure what values they hold. You will be able to see values as a line and actual numbers. Use this in "Visual mode" of course.]

Good information, Andy, thank you for it.

Ticks data is a "must" when trying strategies with small stop-loss and take-profit, and especially when using techiques like trailing stop. It will be lose of time if you backtest scalping with reguar ticks data.

Far away from 1M, when we work with bigger size of stop-loss and take-profit, it's also iportant that we have good quality of lower timeframe data. 1M can be good enough, but note that M1 data normally exists in MetaTrader's history for only a few months ago. Well, it can be downloaded for longer period (this requires more PC resources).

What I actually like is that "Open prices only" model in MetaTrader's Tester. The good part is that this model is much more faster that "Every tick" model. But it requires special strategies to be tested with it. Trailing stop is not a good choice here. If our strategy is to keep single trade per bar, it's ok to be backtested using this model. In fxDreema you can use "Once per bar" block at the very top, and this will make things to happen only when a new bar comes.

Not exactly the same, but now when you create new rows into the editor, this automatically makes it to extend below.

Good idea. I will see what can I do

I can't get the idea as well. Where are blue and red lines comes from? Are they trendlines, and if yes - when a trendline happens to be below 0.00?

True. 2 years after launching MT5 it seems that people still doesn't like this position model, and I'm hoping that there will be MT6 with MT4-like model and some great things from MT5.

I know this VOM system and the idea is great. Well, there is no chance that I will use this particular thing, because there is a basic rule in fxDreema - the output file must be only one, and all custom functions used must be inside. I have an idea to create virtual model like this in fxDreema, but I'm not started working for this. The reason is well known - MT5 is not widely used. So... who knows. Waiting for an inspiration

I received your email, but I didn't sence that this is a question. For MT4 in fxDreema there is an option to use Virtual stops instead of hard ones. See in Options -> Current project options. Additionaly, there is an option to add emergency stops - hard stops at some distance from virtual ones.

Corrected. Thanks for this report! 8-)

Yes, this feature is... it should be there, it would be nice

To share custom libraries made with Library Studio with other people? Not possible in direct way. I think most of the people are not using Library Studio, so this was not needed before.