Thanks again, now I understand this limitation of loading properties for all indicators despite the fact that I am to run only one indicator. Perhaps NT should only check properties for the indicator in demand not all indicators in the folder.
Having said that I think part of the delay in loading indicator window, at least in my case, is that there is an attempt somewhere in the process to reach a remote server and the remote server returns an error: (500) Internal Server Error.
I have no clue what or how an indicator cause this error. I have attached the error from the Output window. I believe the process that causes this error, at least partially, delays the loading of the indicator list.
Appreciate any feedback.
Comment