Posts made by fxDreema

For some reason my post is broken, I don't know why

Anyway. I think you want to do it in this model:

No Buy => Condition to Buy => Close positions => Buy
No Sell => Condition to Sell => Close positions => Sell

These are 2 chains of blocks, almost the same, but one of them is for buys and the other is for sells.

Now from what I see you open a new position and on the very next moment it will be closed because of the opposite condition. I didn't checked it, but I'm pretty sure that this is the case.

And what is your version?

I have old Opera on my old laptop and it doesn't work there, but this version is from 2012, the latest version that used their engine Presto. Then they moved to WebKit, which is the same thing that Chrome uses. When I check for updates it says that it is updated, but Presto 2.12.388 is from 2 november 2012 and it's discontinued.

What about this option? http://prntscr.com/85rsgu

This indicator uses some libraries located in "Include/Controls". I don't know, it looks a little bit complex for me. How will people design such things (with many possible options) using blocks...

This is interesting question and I need to check how things happen with this function http://docs.mql4.com/dateandtime/timegmt. I guess I should add new option to all blocks that use Time or simply to use this function instead of the who returns the exact server time, or to add a new option for the project itself.

Having nothing here is incorrect in any case. I'm not sure if this means 0 and the block does nothing at all (this will be the better behaviour) or it runs through a;; history positions. Imagine if you have 500 closed positions in the history and checking them all for something on each tick...

In MT5 you can have 1 position per symbol. If a running position is stopped, then you just end up with no running position. You are actually using "No position is running" in this project, so I think I don't understand what you want to do

I think it works now

Mm, I believed that this is ok, now I will check it

I think I set it to 25 history points.

I wanted to leave the Save button and extend it actually. Let's say, to be able to save the current project and also to be able to save it to another version of the project. Then you have a list of versions, let's say 10 versions. Something like having 10 different projects into 1. But if you can load each one of them and modify and save it again, eventually you will end up with totally different strategies under the same cover. So I decided to not make it work that way.

I removed that button temporarily, until I find how to use it properly. I still think that it adds beauty to the builder, at least The question is, how to use it properly? And I want to have versions of the project, but these versions should be ordered by time somehow. Like, the first version is from 1 january, the second version is from 3 March, the last version is from yesterday. But what happens if you want to edit the first version?

Here is how versioning happens in GitHub (website for programmers)
http://jlord.us/git-it/challenges/branc ... birds.html
http://jlord.us/git-it/assets/imgs/branches.png

But maybe this is too complex for the users of fxDreema. What this is, you have a single Master version and you can start a new Branch from it and work on it until you decide to merge that branch into the Master again.

At the end I decided that if someone wants to keep something for later, he can also do it with the source code file that he exports, having the project and it's code in this way. But this is probably too simple and limited.

So the next thing I decided is that I can make it possible to mark multiple projects to not be deleted (these checkboxes) => no Save button is needed for this and you can always start working from one of these points. Isn't this the best way?

Well, I also imagine that stops should be modified with something that has "modify stops" in it's name and the time should be checked with something that contains "time" in it. Are these blocks enough... probably. But if you have other specifics, maybe not. If you just want to set the stops to 20 pips from the current price at XX:XX (+/- few minutes), then Modify Stops is ok. if all the previous stops must be remembered, then we have a problem

What project is this? For "For each closed position" you also need to specify how many positions to loop. By default this is 10, but in your case this needs to be 1.

Many people have problems understanding these blocks, but it's not hard at all. Every "For each... " block checks how many... let's say orders there are, then for each one of them causes the next blocks connected to it to run. A little bit of imagination is needed.

What I can see now is that you are working under "on Timer", while normally you should work under "on Tick"

On the right use Value -> Numeric if you want the number to be fixed. You can use it as a Constant, also in the same place (right-click over the input field) - for this you just need to define a constant. Or you can use some horizontal line.

But what is the most important here, DO NOT use == in the condition when comparing two prices. Use everything else, but not ==. If you think for a while, you will understand why.

Този номер е вързан към Magic Number, който не се променя, или поне аз не знам да може. Много малко неща се променят всъщност, май само стоповете. Само за чакащи поръчки опциите са малко повече: http://docs.mql4.com/trading/ordermodify

if you are trying hedging strategies, my opinion about these is that they are overcomplicated Martingale strategies. The same result, but much, much harder to make and maintain. The easiest thing to do in your case is to just close those buy trades and think fresh what to do next.

If you want to calculate the total lot size of those trades, it's a little bit complicated and it looks something like this: http://prntscr.com/85eof1
http://i.imgur.com/OtO811w.png

For the future I was planning a block that will load a group of trades and then in "Condition" and all the other blocks various parameters will be available, like Average Lots, Total Lots, Min Lots, SL, TP... stuff like that.

For too specific things like this maybe it's better to code them. There are blocks to draw every object possible and I have seen people making panels, but I never did this for myself and I don't know whether it's easy or not. You can check those blocks whose names start with "Draw"

Then, for capturing events, there is a workfield "on Chart". Here is when you can capture different events uding the special blocks that will appear in the list.

Well, I don't have all the browsers on the world with all their versions, but the good thing these days is that modern browsers auto-update themselves. My Opera version is 31.0.1889.99 and it's telling me that it's up to date. Yes, exporting files work on my Opera.

https://fxdreema.com/examples/
https://fxdreema.com/help/

Some examples may appear weird now, because I recently updated the website, but the main ideas are there.

__Ok I'm having some serious problems now. When I try to move or expand the "Area" boxes, they move erratically, then they either jump completely off screen, taking all my blocks with them, or the entire project disappears! The worst part is, it seems to auto save after this with your EA in a completely scrambled condition and half your blocks stretched way out off the screen where you can't even get to them, or all on top of each other in one big pile. I'm having this problem in both firefox and chrome.

What are the chances you can just bring the old Dreema back (it was perfect) and build the new one on the side or something until its ready. Maybe give it to a few beta testers or something to help you work out the bugs. I'm all for updates and everything, but it seems you've done more than just change the colors and add a few features, and in it's current condition, this new version is difficult/impossible to use and unpredictable. I spend way too much time working with this product to deal with all this - I'll lose my sanity. And I'm concerned that if I use the local version too much while the web version is being fixed, I'll have a bunch of complex EA's that I spent a great deal of time on that won't be compatible to be edited with the new web version when it's running smoothly again, and eventually the local version won't work either since it's no longer being supported? I vote for the old Dreema![/quote:9994cfe1]

I decided that this update will be smooth, but every hour something goes wrong I just experienced this problem with one area, I think that this problem is something small that I missed somewhere yesterday when I worked on the scrollbar. I will fix it in hours.

Local versions are whole bodies and they will not broke inside because of the web version. They only use the server for the initial login. Even if I continue updating the web version and not making new local builds, they will still work.

I was working for this update from the beginning of 2014 at least. Everything is now reweritten, I even created my own PHP framework and my own jQuery alternative that is faster. For all that time I did very little updates on fxDreema, mostly because it's code was reached the point where it was hard to maintain. And because of that I felt bad for months. So one day I decided to upload the update. Yes, there are few bugs here and there, but when I clear them all, the system will be much better from before. It works faster, it was written in a better way and it's more predictable for me. Most of the problems that appeared was because I wrote "true" instead of "false" somewhere in the code (I mean, simple things) or because of features that I forgot to update. I still have the whole backup before the update and it contains all projects at that time. Also, a new backup is created every night, so everything can be restored. Even the most recent actions can be restored, because in History there is a list of independent versions of the project.

__On free version when I try to download an .mq4 file it gives me this message: Method Unavailable: createObjectURL

Also when I tried to download the .ex4 file gave me some error messages on red panel like compile timeframe, but I had marked the timeframe, so this must be a problem to fix to :)[/quote:2o678y2z]

This appears on browsers that does not support this method. I know for sure that Safari has these issues. Otherwise on my Chrome, Firefox, Opera and even IE 11 it works.
You may think - this worked before, why not working now? Because now I am using JavaScript and it's Blob functions to build the output file and cause the "Save as" popup to appear. It is easier for me to make it that way and modern browsers should support that.

But I don't know why someone will do "Save As" every time, so I can recommend Chrome with the plugin that I wrote for it to automatically save and overwrite the output files. This plugin is also safe, because it uses only Chrome API's, it asks for permissions to write and it's code can be seen from everyone.