By the way, I wrote a plugin for the new version to prevent posting links for new accounts. This is mostly inspired by the spammers. New registrations will not be able to make posts with links to other websites when they are newer than some days, and also if they don't have some number of posts. I'm thinking about 60 days and 20 posts, but I can change the numbers. I can also change which websites to Not be counted and be allowed, but initially I will start with just fxdreema.com.
Technically, it's not an extension, but a Chrome App... not that this matters. The problem is that Google are removing support for the API (the functions with which it is written), from 2020 it seems. Maybe it still works for someone who still have it in the browser, maybe not. But it's not available in the Google Store - https://chromewebstore.google.com/detail/fxdreema-download-files/lnlppnklledgeaafojedgemkdhjdgdkp
If we go to the documentation page of the chrome.fileSystem API that is used in the extension, we can see that there is a deprecation message and a link to find out how to migrate to another API. And we can see there is something called File System Access API.
I tried this API, it's nice, it works directly in the browser, I wrote the whole functionality of the extension (and a little bit more) and everything works very good... in Linux... and for some directories in Windows, like Documents. The thing is that this API doesn't allow access to system directories, and it seems that they consider \AppData\Roaming\MetaQuotes\Terminal...\MQL4\Experts as such. And as you all probably know, this is where usually expert advisor files are.
At this point I don't know what API to use.
There is still a chance for the extension to work, but it needs to be installed locally. If you want to try:
It seems that the problem started to happen after some MT5 update, because I haven't changed this code where I found the problem now. I believe I fixed it. But the Trade detection code is a little bit complicated, so I would not be surprised if there is another bug. I hope ther is not.
Here is a little tip for being able to see what is going on in these Trade events in case there is a problem like this. There is a big class where the Trade detection happens, and I added few methods to print out information about the events. Normally this information does not appear, but this can be enabled. In the source code search for "debug" and you will find this:
public:
/**
* Default constructor
*/
OnTradeEventDetector(void)
{
debug = false;
isRepeat = false;
eventValuesQueueIndex = -1;
};
Change debug = false; to debug = true;. Now in MT5, in the logs, information about every trade event will be printed.
@ontradingx said in Why doesnt everyone here come together?:
@biztet
The idea is to do the project 100% in Fxdreema because I believe that most people who use Fxdreem like me are not mql programmers or have difficulty in programming only in codes.
I think it's not only for non-programmers, but for programmers too. There is one interesting aspect here - maybe most of the time our expert advisors are trading ideas that we want to try, but also these trading ideas can change very much when we start adding new ideas to try to minimize the losses. We start with the idea to make something, then we make something different (or even few EAs), and at the end no EA is really finished. In comparison, if it's a normal program (desktop app, website), the programmer more or less knows what he wants to make.
I think the EA bulder is good for making very quick changes in the behavior of the program. Doing such thing in the code is at least annoying. Actually, before making this website, I was experimenting with different strategies (martingale, trailing stop, fibonacci...) in MQL4 and even if my code was not that big, I was always changing the code here and there to add the new functionality. At some point I was even making some "universal" EA with everything in it.
After I made it, I was trying to make EAs with the EA builder as well, and of course I did it faster. However, my trading ideas were always very limited - some Martingale, some breakout, simple stuff. Which is probably what most people do. For that reason I see the EA builder mostly as a learning tool where anyone can try to make the strategies that other traders tried before many times.
There are also those people with bigger projects that I really can't understand. Mostly because I think fxDreema is not very good for making big projects, it just doesn't allow for good programming practices in such big scale.
But even if someone makes a profitable strategy, there is the age old question - why he will want to share it with others? That's why I don't believe in the idea of everyone coming together. Also, if for some reason this happens and everyone starts trading the same time, that strategy would quickly become obsolete.
When it comes to the usual simple strategies, I can imagine a website or a page where these strategies are presented with their results. This way if someone wants to try them, he would just see the results and understand their downsides. Or even try them himself without making them himself again.
I know that EAs can send emails or messages to android. HTTP requests to a server are also possible. They can also write to files and thus communicating with other programs on the same PC, but this is very ugly way of doing things. To communicate between EAs under the same MetaTrader, you can use those Terminal Variables (or Global Variables, F3 in MetaTrader). In theory one EA can also communicate via sockets or named pipes, but this would be very special EA that does only this task.
They are in fact 4 lines printed on the chart.
fxd_line_5_0 is the one that appears first on candle 1. Eventually id3_thirdline appers on top of it.
Well, as @miki says, there is right and wrong code in this particular situation. But the thing is that there could be a reason for "// Set variables (in)" to be at the bottom, and this is because in that Variables window you could use those P1, P2, P3 things, which are shortcuts for ObjName, ObjectType, ObjColor and the others. It's like the chicken and egg problem.
It looks that my assumption was that in the Variables window we should be able to use the Px values after they are modified. And there could be an use case where we want this, for example:
https://fxdreema.com/shared/5zi3oorD
But when I'm thinking about it, this use case is less intuitive and less possible from the one @roar stumbled upon, so I decided to fix the problem by moving "Set variables (in)" at the top. This means that the example that I'm giving above will be wrong.
I hope that this update doesn't change anyone's project, because it is always possible that someone is doing the things in the way my example works.
Well, this is better https://www.mql5.com/en/docs/convert/timetostring
I guess there is no proper way in fxDreema to output time variable, I wonder what can I do about this. But this works: http://prntscr.com/dwzl2t
I know that this is Forex-related forum, but just take a look at the cryptocurrencies these days - they are exploding and I think this is very interesting.
In the Forex world we have regular government currencies - USD, EUR and so on. All of them are controlled by some shadow entities (for example FED for US Dollars) and the value of these currencies goes up (not really) or down depending on the mood of these shadow entities. Even the prices of gold and silver are artificially suppressed. So, in Forex we may think that we are trading, but we are in fact betting in this huge virtual casino.
Cryptocurrencies - take a look at their performance - https://coinmarketcap.com/ (those small charts). Bitcoin doubled in value in few months, Ethereum doubled in a week, ZCash doubled in few hours. And I think that this is only the beginning, because most of the people in the world still don't understand cryptocurrencies, but one by one they will, and the value can only go up and up.
So, I can suggest to anyone to take a look at the cryptocurrencies. If you still don't understand them, take some time to learn them. And get some, just in case.
https://fxdreema.com/forum/topic/16633/all-blocks-resized-lost-all-connections?_=1682276113577
I fixed the problem that caused the website to be slow. It was a very slow database query that I wrote few months ago.
The other problem with the missing block titles the connections... I still don't know why it happened. I know where in the code it happens, I just can't explain how this part of the code is reached for newly created projects. It's some code where the structure of old projects (created years ago) is being updated to newer structure. For some reason some newly created projects ended up being "updated" and their structure was changed. I'm still not finished with this problem, I have to make some additional investigations.
It's a long story...
In the beginning Variables were just regular global variables and Constants were "extern" global variables. Then I started thinking "Hey, what if I remove the Constants and put a checkbox to turn any Variable into "extern" parameter?". And obviously I did that. But immediately I found a small problem...
In MQL5 you can define "extern" variable and then modify it in the code. But in MQL5. Try this MQL5 code:
input int inp = 0;
void OnInit() {
inp = 1;
}
It can't be compiled, it says "'inp' - constant cannot be modified"
If I use "extern" instead of "input", then there is no compile error, but also the variable is no longer an input parameters, it's like the keyword "extern" does nothing for MQL5.
Only in MQL4 and only if you use the keyword "extern" you can have input parameter that can then be modified into the code. But this behavior is for legacy reasons.
So, having input parameters that can be also modified in the code was (and still is) forbidden in MQL5 and even in MQL4 (when you use "input"). That's why after I added those checkboxes for the Variables I almost immediately regretted.
What is the situation today? In the output code of the web version of fxDreema, both Constants and Variables are not global variables. They are members of two separate classes. This means that they all can be modified. But there are some problems again. I found that for people with many many Variables, the code is compiled very slowly. I guess that having classes with too many members is not good idea. So I'm now thinking to make Constants and Variables global variables again.
There are some technical difficulties as you can see and this determines my decisions 
It is too big project for the compiler at this point
It doesn't work in both for me, but because of an error coming from Buy and Sell blocks. It's about the chosen money management, which requires some Stop Loss to be set
@l-andorrĂ Global Variables (of the Terminal) are stored in a file called gvariables.dat for persistence. But MetaTrader updates this file when it closes normally. I just tried it. I added a new variable, hard-reset the computer, opened MetaTrader again... new variable gone. The same with objects on the chart.
@iftikhar123ali If your sequence is adding 0.1 every time, maybe try Martingale in the settings. I know Martingale sounds scary and not what you describe, but I added so much settings over there that you can change the behavior completely.
Otherwise, when we base our next lot size on the previous one, it's always better to get the information from the trades directly. Get the lot size of the last trade, calculate the lot size of the next and so on. So, if MetaTrader restarts for whatever reason, we are fine, we know what the last lot size was and we can continue.
But there is an issue here. How do we know if we are in the middle of the sequence, or we want to start with the initial lot? Well, it depends. Maybe the value of the last lot size can tell us that. If we want to have a sequence of 0.1 - 0.2 - 0.3 - 0.4 and then start over, then if the last lot size is 0.4, it's obvious that it's time to reset and start with 0.1 again. If we cannot use the lot sizes, then the next best would be to use the comment property of the trades... although you really have to double check if whatever information you put there, stays there. Or those Terminal (Global) Variables, but I'm not sure if they work properly in case of electricity failure. One more way of storing data I can think of is some object on the chart... and again, I'm not sure if they stay on the chart on energy failure.
I'm in a process of rewriting the whole website. Such version control is something I was thinking about and I'm making the new database structure with this in mind. My first target, however, will be to release the new version of the builder with almost the same features as we have now, with slight upgrades on the most used stuff. For example, the movement of the blocks around will be a little bit different - without the scrollbars, with zoom.
Technically, it's not an extension, but a Chrome App... not that this matters. The problem is that Google are removing support for the API (the functions with which it is written), from 2020 it seems. Maybe it still works for someone who still have it in the browser, maybe not. But it's not available in the Google Store - https://chromewebstore.google.com/detail/fxdreema-download-files/lnlppnklledgeaafojedgemkdhjdgdkp
If we go to the documentation page of the chrome.fileSystem API that is used in the extension, we can see that there is a deprecation message and a link to find out how to migrate to another API. And we can see there is something called File System Access API.
I tried this API, it's nice, it works directly in the browser, I wrote the whole functionality of the extension (and a little bit more) and everything works very good... in Linux... and for some directories in Windows, like Documents. The thing is that this API doesn't allow access to system directories, and it seems that they consider \AppData\Roaming\MetaQuotes\Terminal...\MQL4\Experts as such. And as you all probably know, this is where usually expert advisor files are.
At this point I don't know what API to use.
There is still a chance for the extension to work, but it needs to be installed locally. If you want to try:
Error 403 most probably means that I blocked the IP address. Bad guys are trying to copy, spam or hack the website almost daily, I have different ways to detect this, and I block many IP addresses often. If someone uses VPN, it's possible that I have blocked the IP address in the past, if someone else used that address for bad stuff.
I also have some rules to block requests on particular patterns of the HTTP headers.
If somebody is having this error, send me an email mentioning the blocked IP address, so I can look unblock it.
I found a bug that is very problematic when someone has slow connection to the website. When downloading a file, we know that "Processing" appears up there and in background the file is downloading. However, if the download fails, then the following clicks on the export buttons are not registered, the website stops communicating with the server at all. So it's very likely that a person with slow connection with the website is fooled by this bug, thinking that he is trying to download files, but actually downloading nothing. The quick fix is to reload the page and try again, but if the connection is slow anyway, who will want to reload all the time.
At the end of the day, I think the problem is a mix of issues. Something is probably wrong with the internet connection between Thailand and Europe, then many users of fxdreema are from Thailand at the moment, and then this bug.
I will try to see what can I do about the bug, and about working with the website when the connection with it is slow.
It was reported to me that the problem started on Saturday, 21th. Pretty much all people who reported this problem to me are from Thailand. Many of them I see are part of these courses, where multiple people are logging into the same account. For that reason I thought that this could be the problem, but it seems that some of the people who reported the problem have their own accounts, so I'm not sure. I was thinking that if it's a course, maybe bunch of people are generating projects at the same time and this overloads the server. But if this is the case, then after such intense moments the server will be fine. However, in the reports I see that people are experiencing slow website in general, like the whole time. And it's just strange to me that the server appears slow for specific group of people, while for others it works fine. There must be something different that happens to these accounts, I just don't know what.
These problems seems to happen for the span of few days, like a week or so. Currently, something started to happen on Saturday. Maybe some new course or something. I think it's something external to the website and not just the server.