Experts: Martin

 

Martin:

A trading system based on the Martingale technique.

Author: Vladimir Karputov

 
For time, do not set an Optimisation step.
 

The confusion comes out in the names.

Martin
Martin
  • votes: 18
  • 2017.07.18
  • Vladimir Karputov
  • www.mql5.com
Далее описание от автора идеи: Описание Советник создан по просьбе одного из участников нашего форума. Советник имеет увеличение лота, но чистым мартином его назвать нельзя, более того, этот советник действительно выходит из флета, что многим мартинам не дано. Прошу высказывать здесь...
 
fxsaber:
You can't set an Optimisation step for time.

So enum never allowed to enter a step. Only "start" and "end". And this has been the case since forever (a very long time ago).

 
Vladimir Karputov:

Well, enum has never allowed you to enter a step. Only "start" and "end". And this has been the case since forever (a very long time ago).

That's right. Only in the MT4-original version it is possible to set a step for time, while in the MT5-variant the user is artificially deprived of this possibility.

Moreover, it is much more convenient to type a number than to choose with the mouse in the drop-down list.

 
fxsaber:

That's right. Only in the MT4-original version you can set a step for time, while in the MT5-variant the user is artificially deprived of this possibility.

Moreover, it is much more convenient to type in a number than to choose with the mouse in the drop-down list.


Nope. When the user enters the date (or time), which is usually done via string, the user should not be trusted with manual input, because manually you can make up a number that cannot even be read. Besides, we should not forget that enum is great for optimisation.

And this was discussed a while ago. Remember the topic.

 
Vladimir Karputov:

Nope. When the user enters the date (or time), which is usually done via string, the user should not be trusted to enter it manually, because manually you can make up a number that cannot be read.

What does commonness have to do with it, when in the MT4-original it is not done with string, but with int?!

Besides, we should not forget that enum is excellent for optimisation.

If enum does not fit perfectly - you cannot set a step.

And this was discussed a while ago. Remember the topic.

I remember thatdisgusting topic. It has nothing to do with this EA. Except that the author of this conversion and the topic coincide.

Перевод string в часы и минуты
Перевод string в часы и минуты
  • 2017.09.06
  • www.mql5.com
Когда встаёт задача задать во входных параметрах время в формате ЧЧ:ММ, приходится решать дилему: удобство пользователя при вводе значений или удоб...
 
fxsaber:

What does regularity have to do with it, when in the MT4-original it's not string through the arse at all, but normal - through int?!

It doesn't fit enum perfectly - you can't set a step.

I remember thatdisgusting topic. It has nothing to do with this EA. Except that the author of this conversion and the topic coincide.


Nobody cares about what was in the old terminal.

If you want a step in enum - write to ServiceDesk, I am not a terminal developer and cannot give you a step when optimising enum.

 
Vladimir Karputov:

Nope. When it comes to user input of date (or time), which is usually done via string, the user should not be trusted with manual input, because manually you can make up a number that cannot even be read. Besides, we should not forget that enum is great for optimisation.

And this was discussed a while ago. Remember the topic.


time has always been set via int (if you write it as you do in your code, hour and minutes separately).

They were written using int just for the purpose of optimisation and for optimisation of these parameters a step is fundamentally needed.

No one has ever done it with enum, because users are always sane and sensible.

 
Vladimir Karputov:

Nobody cares about what was in the old terminal.

It's about the new terminal.
 
Andrey F. Zelinsky:

time has always been set via int (if you write it as you do in your code, hour and minutes separately).

These parameters were written using int just for the purpose of optimisation, and a step is fundamentally needed to optimise these parameters.

No one has ever done it via enum -- because users are always sane and sensible.


My experience is just the opposite. They are all wizards - as soon as you give them the freedom to enter something manually, they will make up such a mess. That's why enum is the best option:

  1. it is oriented to the user who has a computer mouse integrated into his hand (99% of all people who work with computers :) ) - two clicks are always easier than clicking and entering numbers
  2. guaranteed that there is no exceeding of the range of values during optimisation, i.e. by the example of a clock, the input parameter is guaranteed to be in the range from 0 to 23.