Getting Strategy Tester (and terminal) frozen with WindowHandle() function - page 3

New comment
 
Rosh:

I don't think that this case may be a reason to request for service desk. It is not bug and is not direct purpose of Strategy Tester.
Rosh,

I do not understand your position. If one software can fall into a deadlock situation, whatever a user is trying to do with allowed actions, there is definitely lack of design and/or a bug.

Anyone dealing with testing and quality control in the software industry will agree on this and will call for a fix.

Bugs not only address programming errors regarding functional specifications, but implementation decisions as well.
 
paulepanke:

If the terminal freezes because we call WindowHandle() from a stopping indicator or expert this simply is expected behaviour

IsStopped() is your friend.

The issue described on top of this thread is about one indicator attached to one EA launched with the Expert Advisor in visual mode.

In this scenario none of the indicator and EA are stopping, they still keep running until freeze.

What is your understanding in that context ?

IsStopped() isn't friend of indicators ...

 
Back to the topic ... Let's simplify to avoid some dodging and side step ... or the other way around.

What about same issue with one single Expert Advisor in visual mode without applying an indicator ?

Let's go:
  1. use joined ea_WindowHandle.mq4 Expert Advisor
  2. choose a symbol to work with and open a chart for symbol,M5
  3. launch Strategy Tester with the EA for symbol,M1 in visual mode (average speed)
  4. have a look at the messages in the journal of the Tester (journal tab): WindowHandle() works
  5. stop the Tester => the terminal hangs
Most objections are gone and the issue is still there. And the code includes the IsStopping() call to avoid calling WindowHandle() when stopping.

Is this still a feature or a bug ?
Files:
ea_windowhandle.mq4  2 kb
 
Not much point using Alert for something running in the ST.
 
RaptorUK:
Not much point using Alert for something running in the ST.
Please, be aware Alert() issues Print(). With ST the Alert() display is cut, but one print() is performed anyway. And journal tab shows those messages.
123
New comment