@[PoshTrader] Symbol Watermark:  23 Aug 2020, 21:46

@[PoshTrader] Market Sentiment:  14 Aug 2020, 12:52

@Renko:  27 Apr 2018, 16:25

@Renko:  20 Feb 2018, 15:55

@Renko:  02 Jun 2017, 13:41

@Enhanced Deal Map:  10 May 2017, 03:28

@Trend Analyzer:  15 Mar 2017, 15:14

@Milliseconds Elapsed:  14 Feb 2017, 12:08

@Milliseconds Elapsed Proper Version:  14 Feb 2017, 11:25

@Milliseconds Elapsed Proper Version:  14 Feb 2017, 03:30

@Crashed in OnLoad with NotSupportedException: Unable to load unsupported parameter type:  31 May 2022, 12:57

amusleh said:

Jiri said:

Hi! Any update? Is this a high priority? There are many users worried at this point, please give me something that I can use to calm them down and ensure it will be working again in the near future.

Hi,

It's high priority and this change will take effect on future releases of cTrader, I can't give you any exact ETA but you can expect it on next couple of weeks.

Glad to hear that, much appreciated!

@Crashed in OnLoad with NotSupportedException: Unable to load unsupported parameter type:  30 May 2022, 10:33

Hi! Any update? Is this a high priority? There are many users worried at this point, please give me something that I can use to calm them down and ensure it will be working again in the near future.

@Error CT0001: Unable to cast object of type 'System.Xml.XmlComponent' to type 'System.Xml.XmlElement'.:  27 May 2022, 10:46

amusleh said:

Hi,

To build an indicator with source code by using dotnet CLI you can use: 

dotnet build -p:IncludeSource=True

It's not documented anywhere yet, we will add it on Automate API documentation.

Thank you!

@Error CT0001: Unable to cast object of type 'System.Xml.XmlComponent' to type 'System.Xml.XmlElement'.:  27 May 2022, 10:38

On my end, it fixed implicit usings but not comments in the .csproj. Please, try the project below.

<Project Sdk="Microsoft.NET.Sdk">

	<PropertyGroup>
		<TargetFramework>net6.0</TargetFramework>
		<ImplicitUsings>enable</ImplicitUsings>
		<!--<LangVersion>latest</LangVersion>-->
	</PropertyGroup>

	<ItemGroup>
		<PackageReference Include="cTrader.Automate" Version="1.*" />
	</ItemGroup>

</Project>

using cAlgo.API;

namespace cAlgo
{
    [Indicator(AccessRights = AccessRights.None)]
    public class ErrorCT0001 : Indicator
    {
        protected override void Initialize()
        {
            Print($"The PI value is '{Math.PI}'.");
        }

        public override void Calculate(int index) { }
    }
}

@CT 4.2 Chart Freeze Adding a Canvas:  27 May 2022, 10:14

I have noticed this as well, it's acting as if the canvas is having transparent background which makes it capture mouse events. You can set IsHitTestVisible to false to fix that but that will affect all the child items which might not be desirable. Setting the BackgroundColor to null does not help.

@Error CT0001: Unable to cast object of type 'System.Xml.XmlComponent' to type 'System.Xml.XmlElement'.:  27 May 2022, 09:56

Thanks for sharing this with me but it's not fixing the Error CT0001. Furthermore, I asked if it's possible to control whether the dotnet build should include the source code or not by using build properties passed as a parameter.

Amusleh, if you don't have an answer then let me know. I feel like many of my questions are being ignored making me repeat the same question multiple times hoping for an answer. I would highly appreciate it if we can make the communication more efficient.

@Crashed in OnLoad with NotSupportedException: Unable to load unsupported parameter type:  26 May 2022, 20:18

amusleh said:

Hi,

We discussed this and we are considering to change this behavior, but we can't make any promise.

Any estimation on when will you know the final verdict? Is it considered in the upcoming version, if so what is the ETA?

@Error CT0001: Unable to cast object of type 'System.Xml.XmlComponent' to type 'System.Xml.XmlElement'.:  26 May 2022, 14:37

The cTrader builder fails with Error CT00001: Unable to cast object of type 'System.Xml.XmlComponent' to type 'System.Xml.XmlElement' if the .csproj file contains any comments. Additionally, the builder does not support implicit using and fails with an Error CS0103 if enabled. This leads to a question, is there a way to build an algo with the source code using the dotnet build or MSBuild with a parameter instead of relying on the integrated builder?

@Crashed in OnLoad with NotSupportedException: Unable to load unsupported parameter type:  25 May 2022, 13:28

I am not asking you to remove it, I am asking you to add the condition back in so my products can continue to work.

Please, can you explain why there needs to be the parameter type check for all the classes inheriting from the Indicator despite not being decorated with the IndicatorAttribute, why the change is required and can't be reverted?

@Crashed in OnLoad with NotSupportedException: Unable to load unsupported parameter type:  25 May 2022, 13:03

It was never supported, parameter have a list of supported types, and you can't use other types except them for parameters.

It was supported, how else would I build indicators that way which are working perfectly fine (prior 4.2) and are still used by hundreds of cTrader users.

You are misusing parameter attribute, it's meant to be used for showing a parameter on indicator/cBot parameters window, it's linked to cTrader UI and you can't use any object you want to as a parameter.

That applies to public indicators with IndicatorAttribute that are supposed to be shown in the UI, then it makes sense to have limited types supported only. If the indicator is not decorated with the IndicatorAttribute, whether it’s public, internal, or private, it is not exposed to the UI, and there is no need for the parameter type limitation. Using the ParameterAttribute is the only way to populate properties in the constructor by using the GetIndicator method and passing parameters into it. Which is how I built my indicators that were working for years without a single problem.

This is and was our design, you can't blame us for your misuse of API. The way you used Parameter attribute was not correct, and you were exploiting a bug on parameter type validation. You were exploiting a bug on API and when it got fixed now you are complaining why we imposed new limitation?

Are you serious about this?! I used the API as it was delivered to me. If I blame you for anything then it's for making changes for no reason that breaks almost every product I have made for this community and for you being so arrogant and unwilling to do anything about it.

I have no idea what's internal indicator

Here you can learn about internal modifier, what it is and why to use them. I have mentioned it numerous times, there are accessibility and OOP reasons for it. I don't see why I should be limiting myself to certain design patterns only.
https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/internal

It's not a new imposed limitation, it was a bug on parameter type validation and it's now fixed. You have to use an API properly, if there was something weird possible you had to report it to us, not misuse it. We haven't imposed any new limitation, cTrader 4.2 contains some bug fixes.

The limitation wasn't there before, it wasn't mentioned anywhere as a bug, and it wasn't breaking anything. If there is no reason for the change then why make it? I would really like to know what kind of bug this change is fixing. It breaks products that are in use by hundreds of users, it’s your community and my customers that are affected.

Please, revert this change and make the parameter type check only if the indicator is public and decorated with the IndicatorAttribute as it used to be all the time! Most of these indicators are offered for free so it's not worth my time to redesign all the indicators, reinvent the wheel to get all the features I am utilizing from the Indicator class, and redistribute it to over 600 users. If you don't want to address this, then let me know so I can inform all the users about discontinuing all the products before their brokers roll to the latest version of cTrader. I am already getting angry emails from those that have rolled over to the latest version.