Debug mode output logs.

When debugging my applications with SfSegmentedControl I receive a lot of messages:

09-14 12:13:25.241 W/View    (17475): requestLayout() improperly called by md552cceaad93f74aa004b5608c07905243.SegmentView{ad520af8 V.ED.... ......ID 309,0-462,60} during layout: running second layout pass
09-14 12:13:25.241 W/View    (17475): requestLayout() improperly called by md552cceaad93f74aa004b5608c07905243.ViewLayout{ad05cda8 V.E..... ......ID 0,0-463,60} during layout: running second layout pass
09-14 12:13:25.241 W/View    (17475): requestLayout() improperly called by md552cceaad93f74aa004b5608c07905243.SegmentView{ad51fb68 V.ED.... ......ID 1,0-154,60} during layout: running second layout pass
09-14 12:13:25.241 W/View    (17475): requestLayout() improperly called by md552cceaad93f74aa004b5608c07905243.SegmentView{ad5205c8 V.ED.... ......ID 155,0-308,60} during layout: running second layout pass

Is this normal ?

3 Replies

PA Paul Anderson S Syncfusion Team September 14, 2018 10:28 AM UTC

Hi Piotr,

Thank you for using Syncfusion products.

The reported background log will not cause any issue or performance lag and it is occurring from the Android Framework layouts while measuring the views and layouting in the background. We have also already logged an improvement task for the same.

We will clear these logs with the control and this improvement will be done in any of our upcoming release.

Regards,
Paul Anderson
 



PG Piotr Grzywa September 14, 2018 10:59 AM UTC

OK .


PA Paul Anderson S Syncfusion Team September 14, 2018 11:02 AM UTC

Hi Piotr, 
  
Thank you. Please get in touch if you required further assistance. 
  
Regards, 
Paul Anderson 


Loader.
Up arrow icon