self updating/refreshing grid, compare two groups of trades

[fxDreema]

Ramsay, my feelings about Sure-Fire are very negative Yes, this strategy is often requested and I shared some example that I made long time ago, but it's just a stupid strategy with wrong inputs.

First of all, let's look at this row:
0.1, 0.3, 0.6, 1.2, 2.4, 4.8, 9.6, 19.2 and 38.4

If we remove the first 0.1, then it appears that each number is double the size of the previous one, like Martingale. But why the second value is 0.3 when the first one is 0.1? Because of this small things I added some extra blocks in the example, but why do I think that the author was wrong with his numbers...

[fxDreema]

Now I see at the bottom that someone added extra stuff to the PDF and wrote this:

__I like this strategy because your overall position sizes (and therefore risk) end up being lower:

• Original sure-fire strategy position sizes: .1, .3, .6, 1.2, etc.
• This strategy's position sizes: .1, .2, .4, .8, etc.[/quote:2ef5wjra]

If I can make things even more simple, why not just using one trade at a time with fixed Stop-Loss and Take-Profit and Martingale lot size?

What we have at this time: http://prntscr.com/9genv4
Buy 0.1 + Sell 0.3 is equal to Sell 0.2. Why working with two trades when we can do it with only one. Just close that Buy and open Sell with lower lot size.

[ramsay09]

Well... fxdreema, I think this strategy is a range breakout trend following strategy and the only disadvantage is that the EAs range is not cerrectly adapted to the true current market range. If it is possible (I will try to do that) this strategy could become very interesting.

If someone don't want to take a loss on false breakouts and the stop los is the opposite range border, the sequence 1, 3, 6, 12... is correct. If someone prefer 1, 2, 4, 8... or even less, the result will be that EA/strategy need more pips to get into profit to close all trades. That will decrease the propability to close all trades and increase the propability to get trapped into a range and get a margin call or to get high draw downs.

You have to think in the category of position mangement. If you will do so you will see that it is completly irrelevent to close the opposit position. What counts is the net lot size in the wished direction. 1 -1-2 = (-2); -2 + 6 = (+4); +4 -12 = (-8); -8 +24 = +16; ...
So if you don' t want to take a loss on false break outs and want to close the oposit trade, you need the sequence 1, 2, 4, 8, 16.
A lower increase of sequence will implies that EA/strategy need more pips to come into profit.

This is what the strategy "told" to me :).

But anyway, this strategy is not very profitable and I prefer martingale against trend strategies.

[fxDreema]

Here is my old implementation for Sure Fire that I have posted multiple times - https://fxdreema.com/shared/rShdtBC4e Those Formula blocks are there only because everything starts with 1, 3, 6. For 1, 2, 4 it would be easier to build and with less blocks.

[ramsay09]

Since today morning I have multiple errors in the following kind piece of code:

else if (ModeOutput == "id_by_visible")
{
int VisibleShift = 0;
int VisibleID = 0;
int VisibleLimit = 100;

	if (VisibleLimit == 0) {VisibleLimit = Bars;}
	
	int vid = 0;

There are 80 errors involving the same kind of code. Please look over my current EAs: "Grid-EA full-auto v1.3" and "Grid-EA SR full-auto v1.1".

[ramsay09]

the errors mentioned in my last post are gone.

That is not the reaseon I want you to add the backup (two days back) of my EA "Grid-EA full-auto v1.3". There is something strange with the buy/sell blocks and the formulas.

[fxDreema]

Yes, there was some error. As you probably know, I was experimenting with "strict" mode, but with it some problems appeared. Then I disabled it and these errors appeared. Now I fixed those errors, I guess, and currently I disabled this "strict" mode, mostly because of some issues when printing numbers. Are you sure about the restore? Note that when I restore some project, it's only data about when blocks are located and their settings. The actual code that is generated does not come with the project itself.

[ramsay09]

No, thanks restoring became obsolet. I already have realized what you have wrote I have to note. Importing an old version from my HD was not removing problems. Therefore I have to mirror all my EA versions to my hd more frequently.

I would like to use the desktp builder but importing my current projects is not possible. I think it is necessary to make both version equal (browser and desktop). Couldn't you do that as early as the browser version is stable. In that case I (and probabely everyone) could work on an stable version and not on an experimenting platform like the browser version unfortunately but obviousely is.

Nevertheless fxdreema is growing and becomes better and better, but...

p.s. where did you have posted or are you posting an upcoming experimental phase. I have to keep an eye on those postings.

By the way happy new year...

[fxDreema]

The biggest problem is that I don't even want to create desktop software, I never did I always preferred to do something for the web. The desktop version was secondary from the beginning and I made it mostly because few people told me that they prefer their projects to be private. Nothing about stability, in the beginning the desktop version was very unstable. Now it appears stable because I rarely update it and when I do it, it's days after some major update on the web version. If I put everything new as soon as possible in the desktop version, you will complain from it for the same reason - it will be "unstable". There were times when I reuploaded it few times a day because every time i found some newly introduced bug

The desktop version is actually Chrome + Server + PHP code packed into an .exe file. But the server is not Apache or something well known and it doesn't have things like mod_rewrite, which is why I have troubles to put the new fxDreema into it. I worked for the current PHP framework for some months and it's easier for me to work on it now, but there is one very specific regex in the .htaccess which rewrites all requests to the server. I mean, when you want to open /examples, there is no folder /examples right on the root directory on the server, it's somewhere else.

The program I use to build the desktop version (ExeOutput for PHP) also has some Ajax issues. So I wanted to try the new version instead of working with all those bugs from the old one. The guys behind this soft mentioned few times that they will publish new version in October, but even today there is no official new version, only some Beta - http://www.gdgsoft.info/t/exeoutput-2-b ... 01-15/1363 The "jdeel" guy over there is me, but I did nothing since I wrote this post, because...

Meanwhile I decided to try NodeJS (something like Apache+PHP, but for JavaScript) and I liked it more than PHP, so I decided to move away from PHP. In the last few months I was working again on a framework, this time for NodeJS. So now I am a little bit here and there. My wish is to move the website on NodeJS, but this is not an easy task. If I do that, I will not be able to use the same soft to pack the desktop version, but I think that it can be easier for NodeJS, because this is standalone Server + JS Scripting.

Why am I writing those frameworks and jumping from PHP to NodeJS when everything appears to be working... well, because I want to make some other websites, I'm not thinking only for fxDreema. It works for now and I live because of it, but who knows what will happen, tomorrow people may lose interest in it

So I don't know. What I feel is that I want to remove the link for downloading desktop version and focus only on web stuff only. But people like it, maybe because it sometimes appears to work faster.

[ramsay09]

I can understand you very well, no one knows what will happen in the future these days. It's OK.

[ramsay09]

I have found a possible solution for my issue some postings ago but it is not working as it should. The problem is that the values of variables are lost when ea was restarted.

https://fxdreema.com/shared/pQ8moLjYb (add manually buys and sells for testing)

The intention is to set the variables to the newest lot size after setting constant to "1" . This part is working fine but after setting constant to "0" (turn off) the default value of the variables are returning. The intention is to keep the loaded lot size and than ea should work on with the loaded variables.

Why the default values are returning? The variables got a new value. I don't understand that.

[fxDreema]

I know why, but I think it should not be this way. I will see what can I do for this issue

[fxDreema]

Ok, try it now. Variables must remain the same in case of changing input parameters, changing template or changing the chart

[ramsay09]

It seems to working like I need it, thanks.

[ramsay09]

I have a question regarding the "no trade nearby" block. When I select "around the price" (value is 50) does that mean +/- 50 pips or +/-25 pips above and below the trade. Is it only the last trade or any trade nearby?

[fxDreema]

The whole range is 50 pips, so +/-25 pips. Any trade. If am I not wrong I see that I missed to add some description of this block

[ramsay09]

Ok, thanks.

Could you explain me in more details how and where to cut after point digits? I would like to have 3 digits after point for some variables. I know there are functions but I don't know where and how to use them.

[fxDreema]

I don't know what to tell you, as I also have troubles with this Floating numbers are crazy in C/C++, and MQL4 comes from there. NormalizeDouble() is used to cut digits, but sometimes it doesn't work as expected. For displaying data DoubleToString() is used, the input here is a number and the output is string (text).

I discovered that in strict mode if I try to get the Equity, which is some floating number, the result can be some number followed by many random numbers. And if I apply NormalizeDouble to the 2nd digit for example, it still does not cut the number to the 2nd number, there is something like 000001 left at the end. Then if I put (double) in front it appears that everything is ok. But the whole thing becomes something like:

(double)(NormalizeDouble(AccountEquity(), 2))

... only to cut some floating number to the 2nd digit. And I'm still not sure that the number is actually cut or I am only hiding the truth

This is for strict mode. Currently I disabled it, because... because. With strict mode people are complaining more from weird looking numbers coming out of "Comment" While in normal mode at least numbers are outputted in the way they should be.

[ramsay09]

Well, what would the Qeen say: We are not amused about that. :). But it is ok for now, in case it become urgend to have that I can use integer variables to solve that problem.

But I have another issue. My Button on my EA "Grid-EA SF full-auto v1.4" is not appearing. On version 1.2 the Button is appearing and is working correctly. I am sure I did not change anything around the Button. please, could you look over and make it appearing and working again.

p.s. the Buttons on "Grid-EA full-auto v1.4" are also not working. Did you have changed something. Operands *, / on adjust field are not working.

[fxDreema]

Can you show me smaller temporary examples of something when it doesn't work. It's always projects with hundreds of blocks... I have no idea where to look at and what am I looking for