C1DockingTab layout restore does not work

C1DockingTab layout restore does not work

Posted by: wknauf on 27 January 2024, 3:42 am EST

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 27 January 2024, 3:42 am EST

  While trying to analyze a strange behavior with C1DockingTab layout restore in our real world app, I ran into a very strange problem, see attached sample.
  
  C1DockingTabLayoutRestore.zip

  Just open it, close it and open it again. Now, the C1CommandDock at bottom has a height of “0”, same for the C1CommandDock to the right and its width. Thus, they seem to be invisible.

  In our real app, this does not happen - but here, one of the tabs does not autohide properly. While trying to reproduce this problem, I stumbled with this new issue.
  
  The problem happens with .631 und .636.

  Probably it is some trivial error by me, but I don’t see it…

  Due to historical reasons, we have C1CommandDock/C1DockingTab on a UserControl instead of a form (don’t know why ), and restore the layout not in “OnLoad”, but in “OnVisibleChanged” (because errors could happen, and in this case we want to reset the stored layout and close the form, which is forbidden in “OnLoad”).

  Best regards

  Wolfgang

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 29 January 2024, 11:31 pm EST

  Hello Wolfgang,
  
  Thank you for bringing this matter to our attention.
  
  We were able to replicate the behavior at our end, so we have escalated it to the development team. We will give you an update as soon as we get any necessary information.
  
  Sorry, but we could not replicate the behavior where tabs do not autohide properly. Please refer to the attached GIF, autoHideTabs.zip. Could you please share the steps with us to replicate this behavior on our end?
  
  Regards,
  
  Uttkarsh.autoHideTabs.zip

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 30 January 2024, 12:04 am EST

  Sorry, the “not autohiding C1DockingTabPage” was an issue caused by our own code, and I could work around it meanwhile. I should have posted this information, sorry for the time you wasted to investigate this.

  Best regards

  Wolfgang

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 30 January 2024, 9:04 pm EST

  Hello Wolfgang,

  No problem at all! We appreciate your update and understanding.
  
  Collaboration is key, and we’re here to assist in any way we can. Thank you for keeping us in the loop, and there is no need to apologize — troubleshooting is part of the process!
  
  If you have any further questions or run into more issues, feel free to reach out.

  The reported behavior is a bug, according to the developers. Apologies, but there is no viable workaround for it.
  
  Rest assured, we’ll update you as soon as the issue is resolved.

  [Internal Tracking ID: C1WIN-31592]

  Regards,
  
  Uttkarsh.