Skip to main content
pshashipreetham
18-Opal
pshashipreetham18-Opal
18-Opal
May 29, 2023
Question

Collection Widget Height is not Responsive.

  • May 29, 2023
  • 1 reply
  • 2776 views

Hi there,

 

Collection Widget is placed in a Responsive Mashup, but Collection Widget Height is Static. It won't get responsive.

 

How can Collection Widget Height be responsive based on the number of Cells present in it?

 

Thanks,

 

1 reply

V
VVM_410-Marble
10-Marble
May 29, 2023

Hi @pshashipreetham ,

 

Is the view property of the collection widget set to "flow" or "table"? Are the cell mashups fixed or responsive?

 

Usually when a collection widget is placed in a responsive container, it will take the entire height and width of the container. Some screenshots of your mashup in the editor and at runtime would be useful to further understand the issue you are facing.

 

Please note, there is a cell height and width property property present, that you can adjust. The collection widget will not adjust this directly. So, given the real estate you have, you should programmatically adjust the cell height if you want everything to fit and no collection widget scrollbar to appear. (e.g. if the view is "table" and you have 500px of space and 10 rows in your collection data, then you need to programmatically adjust the cell height to 50px each.)

pshashipreetham
18-Opal
pshashipreetham18-OpalAuthor
18-Opal
May 30, 2023

Hi @VVM_4 ,

 

I adjusted the Cell Height Programmatically. It's about the Collection Widget, which has the static Height property when placed in the Responsive container. At the same time, other responsive Widget's Height Property Vanishes as soon as we drop them in the Responsive container.

 

How can I avoid the static Height Property of the Collection Widget in Thingworx?

 

The Collection Widget is set to Table.

 

Thanks,

V
VVM_410-Marble
10-Marble
June 9, 2023

Hi Shashi,

 

This is pretty weird behavior. The collection widget is responsive and I have never seen this happen.

 

The only time this should happen, is if the Positioning property of the container layout is set to "Static". If this is happening even though the positioning is "Responsive", then I would suggest raising a support ticket on this.

    Terms & ConditionsCookie settingsAccessibility statement