Regression/Crash in C1FlexGrid .537 in "Tree.Sort"

Regression/Crash in C1FlexGrid .537 in "Tree.Sort"

Posted by: wknauf on 25 January 2022, 12:24 am EST

• 

  wknauf

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 25 January 2022, 12:24 am EST

  Hi C1,

  see attached sample: GridTreeCrash.zip

  It crashes in the call to “C1FlexGrid.Tree.Sort” with this exception:

  System.NullReferenceException
    HResult=0x80004003
    Message=Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
    Source=C1.Win.C1FlexGrid.4.5.2
    StackTrace:
     at C1.Win.C1FlexGrid.Node.#kMn(Node #Nwf, IComparer #G5f)
     at C1.Win.C1FlexGrid.GridTree.#1sf(Int32 #epd, IComparer #G5f, SortFlags #ipj, Int32 #g0b, Int32 #h0b)
     at C1.Win.C1FlexGrid.GridTree.Sort(Int32 level, IComparer comparer)
     at GridTreeCrash.Form1..ctor() in c:\temp\GridTreeCrash\GridTreeCrash\Form1.cs:line 34
  

  Is there any workaround? Is it caused by the way I create the grid?

  This is a major regression, as it blocks the update to .537 for us.

  And it would also block the update to Visual Studio 2022, as https://www.grapecity.com/forums/winforms-edition/c1-flex-grid-with-visual-s states that the new C1 version is required to support it.

  So, if this is a regression, please consider providing another hotfix release. If not, we could not migrate to Visual Studio 2022 until your next release 22v1.

  Best regards

  Wolfgang

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 26 January 2022, 5:40 pm EST

  Hi Wolfgang,

  We could observe the issue at our end. It seems like a bug, we have reported it to the development team. We will let you know as soon as we have an update.
  
  [Tracking ID: C1WIN-26628]

  If you are using NET4.5.2 controls, you can use the 21v3 (532 builds) release of C1 controls with VisualStudio 2022, if you are facing any issues please let us know.

  Regards
  
  Avnish

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 26 January 2022, 6:10 pm EST

  Hi Avnish,

  according to the linked post, the issue was still present on DEC 30 2021 in 21v3 and you wrote that the ETA is the 213 hotfix release (.537?). This sounds as if .532 (regular 21v3 release) still did not work with VS2022?

  Best regards

  Wolfgang

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 26 January 2022, 6:12 pm EST

  Hi Wolfgang,

  The issue was specific to NET4 controls if you are using the NET4.5.2 version of C1 controls then you should be able to use the 21v3 release NET4.5.2 C1 controls with the Visual Studio 2022 without any issues.

  Regards
  
  Avnish

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 26 January 2022, 6:21 pm EST

  Ah, thanks for the clarification! OK, so I will give VS2022 a try with .532.
  
  The 22v1 release will hopefully contain a fix for the Tree.Sort issue.

  Best regards

  Wolfgang

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 7 March 2022, 2:40 am EST

  Hi C1,

  what is the roadmap for this issue? Is a wrote it blocks us from upgrading to newer versions.

  Best regards

  Wolfgang

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 7 March 2022, 2:15 pm EST

  Hi Wolfgang,

  The fix for this issue will be included in the 22v1 release. The ETA for the release is near the end of March 2022.

  Regards
  
  Avnish

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 5 April 2022, 1:16 am EST

  I can confirm that bug was fixed in .548, many thanks!

  Best regards

  Wolfgang

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 5 April 2022, 3:12 pm EST

  Hi Wolfgang,

  The issue has been fixed in the 2022v1(548) release. Please let us know if you still face any issues.

  Kind Regards,
  
  Kartik