What's all this nonsense about the tab character{t}? - page 7
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Andrey, I told you, that it was not necessary to multiply the parallel versions. Now you have one function and I have another... You should have kept one project.
Doesn't really matter :-). If the project is simple, you can maintain 2 projects :-).
To add other functions - 5 minutes of time.
You know, if the video doesn't inspire you, don't edit it :-).
And personally I won't be able to write my advisers without such a thing ;-)...
What's the idea - for me to manually look for something in the log.
The Stone Flower doesn't work. The script (my Expert Advisor) opens the second window.
Do you have any idea how to fix it? I do not have any.
MetaDriver:
Any idea how to treat it? I don't have one yet.
I've got one. It's a little messy, but it will work.
The scheme of work is like this:
1. tester expert writes a log file, not a window.
2. After testing, we take MyTesterLog.log file and copy it manually to ..\MetaTrader 5\MQL5\Files folder
3. ShowLog-expert in Inite takes everything from the file to Debug-window...
4. ...and positions clicks in the same window as intended.
It's boring to write yet, but it should work 100%.
.
So...
The point is that all Mql-files must refer explicitly to the same dll-index.
Otherwise, it loads them from different places and you get two windows.
I was shocked myself - I ended up with the same 1:1 !!!
.
Well...
The point is that all Mql-files must refer explicitly to one dll-ina.
Otherwise, it loads them from different places and you get two windows.
I'm not interested in Whose fault it is. // I know it myself. ))
Tell me what to do.
;)
I am not interested in WHO is to blame. // I know it myself. ))
Tell me what to do.
;)
all Mql files must refer to the same dll-in.
.
Check that the imports refer to the same dll-in.
Told you:
all Mql-files must refer explicitly to one dll-index.
.
Make sure the imports refer to the same dll-in.
There's no doubt about it.
I think (actually I'm sure) MT5 creates a new instance for each process. I think I even encountered this in the documentation some time ago. I even wonder why all different instances of EAs write everything in one window during optimization. Perhaps they all exist within a single thread, so it is possible. Anyway, this problem is beyond my comprehension. If you can't make different instances of DLL write everything in one window, I'll pass.
You can probably do this by using the second dll-in (called from the first one) as the window's host. In any case, window should be a singleton.
// Correct the buttons at the same time, Bomb! ;)
There's no doubt about it.
I think (actually I'm sure) MT5 creates a new instance for each process. I think I even encountered this in the documentation some time ago. I even wonder why all different instances of EAs write everything in one window during optimization. Perhaps they all exist within a single thread, so it is possible. Anyway, this problem is beyond my comprehension. If you can't force different instances of DLL to write everything in one window, I'll pass.
Perhaps this can be done, if you use second DLL-ino (called from the first), as the hostess of the window. In any case, the window must be a singleton.
// Correct the buttons at the same time, Bomb! ;)
Hmmm... If there's a separate process for each instance, that's a bummer...
and there's no simple cure.
.
> I even wonder why DIFFERENT instances of EAs write everything in one window during optimization.
If they are from one process, they write everything in one window.
.
> If you can't make different instances of a DLL write everything in one window - I'll pass.
It's relatively easy to do, but I'd have to redo everything :-).
How good that I'm not using MT5 yet :-D.
.
If the processes are different, then the second dllin will not solve the problem.
You need a separate process with a window to receive messages
and commands from several other processes.
.
The easiest way is to find a window and send it WM_COPYDATA of some kind.
It's all bad... :)
All experts on different normal charts + all scripts (there) ready to write in the same window.
Just run in the tester - opens another and writes in it. Such a mess.
Probably because the tester is actually a separate program (MetaTester.exe), it opens an additional copy. You can't get in its way.
Razumo: I think we need the dll-level decoupling/binding.
--
Trailer is a corrected version of EA + intermediate lib on µl (tried to make one instance of dll to use)