Hello!
Using the SymbolInd indicator transformer, two instruments (USD000UTSTOM_131201 and SPFB.SI_090101) are opened with a time frame of 1 hour.
The following errors occurred while working with the SymbolInd transformer indicator:
1. The symbol USD000UTSTOM_131201 was replaced by RI.RVI_1MIN_150505 spontaneously with a time frame of 1 minute. In this case, no buttons were pressed.
2. Then I changed the time frame to 5 minutes. The download took only 4.5 minutes.
Attached video:
https://drive.google.com/file/d/1L8ezGCbbzTxuhustLlzcnq5tOqIcl6HE/view?usp=sharing
It would be nice to correct these errors.
Using the SymbolInd indicator transformer, two instruments (USD000UTSTOM_131201 and SPFB.SI_090101) are opened with a time frame of 1 hour.
The following errors occurred while working with the SymbolInd transformer indicator:
1. The symbol USD000UTSTOM_131201 was replaced by RI.RVI_1MIN_150505 spontaneously with a time frame of 1 minute. In this case, no buttons were pressed.
2. Then I changed the time frame to 5 minutes. The download took only 4.5 minutes.
Attached video:
https://drive.google.com/file/d/1L8ezGCbbzTxuhustLlzcnq5tOqIcl6HE/view?usp=sharing
It would be nice to correct these errors.
Rename
The video resolution is to poor to see anything more than a symbol changing and that some error was showing in the Log Viewer. It would be nice to know about this error.
Probably what happened is that you didn't wait for a long-running request to complete, and when it finally returned, it loaded the chart. I'm not certain we can do anything about that since we can't kill threads in .Net 6.
Probably what happened is that you didn't wait for a long-running request to complete, and when it finally returned, it loaded the chart. I'm not certain we can do anything about that since we can't kill threads in .Net 6.
Hello Cone!
The error is clearly visible in the video. The error text is as follows: "QUIK: Failed to connect to QUIK: QuikSharp is not started". This error is present all the time and did not interfere with the work before the bug I described.
Here is a function for terminating a thread in NET 6.0:
https://learn.microsoft.com/en-us/dotnet/api/system.threading.thread.abort?view=net-6.0
In addition, nothing prevents the thread from terminating correctly and making it so that it does not hang.
Either way, it's a bug in the program that you can fix. There are no technical restrictions.
The error is clearly visible in the video. The error text is as follows: "QUIK: Failed to connect to QUIK: QuikSharp is not started". This error is present all the time and did not interfere with the work before the bug I described.
Here is a function for terminating a thread in NET 6.0:
https://learn.microsoft.com/en-us/dotnet/api/system.threading.thread.abort?view=net-6.0
In addition, nothing prevents the thread from terminating correctly and making it so that it does not hang.
Either way, it's a bug in the program that you can fix. There are no technical restrictions.
Maybe you should read all the text in your link? (shrug)
Denis please read a source THOROUGHLY before making a suggestion and claim. In case you still don’t read it let me save you some effort and quote the relevant passage:
“ This method is obsolete. On .NET 5 and later versions, calling this method produces a compile-time warning. This method throws a PlatformNotSupportedException at run time on .NET 5 and later and .NET Core.”
“ This method is obsolete. On .NET 5 and later versions, calling this method produces a compile-time warning. This method throws a PlatformNotSupportedException at run time on .NET 5 and later and .NET Core.”
I am not an expert in programming, but maybe this link will help you:
https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/5.0/thread-abort-obsolete
https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/5.0/thread-abort-obsolete
I read that long ago, but thanks.
Your Response
Post
Edit Post
Login is required