You would need to provide some more detailed information regarding this matter. Is this reproducible using specific steps. Is it possible to record a video demonstrating this behavior? Did you try a clean installation? Does this continue happening after a clean installation as well?
You would need to provide some more detailed information regarding this matter. Is this reproducible using specific steps. Is it possible to record a video demonstrating this behavior? Did you try a clean installation? Does this continue happening after a clean installation as well?
Check the video below on how to save your chart objects.
Best regards,
Panagiotis
This is not what I mean. Look at any other platform where it is part of the workflow. What is put on the charts stays on the chart, even if I hav not used the chart for weeks or months.
Objects stay on chart on cTrader as well until the chart is deleted.
As per the specs, 494 is not a part of the position report. It is only applicable to orders.
Best regards,
Panagiotis
I understand, is there any other way you would recommend to manage multiple strategies through the fix api? Because without the magic number I don't see how I could do this.
Thanks
Hi there,
One way would be to save this information on the client side. However FIX API is not recommended for complicated scenarios. You should consider Open API instead.
That's not the volume data of each bar,it's the amount of price changes within the candle (ticks)
Is there a way of getting true volumes of Ticks ie 10 tick chart 10 orders but how big or small are these orders?? The only reference we have is how large the candle is compared to previous
I know all of this, but it still would be nice to have the mutex/thread-safe access to the LocalStorage on Type & Instance level done by cTrader and not by an error prone user implementation.
As a user I would assume, that I do no need to care about syncing stuff (I should not even think about flushing/reloading) and just use the LocalStorage on Type&Instance level. The implementation in the background should take care that it is an atomic access to the “global” storage. And this is not the case right now, so it lacks these features whichs makes things uneccessary complex.
So if possible, please extend your implementation to guarantee a thread safe behavior across multiple instances when using LocalStorage.
Well this is not a cTrader issue but a general programming concept. When two threads try to access the same resource at the same time, then such issues happen. You need to implement some kind of control, like using a mutex
Regarding
If there is already a storage on the “type”-level, there is no reason to not be in sync over different instances. Please re-think about this. It would be nice to have a consistent access to values without flush/reload.
As you mentioned before this is resource consuming, therefore it happens automatically by design every minute.
Best regards,
Panagiotis
Hi Carsten,
Thanks for your suggestion. At the moment, we believe that this type of decision making needs to take place at the cBot's developer level and not on the API level. For most implementations, all this built in complexity would just incur unnecessary overhead to the end user. The vast majority of applications does not require a thread safe implementation so we do not see a reason to force it.
There is a mapping between symbols with different names. If you think a symbol is not mapped correctly accross symbols, feel free to share more information about it.
You need to be more specific regarding your issue. Can you please explain exactly what you are doing and how we can reproduce it? Can you share info that would help us understand the problem e.g. screenshots?
I created a cbot but it requires the user full access. When I share the algo file after the build process and I send to another person, it doesn't work because of the access. What do you recommend for that?
Hi there,
Can you be more specific regarding what is not working. cBots with full access permissions should just ask for permissions on start, but other than that, they should work without issues.
PanagiotisCharalampous
08 Apr 2024, 12:11
RE: RE: RE: RE: RE: RE: automate is just a white screen - why?
ctid2022215 said:
Thank you, the latest version is 17.4.1
@PanagiotisCharalampous