Hahaaaa: a true newbie bug in this version, which caused that high cpu resource consumption!

Who can find it?

Will be fixed in next release, to come soon.

s.

@gg53: thanks for testing and reporting!

array out of range: there’s obviously insufficient history in one of the symbols involved on your system. I’ll add a history check in a future version. Meanwhile you can reduce ‘maximum bar count’ to avoid this error.
lines ‘disappear’: this is caused by the session reset algorithm. You might consider…[Read more]

Hi,

Trying to modify VlanFx ‘s EA . This is quick and dirty (have not so much time, still working on TickVolume, etc) … so try it first on demo, this can have bugs … :(

Hi,

Trying to modify VlanFx ‘s EA . This is quick and dirty (have not so much time, still working on TickVolume, etc) … so try it first on demo, this can have bugs … :(

Ok, those mysterious symbol prefix and suffix again! I never understood why some brokers pretend to use them, or why some traders are choosing those brokers.

This is a quick patch, version 2.1 showing input parameters for symbol prefix and suffix.

Request for test: please would somebody who is connected to a broker with symbol prefix /…[Read more]

SPAM!

Ok guys!

Next public version of my CIX, including source code. I consider this one much more mature than the initial version 1, published several weeks ago. Especially the session reset algorithm is now working every day, not only once.

It also includes an alternate RSI normalization to choose from, alongside with my timeframe based…[Read more]

Ok guys!

Next public version of my CIX, including source code. I consider this one much more mature than the initial version 1, published several weeks ago. Especially the session reset algorithm is now working every day, not only once.

It also includes an alternate RSI normalization to choose from, alongside with my timeframe based…[Read more]

@gg53:

I’m happy that you changed your mind. This is what I proposed (and coded) several weeks ago, and you did not seem to like it.

See my next post for details and a new version.

s.

Ahhh, one more thing:

Good style does not mean an abundant number of comments in your code. These will only be disturbing, obfuscating the very structure of your algorithms.

Good style means that your code is so easy to understand, that it requires only a minimum of comments, and that you inserted exactly this minimum into your code.

s.

Hi Guys!

From code posted and code sent to me, I’ve got an idea now that most of the coders around have a sense about the basics of code formatting, indentation, and commenting. Yet it might be useful to review an article that deals with the very basics of these topics. The article uses C code for examples, which is very similar to MQL.…[Read more]

Thanks for that information G …

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience. Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful nam…[Read more]

@tankhang: great, good luck!

s.

@smallcat:

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience.

Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful names like volumeBullish and…[Read more]

@smallcat:

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience.

Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful names like volumeBullish and…[Read more]

@smallcat:

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience.

Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful names like volumeBullish and…[Read more]

Hi,
I am trying to create a tickVolume histogram (like GG did : Gadi_TickVolume_2.2 or previous versions). The idea based on chatting with GG last year, and the based code i took from “TVI.mq4” by “profitrader@inbox.ru” . It was a line indicator, not histogram. May be there is a histogram version out there, but i want to try to make it my self, so…[Read more]

Hi,
I am trying to create a tickVolume histogram (like GG did : Gadi_TickVolume_2.2 or previous versions). The idea based on chatting with GG last year, and the based code i took from “TVI.mq4” by “profitrader@inbox.ru” . It was a line indicator, not histogram. May be there is a histogram version out there, but i want to try to make it my self, so…[Read more]

Hi,
I am trying to create a tickVolume histogram (like GG did : Gadi_TickVolume_2.2 or previous versions). The idea based on chatting with GG last year, and the based code i took from “TVI.mq4” by “profitrader@inbox.ru” . It was a line indicator, not histogram. May be there is a histogram version out there, but i want to try to make it my self, so…[Read more]

Hi,
I am trying to create a tickVolume histogram (like GG did : Gadi_TickVolume_2.2 or previous versions). The idea based on chatting with GG last year, and the based code i took from “TVI.mq4” by “profitrader@inbox.ru” . It was a line indicator, not histogram. May be there is a histogram version out there, but i want to try to make it my self, so…[Read more]