Best posts made by fxDreema

It's not a bug, it's a feature :))) Try it with 0.1 initial lots and it works.

The problem is that there is something called Lot Step. If the Lot Step is 0.01 (in most cases), you can open the following lots (assuming that the minimum lots are 0.01): 0.01, 0.02, 0.03 and so on. The difference between each possible value is the Lot Step. Above 0.1 lots the possible values are not 0.1, 0.11, 0.12, 0.13 and so on.

The block would open open 0.012 lots if it was possible, but it itsn't. Instead, it opens whatever is the nearest possible lot. Try to open 0.012 lots manually - doesn't work as well.

@l-andorrà, I can at least try to finally make some kick-ass documentation

Yes, these lines are printed like lines from the indicator, here is the function:

The red line has name Current_Support, the blue line has name Current_Resistance. You can deal with them as objects.

Here is something I just did: https://fxdreema.com/shared/mQVcuDd8d
Here are the results:

Unfortunately the times are nor very appealing, it's because they are converted to "double" values.
The angle is 0, I guess this is the case for trend lines.
I tried to get the value from candle in the future, but it gives me an error... I'm not sure if it's not possible or there is a bug.

Also take a look at this "Bucket of Closed Trades" block. It has Time filters so you can set the time as 00:00 or even 24 hours in the past. Then, in Condition you can navigate to "Bucket... " and check the count. The problem is only that the block works only with closed trades. Maybe I have to make one such block that can work with all.

I turned off "When someone upvotes your post" and "When a post is edited in a topic you are watching".

@roar Maybe, I don't know. This quick reply field is an option and by default it's not shown. If it makes more problems, I can remove it or maybe change the theme.

@roar Yes, this option changes the id of the previous candle.

By default the crossover compares 4 values - 2 values from the current candle (or the one you choose) and 2 values from its previous candle. If the current candle is 0, the previous one is 1, and the difference (cross width) is 1.

This functionality is one that I regred adding, and I never found a reason to use it. The problem is that if you are using 40 candles difference, anything could happen inside them. Other crossovers and what not.

I added few plugins to test them.

One is obviously emojis. This one was actually active for a while a long time ago, then I removed it for some reason. I think emojis are cool, but these are maybe too big

Another plugin is Q&A plugin, here are screenshots from it. I think it's very appropriate for this category, but the way it is used is not very obvious and it requires extra clicks.

And this one - Glossary plugin. I don't know if I really want to use it, I only verified that it works.

Ok, I made it now to work with initial values like {10, 20, 30}.

If no value is specified, and when the type of the array is numeric (int, double), the value will automatically appear as 0, which looks wrong when we work with arrays, but this 0 is not actually used. Even if you write any other numeric value, it will not be used. Only value containing { will be used as initial value.

@roar said in My first MQL5 array doesn't work:

Mql5 is such a diva, always demanding some weird special tricks lol

Absolutely. MQL5 is very annoying language. And I'm a JavaScript developer.

@Pheaktra-Capo Arrays contain multiple values, as many as you want. And you can iterate these values - access them one after another. So they are often used in for loops. A simple array is like one row (or column) of data in a table. In MQL there are multi-dimentional arrays that are more like whole tables of data... but you don't want to try these.

Normally you have these events - init, tick, deinit and so on. I assume you understand them, so I won't explain them here. These events correspond to the actual event functions in MQL (https://www.mql5.com/en/docs/event_handlers). If we take the OnTick function for example, it automatically runs on every incoming tick, which means the code inside this function is executed on every tick. In fxDreema instead of code you have blocks, but the idea is the same.

This means that when building a logic, the foundation of the logic must always be the tick event. You must be able to imagine how ticks are coming and how blocks are executed on every tick.

However, traders usually think about their logic in a little bit different way. They think about steps, like "first this happens, then this happens, then this is checked and if true - this happens, otherwise something else happens". Such logic never mentions the incoming ticks.

"Waiting" blocks are my attempt to allow making the EA in that Steps logic. If all "wait" blocks can pass every time, then the whole logic is the same as the Tick logic. But if some "wait" block doesn't pass, then on the next tick this will be the block that will be executed first - the blocks above it will not be executed. And this will repeat on every tick until the "wait" block finally passes. Only when the end of the branch is reached, the top block would have the chance to be executed again.

But after I made this functionality and I tested it, I was disappointed. I don't know, maybe my brain is more accustomed to the Tick logic, or the Tick logic is just better for making trading logic. I noticed that when I stared adding more branches of blocks, I was having hard times synchronizing the work of all branches.

So, the "Waiting" logic is fine until you have only 1 branch of blocks, or the different branches are doing completely different things and they don't interfere.

Oh no, tickets. Tickets are crazy AF in MQL5, I don't recommend working with them at all. You know I recently worked on these blocks, and still I can't directly tell you what is going on with the tickets.

In MQL4 you create some order - running order, pending order - you got a new ticket number. Easy. A little bit more complicated when you decide to partially close a trade - the original one is closed and a new one is opened, but it's OpenPrice is the same as the original. Still easy.

In MQL5 there are positions, deals and orders. You decide to just open a new "trade", and you end up with a new order, which leads to a new deal, which leads to a new position. You got all three, and all with same or different tickets, depending on the environment. There is also something else called Position Identifier. If you think the arrays are complicated, try to understand orders, deals and positions in MQL5.

In MQL5 when you partially close a position, its ticket remains the same, but a new deal is created. You can have many deals (with different tickets) belonging to the same position. Even when you open and close a position, there are 2 deals - one IN deal for the open and one OUT deal for the close.

You are collecting ticket numbers in the Trade event, they are probably ticket numbers of positions. I'm not even sure what they are, and I don't really know what they should be - the tickets of the position or the tickets of the last deal.

When it comes to tickets, internally the blocks know when and what to do with them. I don't recommend working with tickets from outside. But if you do, and if you really understand how orders, deals and positions work in MQL5, you can experiment with them and give ideas for how the tickets can be used by users like you.

Timeframes are integer (whole number) values: http://docs.mql4.com/constants/chartcon ... timeframes As you can see, there are also predefined constants that can be used, like PERIOD_M1 and so on...
Well, their datatype appears to be ENUM_TIMEFRAMES, but you can't set this in fxDreema right now. But int or double should work, everything that is numeric.

MQL5 is too easy to break, but MQL4 not that much. I touched few functions in MQL4, but I don't think I touched something related to this problem.

In any case, please, when reporting some problem to me (or to the public), make some very simple example of the problem, something that can be tested quickly. Plus some extra instructions, if needed. I don't know why this is always so hard, but I can assure everyone - it's not, it's easy as connecting 2-3-4 blocks in a new empty project, takes few minutes.
When I don't have such simple example project, I have to imagine what could be the reason for the problem to happen, and there could be multiple possible reasons for the same problem.

Let's get this problem for example. You are getting some critical error 4109 "Trade is not allowed in the expert properties" and you are thinking "Oh my God, what just happened, the admin must have touched and broken something". Ok, this is not impossible, but if you believe that I broke something so important that the EA cannot run, take a look at the other topics in the forum - is there someone else reporting the same problem? If there is, then sure, most probably I broke something. But if there is not, then the probability is that the problem is local to you, something makes your setup different than the others. And if your setup is somehow different than the others, we are now searching what is that difference. One thing that is different is the EA you have.

"Indicator is visible" should pass if the indicator has value different than EMPTY_VALUE or 0
"Indicator appear" should pass if the indicator has value different than EMPTY_VALUE or 0, and in it's previous run the indicator's value was EMPTY_VALUE or 0

I will suggest to use EMPTY_VALUE in your indicator instead of 0. But why there are no positive values in the candles where arrows can be seen... I don't know. I'm not very good with indicators, but when an arrow appears, the buffer should contain value that is positive (the price level).

@vnpython-0 Yea, I'm sitting all day and testing people's strategies :))) I really don't care, but I was thinking many times that it's a good idea if the results from the tests can somehow be uploaded to the server, so for each project we can see whether it was profitable or not. I personally name all my projects ".fxDreema", but I have few named ".fxDreema-profitable" from the time when I was playing with some tests and I had good results.

The row of code that I posted in the other topic is part of one function that i wrote, in which those calculations take place. I posted this to show the person how the calculation is done.

PipValue() is also a custom function that I wrote. But its contents is kinda crazy and I don't recommend to use it anywhere. There is a reason for it to exist, but it's not to be used from the people.

TickValue equals to this - MarketInfo(symbol,MODE_TICKVALUE), which is also that "Money per tick" option.

Tick size is this code: SymbolInfoDouble(SYMBOL,SYMBOL_TRADE_TICK_SIZE)

But I think that the function PipValue() is nothing like these. I'm very bad with numbers, believe me, and I need to spend hours learning about these pips and values and ticks in order to explain them to you. Somehow I made them to work, but these values are one of these things that I immediately forget after use

At the moment someone is attacking the website, trying to login with random credentials and from different IP addresses

I mostly use "Draw Arrow", "Draw Line", "Comment", "Delay" or "Terminate" blocks.

The first 3 are similar, they output something graphical, or print some text.

The "Delay" block doesn't output anything graphical, but because it pauses the EA for few seconds, I have enough time to actually pause the Tester and investigate something at the time it happens.

I use the "Terminate" block to just stop the EA when the EA does enough of what I want. Maybe I want just 2 trades or whatever. This block allows me to run the EA on the fastest speed, stop it when I have enough info, and if I run in multiple times, It would be stopped at the same time.

Try something like this:

Or something like this with using Profit (Equity - Balance)