Any rookie question, so as not to clutter up the forum. Professionals, don't pass by. Nowhere without you - 6. - page 2

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
I have the following question. There is a block in init(), which hangs the terminal (that's what I want to transfer to dll). Naturally, the log cannot be viewed - the terminal is only closed by Ctrl+Alt+Delete. Unprinting in order to trace (and to measure transit time of loops coming into block) doesn't help - printer doesn't write anything, logging is not even created. I try to use FileOpen/FileWrite with the same purpose - file is just created (0 Kb), and silence. I put FileWrite after FileOpen, on the next line - no effect. Which way should I dig?
The topic was closed... Bad man.
I have the following question. There is a block in init(), which hangs the terminal (that's what I want to transfer to dll). Naturally, the log cannot be viewed - the terminal is only closed by Ctrl+Alt+Delete. Unprinting in order to trace (and to measure lapse time of loops coming into block) doesn't help - printer doesn't write anything, logging is not even created. I try to use FileOpen/FileWrite with the same purpose - file is just created (0 Kb), and silence. I put FileWrite after FileOpen, on the next line - no effect. What is the direction to dig?
Look, there is no hidden in the attributes?
It's not hidden.
Try using this. If that doesn't help, to search for errors, you can temporarily take the initialisation block mentioned into the start for a one-off start via a flag and try to 'pull' the logs from it.
Neither one-time startup in start nor ininit works - neither Print nor FileWrite. I'm attaching this piece of code (I don't see another way out), I'm not going to post it here, because it's too long. I have removed all buffer declarations and described all calls of built-in technical indicators there. I've already thought about memory overflow with arrays, I've calculated that the biggest array plus all other arrays is fifty and a half meters. Well, if it doesn't print even on the very first line, when entering the block... - that's what's bothering me. Attached version is true with FileWrite.
Neither one-time launching in startup nor ininit works - neither Print nor FileWrite. I'm attaching this piece of code (I don't see another way out), I'm not pasting it here because it's too long. I have removed all buffer declarations and described all calls of built-in technical indicators there. I've already thought about memory overflow with arrays, I've calculated that the biggest array plus all other arrays is fifty and a half meters. Well, if it doesn't print even on the very first line, when entering the block... - that's what's bothering me. Attached version is true with FileWrite.
The style of the code does not dispose of it. No spaces, brackets at different levels, several operations in a row, no comments... Nightmare! :-))
Do you understand it yourself?
He closed the subject... Not a good man.
= :)
Neither one-time startup nor ininitial startup works - neither Print, nor FileWrite. I'm attaching this piece of code (I don't see another way out), I'm not pasting it here because it's too long. I have removed all buffer declarations and described all calls of built-in technical indicators there. I've already thought about memory overflow with arrays, I've calculated that the biggest array plus all other arrays is fifty and a half meters. Well, if it doesn't print even on the very first line, when entering the block... - that's what's bothering me. Attached version is true with FileWrite.
I agree with Vadim - the code is hard to read. Try to decompose this code into functional blocks, in each block print or write to file. And run it in a structure that "slows down" the code execution, for example, like this:
Delay the execution of the next block by 1 sec. - The terminal should have enough time to print the log.
There are 2 very similar functions in Kim's "last position close flag by STOP" and the other by TAKE.
here is the code
As you can see they are very similar.
But for some reason, only closing by STOP works for me.
It works, but my Expert Advisor does not print UNIT, but keeps printing NULL.
But the close at STOP prints correctly: if stop = 1, if not stop =0....
help me out please....
There are 2 very similar functions in Kim's "last position close flag by STOP" and the other by TAKE.
here is the code
As you can see they are very similar.
But for some reason, only closing by STOP works for me.
I open position manually, put short TAKE. it works - but EA does not print UNIT, but continues to print NULL.
But the close at STOP prints correctly: if stop = 1, if not stop =0....
help me understand this please....