6 Commentsto I noticed, that in a container on first load the resumed event is sometimes, but not always fired…

1. Anonymous says:

   July 22, 2014 at 6:17 am

   < ![CDATA[

   Would you have some hints on the context where it is not fired ?

   ]]>

   Reply
2. Anonymous says:

   July 22, 2014 at 12:16 pm

   < ![CDATA[

   I’m sorry. I just wrote a script to test, and it is fired every single time. So nothing is wrong.

   
   

   
   

   It seems to be a bug in my app drawer script… Now I have to find it

   ]]>

   Reply
3. Anonymous says:

   July 22, 2014 at 12:54 pm

   < ![CDATA[

   Pierre Hébert I have discovered, that this bug is caused by container.getWidth and container.getCellWidth, which both return 0 on first resume event after restart LLX

   
   

   Probably the height methods are also not working…

   ]]>

   Reply
4. Anonymous says:

   July 22, 2014 at 6:58 pm

   < ![CDATA[

   Aaaaaah! So that’s the bug I have on one of my scripts!

   
   

   Now all make sense. I can confirm it.

   ]]>

   Reply
5. Anonymous says:

   July 23, 2014 at 5:46 am

   < ![CDATA[

   I am sorry if this does not work as expected, but this is not a bug. Android send various events and allocate screen space in asynchronous order. LL relay events in the same order, the consequence is that the views may not have received a size yet. It is really not possible to delay the emission of events until a size is set, so at the moment I don’t know how to solve the issue.

   
   

   I think it has been discussed earlier but I don’t recall whether this was linked with size.

   ]]>

   Reply
6. Anonymous says:

   July 23, 2014 at 5:53 am

   < ![CDATA[

   It was the discussion about load event, I thought resume would be something other…

   ]]>

   Reply