Posts made by fxDreema

You can also try to write this:

BuyGroupNum++

Not tested, but there is a chance for this to work.

In that "For each Trade" block these "Loop settings" you see "Skip n trades". If you have 2 there, then the block will skip the first 2 trades that it founds, so "close" would run for all other trades.

The other option "Not more than n trades" means that this is the total number of trades that could be affected (closed, in this case). I think you want to set this to 0 (or empty)

http://prntscr.com/iiri5c

This indicator has only 1 output buffer that is also Black, is there something in this buffer that can be used somehow? Otherwise there is bunch of objects that are created. I actually don't know what information such as "USD FOMC Member Dudley Speaks" means for the EA - is this buy or sell signal? :)) After all, the EA is just a program that understand only mathematics and numbers.

I never tried that, but I guess it can be done with some calculations. After all, what you have is 2 crossed lines made out of 4 points. I'm not very good in mathematics, but I think the cross point is somewhere half way between both price levels.

Yes, it's only MQL now, but I'm actually interested in crypto currencies and I was wondering if it's possible to make something like this. I never started working on this, I am doing other stuff in fxDreema at the moment, but I'm at least curious.

On the other hand, I'm a little bit idealist and I prefer to make things that are good. In that sense, I don't think that trading with bots in those exchanges is good for the world of crypto currencies. If you ask me, I would prefer crypto exchanges that only allow slow human interactions. There are many Pump & Dumps out there.
At the end, it would be the best if most of the people keep the most part of Bitcoin and other cryptos, not the opposite. It's bad when some people trick the system and enrich themselves even more. I guess that now the prices are already manipulated by bots and I don't like that word "manipulation".

Make an object and open its Properties, then go to Parameters. What do you see there?

Some objects are made out of just 1 price level, this is the horizontal line. Vertical lines are made out of 1 Time value. Arrow object is made out of 1 Price and 1 Time values. Trend line object has 2 points, so it has 2 Price and 2 Time values (call them Price 1, Price 2, Time 1 and Time 2). And some other objects are made out of 3 Time and 3 Price values.

So, depending on the object, you can read each of its Price or Time values. And they are 3 simply because there are complex objects that require all of them, but most of the objects has only 1 or 2 Time and Price values. Depends on the object.

Here is how the code of the "Delay" block works in the studio - http://prntscr.com/ig6otk This is the only block where I use .dll and the #import code can be seen at the bottom. Normally I don't want to write code that uses .dll file

I think I programmed those lines to be automatically deleted if no corresponding trade is found. The link between the trade and its line is in the name of the line, the name starts with "#" and the ticket number. I need to check it to see what is going on.
Just in case, it will be good if you have instruction of how to replicate the problem easily. Sometimes I don't know what exactly to do to get the problem.

This "cross width" field is not even important. I think I saw it disappearing before, but I keep it only because it is there since the beginning. I remember only once that someone needed this option, otherwise I don't even recommend to use it. This is one of those things that I would remove if it depends only on me

Do you have example of the "... limits" block that shows the problem? This block is more complicated

This is something that I need to add into the project's settings. I never did that before, maybe because no one asked for it (or at least I don't remember).

Are you sure that your indicators can be used the way you use them? I always recommend to check any custom indicator with the "Trace" block first (example here https://fxdreema.com/demo/mt4-trace-multiple), so you can see the values that the indicator outputs and at least you will know that they are not let's say EMPTY_VALUE or 0 all the time.

Then, you can check whether some block passes or not by connecting "Draw arrow" after it. At least I use this block all the time, otherwise I made "Trace Activity" for this purpose, but I personally never use it This is how you can detect which condition doesn't pass.

To be honest, I don't have very much experience with csv files, I only know that they are "comma separated" and if you open the file with text editor, you will see that the format is very simple. I also don't know what this SPSS expects, I only heard of this program some years ago

I think that few people asked something like this before,, but I don't know if there are any functions to do that, I never tried to solve this problem. Or, maybe there was a way to load another EA, but for the termination I don't know.

1. Wow, nothing is exact when it comes to prices. I always say that no one should use "==" in the Condition block when comparing two prices. The same goes here. This is the minimum amount of pips.

2. This is similar, but not measured in pips. Some indicators have their values that cannot be compared with the price, for example between 0 and 100. Use this option for these indicators. For MA you can also use it. but I think you should enter values like 0.0010 (for 10 pips).

3. I think that back then I wanted to somehow include the "Once per bar" block into this one, but I'm not sure how well I did it. I often think that I should take a second look at this option, because I don't know how useful it is. But I think it is explained - http://prntscr.com/ieum0h If you want to have "Once per bar" at the top of the block, better use "Once per bar", because this option is obviously something that is checked at the output side.

It should be fixed, the indicator needs to be added again

Terminal variables are called Global Variables in MetaTrader, because they are obviously variables that are global (can be accessed from all EAs). I called them Terminal, because the term "global variable" already has meaning for the EA itself. They are values written in some file I think, pretty much like the cookies in the browser, that's why they does not disappear for some time.

In MQL there are 2 general functions that are used to get and set them - GlobalVariableSet() and GlobalVariableGet(). Very, very basic. You can actually use those functions directly if you have to do something a little bit more complex. Otherwise there is a block to set them and also you can get and check their values somewhere in Condition (search for Terminal Variables).

Long time ago, when I started making fxDreema, the only indicator builder I knew was some part of Molanis. Now I don't know whether Molanis still exists or not It's kinda strange that no one decided to make something like that, and I never tried to do it. But maybe there is explanation - indicators are mostly mathematical calculations, I guess we can just write all the formulas easily in the source code instead of connecting bunch of blocks or whatever. I think that if there is an indicator builder, it would be pretty limited in what it can do, but I'm not sure.

This is known as Comment. In MQL4/MQL5 there is a function called Comment() and it prints this text over there. It does not appear as an object. In fxDreema you can print information there with the Comment (ugly) block. Later I made another block (Comment) that now uses some regular text objects to print better looking information.

You can't select this comment and it can be deleted in the source code if you do Comment(""); Basically you set the comment to empty text, which is not visible.

When you are using == to compare two prices, don't forget that the price of everything (candles, indicators) depends on the ticks, but those ticks are coming when they want and the Ask/Bid price is always different. So it's practically wrong to use ==, because you will most likely miss the exact price, and you can miss the price with 0.00001 difference. Simply don't use == to compare prices, use anything else. Use == to check exact values, for example to check whether something is 1 or 0, or some other known value.

So you opened the .mq4 (or .mq5 file) and deleted something in it? Well, if you don't understand MQL... what are you doing there :))) But you can always import that file back to fxDreema and generate the same source code (there is some code at the bottom of the file that fxDreema can understand). But you should have the project in fxDreema already, so now I'm thinking that I probably didn't understood your question.