1. Home
  2. Forum
  3. Xamarin.Forms
  4. Multiple DateTimeRangeNavigator on a same page

Multiple DateTimeRangeNavigator on a same page

We want to use multiple DateTimeRangeNavigator on a same page but there is an issue with RangeChanged event. 
No matter from which DateTimeRangeNavigator we are changing range, event gets invoked from the last one. and whatever the change occurs to any DateTimeRangeNavigator, the last one also gets that change. 

for reference, video has been attached. 

Thank you for your help,
Manzar Gulzar

Attachment: Video_caf1ff84.rar

27 Replies 1 reply marked as answer
SS Swetha Srikumar Syncfusion Team March 29, 2021 06:30 AM UTC


Sent: Monday, March 29, 2021 2:25 AM
To: Syncfusion Support <[email protected]>
Subject: Re: Syncfusion support community forum 163942, Multiple DateTimeRangeNavigator on a same page, has been created. 
  
  
Is there any update on this thread?  



YP Yuvaraj Palanisamy Syncfusion Team March 29, 2021 04:55 PM UTC

Hi Manzar Gulzar, 
 
Greetings from Syncfusion. 
 
We have analyzed your query and we can reproduce the reported problem at our end. Currently we are validating the issue and we will update you with complete details on or before 31st March 2021. 
 
Regards, 
Yuvaraj. 


MG Manzar Gulzar April 1, 2021 10:20 AM UTC

Hi dear,
hope you are fine and enjoying a healthy life.

I just wanted to ask that is there any update?
sorry for bothering you again and again. Actually, we have an urgent deliverable that includes this control. 
will be waiting for your response :)

regards, 
Manzar Gulzar

YP Yuvaraj Palanisamy Syncfusion Team April 1, 2021 05:07 PM UTC

Hi Manzar Gulzar, 
 
We understood your situation. We can reproduce the reported problem at our end and forwarded this to our development team. Currently they are working on this and we will update you with complete details on or before 5th April 2021.  
 
Regards, 
Yuvaraj. 


MG Manzar Gulzar April 8, 2021 06:50 AM UTC

It's 8th April. Is there any update? 

YP Yuvaraj Palanisamy Syncfusion Team April 8, 2021 01:53 PM UTC

Hi Manzar Gulzar, 
 
Thanks for your patience. 
 
On further analysis we have confirmed “In Multiple range navigator control in the same page, RangeChanged event invoked the last DateTimeRangeNavigator” as an issue. The fix of the reported issue will be included in our weekly NuGet release which is expected to publish on 20th April, 2021. We appreciate your patience until then. We will let you know once it gets rolled out.  
    
You can now track the status of your request, review the proposed resolution timeline and contact us for any further inquiries through this link.     
   
     
Note: The provided feedback link is private, and you need to login to view this feedback  
 
Regards, 
Yuvaraj. 


YP Yuvaraj Palanisamy Syncfusion Team April 20, 2021 02:04 PM UTC

Hi Manzar Gulzar,  
   
Sorry for the delay.  
   
Due to some technical hurdles, we are not included this fix for the issue “Multiple RangeNavigator range changed event fires the last range navigator” in today weekly nuget release. And we will include the fix in our upcoming weekly nuget release which will be rolled out on 27th April 2021. Once we rolled out, we will let you know, until then please use the patch.  
 
Regards, 
Yuvaraj. 


MG Manzar Gulzar April 20, 2021 07:02 PM UTC

Hi Yuvraj,

Thanks for the details.

Can you please tell me which patch are you talking about?

regards,
Manzar Gulzar

YP Yuvaraj Palanisamy Syncfusion Team April 21, 2021 11:02 AM UTC

Hi Manzar Gulzar, 
 
Sorry for the inconvenience.   
  
We are currently working on this and once we will complete the issue fix and test case, we will provide the patch for this fix. And as we informed you earlier, we will include the fix in our upcoming weekly nuget release which will be rolled out on 27th April 2021. Once we rolled out. 
  
Regards,  
Yuvaraj.  


YP Yuvaraj Palanisamy Syncfusion Team April 22, 2021 11:45 AM UTC

Hi Manzar Gulzar,  
 
We have fixed the reported problem “In multiple RangeNavigator, range changed event fires the last range navigator”. And we will include the fix in our upcoming weekly nuget release which will be rolled out on 27th April 2021. we will let you know once we rolled out. Please use the provided patch until then. 
 
Also, we have generated the patch for this fix with version 19.1.0.54, until then please use the below patch.    
    
    
    
    
Assembly Version: 19.1.0.54    
        
Disclaimer:      
     
Please note that we have created this patch for version 19.1.0.54 specifically to resolve the issue reported in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.    
  
For more details, please refer below kb to clear the cache:   
 
Regards,  
Yuvaraj.  


YP Yuvaraj Palanisamy Syncfusion Team April 27, 2021 02:28 PM UTC

Hi Manzar Gulzar, 
 
We are glad to announce that our weekly NuGet was rolled out and fix for the reported issue was included in the weekly NuGet.

NuGet Version: 19.1.0.58 

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 
 
Regards, 
Yuvaraj 


Marked as answer
MG Manzar Gulzar April 28, 2021 04:37 PM UTC

Good to hear that.
we will try to use this version and will get back to you if we need any assistance. 

Thanks,
Manzar Gulzar

SM Saravanan Madheswaran Syncfusion Team April 29, 2021 04:39 AM UTC

Hi Manzar,  
 
We appreciate the update and are pleased to assist you. 
 
Regards, 
Saravanan. 


MG Manzar Gulzar June 24, 2021 12:00 PM UTC

There is still an issue with the change range event.
sometimes sender is incorrect in the event when we try to change any of the range from multiple controls on a single page.


YP Yuvaraj Palanisamy Syncfusion Team June 25, 2021 05:20 PM UTC

Hi Manzar Gulzar, 
 
We have checked with our latest version 19.1.0.69 and the reported problem has been working fine at our end. Also, we have shared the sample for your reference. Please find the sample from the below link 
 
  
Syncfusion version : 19.1.0.69 
 
Xamarin.Forms version : 5.0.0.2012 
 
Please clear the cache and check the provided sample with latest version, if still you are facing the same problem, please revert us with modified sample with issue reproduced state which will be helpful to serve you better solution at the earliest. 
 
Regards, 
Yuvaraj. 
  


MG Manzar Gulzar July 2, 2021 01:57 PM UTC

We have used your giver sample and tried to reproduce the issue. We didn't have to change anything in the sample, and issues got reproduced. We have sent a captured video for your understanding.
Please see the attachment. There are still multiple issues with the control that are as follows:

  1. When control first time loads on the screen, the event gets raised multiple times and every time with a different sender value.
  2. when we change the range, different events get the call again multiple times but with the correct sender value. 

Attachment: Issue_with_Range_Navigator_9e8447ce.zip

YP Yuvaraj Palanisamy Syncfusion Team July 5, 2021 12:28 PM UTC

Hi Manzar Gulzar, 

Thank you for providing the video. 

Currently we are validating on this reported problem and we will update you with complete details on or before 7th July 2021. We appreciate your patience until then. 

Regards, 
Yuvaraj.

YP Yuvaraj Palanisamy Syncfusion Team July 8, 2021 05:04 PM UTC

Hi Manzar Gulzar, 
 
Thanks for your patience. 
 
We can reproduce the reported problem “In multiple range navigator, range changed event called multiple times” at our end.  And we will update the fix details for this issue on or before 12th July 2021. We appreciate your patience until then. 
 
Regards, 
Yuvaraj. 


YP Yuvaraj Palanisamy Syncfusion Team July 14, 2021 03:00 AM UTC

Hi Manzar Gulzar,  
  
We regret for the delay.  
  
On further analysis with our development team, The SfDateTimeRangeNavigator RangeChanged event has been fired when updating the visible range start and end also updating the control range changed (Minimum and Maximum).   
  
In loading the SfDateTimeRangeNavigator, fires RangeChanged event while updating the range start and range end which having the updated sender value of SfDateTimeRangeNavigator. And while changing the range, RangeChanged event fires multiple times for every pixel changes.   
  
Regards,  
Yuvaraj.  


CM Cosme Morales Picon November 17, 2021 04:56 PM UTC

As of today, 11/17/2021, I still have the same problem. When I have more than one SfDateTimeRangeNavigator on the same page, only the last one is updated.


Hadn't it been solved?


I have the 19.3.0.48 Nuget package for all the wigets I use, do I have to download the 19.1.0.69 for it to work?


DD Devakumar Dhanapoosanam Syncfusion Team November 18, 2021 04:58 PM UTC

Hi Manzar Gulzar, 
 
Query: I still have the same problem. When I have more than one SfDateTimeRangeNavigator on the same page, only the last one is updated. Hadn't it been solved? 
 
We have analyzed your query and the reported issue has been fixed and moved in 19.1.0.69 NuGet version. We have ensured once again using the latest version too working proper at our end.  
 
Please find the tested sample and video in below link. 

Please clear the cache and check the provided sample with latest version, if still you are facing the same problem, please revert us with modified sample with issue reproduced state which will be helpful to understand and provide you better solution at the earliest. 
 
Regards, 
Devakumar D 


CM Cosme Morales Picon November 19, 2021 12:01 PM UTC

Thanks for answering so quickly. I have been able to reproduce the problem by changing the code to how I want to use it.


I have a flexLayout, to which I dynamically add a graph and a SfDateTimeRangeNavigator. And what I want is to modify the SfDateTimeRangeNavigator and make its top graph zoom. But when there are 2 or more graphs with their respective SfDateTimeRangeNavigator, only the last one is changed regardless of which SfDateTimeRangeNavigator has modified.


I honestly do not know if it is my problem and logic or something about the controller or some limit of it.


I hope you can help me.


PS: Only 3 charts can be added simultaneously.


Attachment: RangeNavigatorNewVersionCosme_abc12be5.zip

DD Devakumar Dhanapoosanam Syncfusion Team November 22, 2021 12:49 PM UTC

Hi Manzar Gulzar, 
 
Thanks for the update. 
 
We were able to reproduce the reported issue with the provided sample in UWP platform at our end. Currently we are validating this at our end and will update you the complete details in two business days on November 24, 2021. 
 
Regards, 
Devakumar D 


DD Devakumar Dhanapoosanam Syncfusion Team November 25, 2021 02:15 AM UTC

Hi Manzar Gulzar, 
 
Sorry for the delay. We still need some more time to validate the reported issue at our end and we will update the complete details for reported issue on November 25, 2021 before EOD. We appreciate your patience until then. 
 
Regards, 
Devakumar D 


DD Devakumar Dhanapoosanam Syncfusion Team November 26, 2021 01:17 AM UTC

Hi Cosme Morales Picon, 
 
We have confirmed the reported issue as bug in UWP platform and we will update the feedback bug report details and the fix timeline on November 26, 2021.  
 
Regards, 
Devakumar D 


DD Devakumar Dhanapoosanam Syncfusion Team November 29, 2021 03:56 PM UTC

Hi Cosme Morales Picon,

Sorry for the delay. We have logged reported issue as a bug “RangeChanged event is not updated when multiple SfDateTimeRangeNavigator are on the same page” in UWP platform and the fix for the reported issue will be available in our upcoming weekly NuGet release which is expected to be roll out on November 30, 2021. We appreciate your patience until then. We will let you know once it gets rolled out.


Note: The provided feedback link is private, and you need to login to view this feedback.

If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal.

Regards,
Devakumar D



DD Devakumar Dhanapoosanam Syncfusion Team November 30, 2021 08:49 AM UTC

Hi Cosme Morales Picon, 
 
We are glad to announce that our weekly NuGet was rolled out and fix for the reported issue was included in the weekly NuGet.  
 
NuGet Version: 19.3.0.56 
 
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 
   
Regards, 
Devakumar D 


Loader.
Up arrow icon