Step back - page 2

New comment
 
sanyooooook:

I also want to be able to roll my actions back in time,

but other than recording on video and rolling it back on tape, I haven't found a solution ))

ZS: but the ability to run the test NOT first for twenty-four hours seems to me to be useful in this case.

Almost the same is offered by setting the date in visualisation mode and the "scroll" button.
 
IvanIvanov:

All you have to do is find the answer to the question - "Who needs it?"

The main thing is to have it. And who needs it will find it later. I think it is much better to have something and not use it, than to have the desire but not be able to use it.

On a domestic level, it's like having a gun in the house. Let it lie there and not disturb anyone. But if a criminal breaks in... And you don't have a gun in the house...

And I kindly ask you not to turn the conversation to lawfulness of use and responsibility for it. Everyone decides for himself whether to use one or not.

 
Tapochun:
Almost the same is suggested by the date setting in visualisation mode and the "scroll" button.
Almost doesn't count, it's not from the date but from the new year, and, fwiw you hit that button, try to catch the candle first - then say
 

sanyooooook:

...but the ability to run the test NOT first for 24 hours seems to me to be useful in this case.

Generally a useful feature... I agree. Even asked/suggested through ServiceBrilliant myself... said they won't do it...
 
IvanIvanov:
Almost doesn't count, it's not from the date but from the new year, and, fuck you hit that button, first try to catch a candle - then say
If you and I are talking about MT5, can you please clarify what you mean by "try to catch a candle"?
 
IvanIvanov:

I understood that if you rewind, the amount of data - on the contrary - is reduced. what prevents you from returning to the state a few steps back, if you continue in the usual direction options can be generated again, it will even be more correct.

No, it won't be less.

To go back 1 tick, you have to remember the entire environment, the state 1 tick ago. For example, the list of positions, list of closed positions, values of all used variables, indicators, variables used in indicators, etc.

But one tick will not be enough, right? So, we need to remember the entire environment state for each of X back ticks. And this will cause an enormous slowdown of the entire testing.
And who will be ready to sacrifice speed for the sake of being able to rewind several bars back? I, for one, am not.

Just don't suggest "make a setting and don't let anyone not want to turn it on". Think about how much you have to invest in this customisation, and whether it will be in demand by millions of users.

 
And scrolling to the right bar is easy to do with an external setting and a single line of code.
 
komposter:

No, there won't be any less.

To go back 1 tick,

The suggestion was to go back 1 bar. It would be better if by pressing the button we could go both back and forward to the necessary bar, and then run the tickwise execution to trace the EA's behavior at a certain moment. This would be very useful for me personally when debugging EAs. Both the debugger and the tester.

However, for testing over a long period and without visualisation this is absolutely unnecessary and should not be available.

 
komposter:

No, it won't be less.

In order to go back 1 tick, you must remember the entire environment 1 tick ago. For example, the list of positions, list of closed positions, values of all used variables, indicators, variables used in indicators, etc.

But one tick will not be enough, right? So, we need to remember the entire environment state for each of X back ticks. And this will cause an enormous slowdown of the entire testing.
And who will be ready to sacrifice speed for the sake of being able to rewind several bars back? I, for one, am not.

Just don't suggest "make a setting and don't let anyone not want to turn it on". Think about how much you have to invest in this tweaking and whether it will be in demand by millions of users.

I do not understand anything, there is a very common tester that has both forward and reverse and does not eat anything and has not invested millions in it.
 
AlexeyVik:

The suggestion was 1 bar backwards. And it would be better to move backwards and forwards to a desired bar by pressing a button and then start tickwise execution to trace the behaviour of the EA at a certain moment. This would be very useful for me personally when debugging EAs. Both the debugger and the tester.

However, for testing over a long period and without visualisation this is absolutely unnecessary and should not be available.

First the bar, then they will ask for control points, then they will ask for ticks too.

If you look at the issue not from the point of view of one single user, but from the point of view of millions, it will be a very different picture.

I'm not saying that I wouldn't take advantage of this opportunity, I just understand that no one will implement it because of 2-3 willing users.

IvanIvanov:
I don't understand anything, there's a very popular tester that has both forward and backward moves and doesn't burn anything.

Shall we do a detailed comparison with the MT tester?

Or "should accelerate to a hundred in 3 seconds like a Lamborghini, but cost like a fiat punto"? ;)

123456789
New comment