For the scalper: 1-click-click ftw

Thank you. Can you post a changelog?

@ m.m.m

Thank you very much, thats very nice



When i switch the timeframes the ea still crashes, is it possible to fix that in the code?

Can you show me how to locate the rectangles?

Delete the version you have and download again from post#1 .
I just tested it and it does not crash Mt4 when timeframes are switched.

I forgot how to locate the rectangles, but you can see how mmm is doing it in the source code.
Then you define your own rectangle on the chart and try to change the code so the EA takes
action when you click into your own rectangle.
From there you fine-tune it by testing all possible x and y distances.
That is how I did it.

Thank you, fxtr51.

Hi m.m.m,

is it possible to code some real buttons like the mt4gui?

The mt4gui is a great tool but always crashes, a stable button would be a fantastic improvement to metatrader users.

https://www.fx1.net/wiki/pmwiki.php/MT4GUI/MT4GUI



Lg
remon

I have been asking a few professional programmers to code something like mt4gui.dll .
It will cost more than 3000 Dollars.
So go ahead and hire a programmer, but do not expect anybody to code it for free for you.

mt4gui doesn´t crash Mt4 if you know how to use it.
It has functions which crash Mt4, yes , and some functions do not work as they should,
but I have managed to circumvent the crashes.
If you ask me how to do it: test, experiment.
Took me weeks and hundreds of crashes daily to find the solution. S

This is a really cool way to implement one-click trading! I have run into a bug however.

When I try to place a drawing element such as a trend line or Fibonacci tool on the chart, or just use the crosshair cursor to measure distances, the operation sometimes fails. The Fibonacci or trend line object appears on the chart with the starting point and ending point in the same spot, overlapping. Any operation that has to do with clicking the mouse button down, dragging it and then releasing it elsewhere has this problem. It is intermittent, does not happen every time -- seems to be worse during the most active times of the market. And just to dispel any doubt, there's no other indicator, EA or other code running in this window other than Z, and this problem has never occurred anywhere that Z is not running.

I enabled the Print statement on line 96, and it reveals that two calls to lbuttondown() are made whenever this problem occurs. I have no clue why. Maybe something weird happens if the button click is received while start() is active, but I'm just speculating. Perhaps replacing the detection of a Left Button Down event with a Left Button Up event might solve this, but I'm out of my element when it comes to Windows internals. Any clues?

Dear m.m.m.

Excellent tool, I love it!!!