CircularGauge PointerType.Marker compilation error

[oggg]

Hi,

I am trying to create a circular gauge with the following markup:

<ejs-circulargauge id="XXXXXXXXX" style="height: 103px" load="gaugeLoad">
        <e-circulargauge-axes>
            <e-circulargauge-axis>
                <e-axis-linestyle width="3" color="transparent"></e-axis-linestyle>
                <e-axis-labelstyle font="font" position="@Syncfusion.EJ2.CircularGauge.Position.Outside"></e-axis-labelstyle>
                <e-axis-majorticks height="0" width="1" interval="200" color="transparent"></e-axis-majorticks>
                <e-axis-minorticks height="0" width="0" color="transparent"></e-axis-minorticks>
                <e-axis-annotations>
                    <e-axis-annotation content="#pointerValue" angle="180" zIndex="1.0" radius="150%"></e-axis-annotation>
                </e-axis-annotations>
                <e-axis-pointers>
                    <e-axis-pointer type="@Syncfusion.EJ2.CircularGauge.PointerType.Marker" markerShape="Triangle" ></e-axis-pointer>
                </e-axis-pointers>
            </e-circulargauge-axis>
        </e-circulargauge-axes>
    </ejs-circulargauge>

But the line "<e-axis-pointer type="@Syncfusion.EJ2.CircularGauge.PointerType.Marker" markerShape="Triangle" ></e-axis-pointer>" causes:

Cannot implicitly convert type 'Syncfusion.EJ2.CircularGauge.PointerType' to 'Syncfusion.EJ2.LinearGauge.Point'. An explicit conversion exists (are you missing a cast?)

Best Regards

[Arun Raji]

Hi Oggg, 

Sorry for the inconvenience, 

We have analysed your scenario. We can replicate the issue in e-axis-pointer tag. Both circular and linear gauge uses same namespace, hence the issue is occurring, we will considered this as improvement from our side and it will be rolled out on second patch release after Volume 2 main release, which is expected on middle of July 2019. You can keep track of the improvement from the below feedback portal. 

Feedback Portal: https://www.syncfusion.com/feedback/6759/  

So, as of now, you can use the Javascript code for circular gauge pointers. I have attached the demo sample in below location for your reference. 

Sample Link: http://www.syncfusion.com/downloads/support/directtrac/general/ze/cicular1082114388  

Let us know, if you have any concerns. 

Regards, 

Arun 

[oggg]

Hello Arun,

Thank you for both the answer and the demo

Best Regards

[Baby Palanidurai]

Hi Oggg,

Thanks for your update.

As mentioned earlier, we will consider this improvement for second patch release after Volume 2 main release, which is expected on middle of July 2019. We will let you know once our release is rolled out. We appreciate your patience until then.

Regards,
Baby.

[Baby Palanidurai]

  

Hi Oggg,   

  

Thanks for your patience.  

   

We are glad to announce that our v17.2.40 patch release is rolled out, we have included the reported issue fix and weekly NuGet packages(v17.2.0.40) has been published in nuget.org.  

Now, the e-axis-pointers, e-axis-ranges, and e-axis-annotations tag names have been renamed to e-lineargauge-pointers, e-lineargauge-ranges, and e-lineargauge-annotations, respectively in ASP.NET core.   

Code snippet: 

<ejs-circulargauge id="circular"> 

        <e-circulargauge-axes> 

            <e-circulargauge-axis> 

                <e-circulargauge-pointers> 

                    <e-circulargauge-pointer type="RangeBar" value="40"></e-circulargauge-pointer> 

                </e-circulargauge-pointers> 

                <e-circulargauge-ranges> 

                    <e-circulargauge-range start="0" end="20"></e-circulargauge-range> 

                </e-circulargauge-ranges> 

                <e-circulargauge-annotations> 

                    <e-circulargauge-annotation content="Value : 40" zIndex="1"></e-circulargauge-annotation> 

                </e-circulargauge-annotations> 

            </e-circulargauge-axis> 

        </e-circulargauge-axes> 

    </ejs-circulargauge> 

 

Screenshot: 

 

We appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.  

   

Thanks,           

Baby.