eynt
20 Oct 2022, 12:17

RE:

Hello

one is 4.2.22.8460 and the other is 4.2.22.8451.

Please try to run the sample bot on as much symbols as possible so it will make the process of reproducing the bug as fast as possible. You can try to run the cBot for a few days to be sure although for me it took no more than a few hours.

My cTrader is configured as UTC+3 perhaps it's related.

Thanks

eynt
20 Oct 2022, 10:07

RE: RE:

I wanted to add that the problem occurs on more than one broker so it's not a broker issue

eynt
19 Oct 2022, 10:13

RE:

Hello

Where you able to reproduce the bug?

eynt
18 Oct 2022, 09:07

RE:

Spotware said:

Dear traders, 

Thanks for reporting this issue. The team is aware of it and working on a solution. In the meanwhile, you need to downgrade the cTrader Automate package to 1.0.2.

Best regards,

cTrader Team

Thank you for your response.

Please report on this forum thread once this issue is solved so we can get notified by email that it is fixed.

eynt
17 Oct 2022, 23:14

RE:

Important update:

I believe I was able to fix this problem by the following actions from Visual Studio:

Right click the solution > Manage NuGet packages for solution > Downgrading cTrader.Automate from version 1.0.3 to 1.0.2

I believe there's some sort of a problem with the cTrader.Automate and I am looking forward to hearing your opinion about the subject.

Thank you

eynt
12 Oct 2022, 15:06 ( Updated at: 12 Oct 2022, 15:07 )

RE: RE:

Is there a way at least to set the default color value?

Thanks

eynt
11 Oct 2022, 00:28

RE:

Thank you

Is there a way to set the bands color by code?

eynt
09 Oct 2022, 10:43

RE:

Hello, anything new?

eynt
06 Oct 2022, 18:19

RE:

Thank you

This work for 2 indicators of the same type. What if the indicators are different types of custom indicators?

eynt
06 Oct 2022, 13:34

RE:

Hello

Anything new on the subject?

eynt
06 Oct 2022, 11:56

RE: RE: Old indicator trigger error on new version

Hello

Anything new on the subject?

eynt
05 Oct 2022, 20:19

RE:

Thank you

This indicator does load data without throwing errors, I will try to use this approach on my projects.

However, if I have several other indicators on my charts, each time GoToData get more data (which can be dozens of times if the date is far in the past) all the indicators are being reloaded again and again which can slows down the entire process of presenting the chart.

Is there a way to make other indicators load themselves only once - when the GoToData finishes getting data?

eynt
04 Oct 2022, 11:56

RE: RE:

Hello

Anything new on the subject?

eynt
29 Sep 2022, 22:09

RE:

This behavior causes my indicator to be suspended (red exclamation mark) and basically fail. Try-catch does not work either.

How can I fix/bypass that behavior?

Thanks

eynt
29 Sep 2022, 17:13

RE: Old indicator trigger error on new version

Hello

Were you able to repreduce the bug?

eynt
29 Sep 2022, 12:46

RE:

Hi

I am reattaching the solution link. I was able to download it from an external computer and open \AssemblyError\GuiTester\GuiTester.sln which has this error.

eynt
29 Sep 2022, 12:26

RE: RE:

Hello

Were you able to download the solution and recreate the error?

eynt
28 Sep 2022, 01:09

RE:

Hello

The following contains a solution with the error above. GuiTester solution and project should have a project reference to WinFormsLibrary3 which will cause following error:

Severity    Code    Description    Project    File    Line    Suppression State
Error    CS1705    Assembly 'WinFormsLibrary3' with identity 'WinFormsLibrary3, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'System.Windows.Forms, Version=6.0.2.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' which has a higher version than referenced assembly 'System.Windows.Forms' with identity 'System.Windows.Forms, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'    GuiTester    D:\Downloads\AssemblyError\GuiTester\GuiTester\CSC    1    Active
 

eynt
25 Sep 2022, 13:12

RE: RE: RE:

Hi

Is there anything new on the subject?

Thanks

eynt
22 Sep 2022, 09:04

RE: RE:

Hi

I tried to create a new bot with a new WinForm class library instead of the old one which was upgraded from .net4 and I got the same error.

I am sending you the solution by email now.

These are the steps I've made:

1. Created a new cBot and changed its cproj file so it can run with winforms

2. Created a new WinForm class library and added a form to it

3. Added the WinForm class library to the bot's solution and added its project reference

4.From the bot I tried creating an instance of the form and its ShowDialog method

5. rebuilt the solution