Winkit : How to ensure a usercontrol is visible / or how to find out why it isn't Cancel The title field is required!

1. Carl Verbiest

   

   59 posts
   Registered:
   12 Oct 2018
   08 Jun 2020

   Link to this post

   I'm not sure if Winkit questions can be posted in the SCL forum.
   
   We have a winkitted screen where we replace an ABL rectangle with a User control containing a .Net control. The control does not appear
   
   When I query the visible attribute of the usercontrol is shows false.
   When I set it to true, I get no error but it remains false.
   Calling Show() does not help either.
   
   In other winkit screens the control shows(*).
   
   Do you have any helpers to force a control to be visible ?
   Do you have helpers / techniques to find out why a particular control does not show ?
   
   (*) the other screens are all using another variant of Embeddedwindow form
   
2. Mike Fechner

   

   319 posts
   Registered:
   14 Sep 2016
   08 Jun 2020 in reply to Carl Verbiest

   Link to this post

   This is difficult to answer without knowing the layout of the screen.
   
   I generally would investigate what the UserControl is parented to and if that's visible and the Location of the UserControl in the parent.
   
   I would use "funky" colors to make sure you'd see the control on the screens. In extreme cases, I have also added a PropertySheet to the Form to change properties of the control(s) in Question at runtime. 
3. Carl Verbiest

   

   59 posts
   Registered:
   12 Oct 2018
   09 Jun 2020 in reply to Mike Fechner

   Link to this post

   The visible attribute is false, but it remains false after setting it to true.
   No error is being thown.
   I'll try the propertysheet approach
   
4. Mike Fechner

   

   319 posts
   Registered:
   14 Sep 2016
   09 Jun 2020 in reply to Carl Verbiest

   Link to this post

   Anything special about the screen layout?
5. Carl Verbiest

   

   59 posts
   Registered:
   12 Oct 2018
   09 Jun 2020 in reply to Mike Fechner

   Link to this post

   Yes,
   
   It occurs on our EmbeddedWindowReportForm which has
   * a predefined ribbon for printer selection
   * a predefined panel for storing selections
   * extra panels where the selection frames of the original window are hosted