Solved <focusedlayout> memory/UI rendering bug issue with doModal and history stack - Help!
#1
I'm currently building a own light The Movie DB info script (similar to ExtendedInfo), but I'm facing a very strange and annoying UI issue.

Each dialog object is stored in a list/stack to generate a dialog history, which works well. But after 2-4 dialogs a container is getting weird and focusedlayout of that list is completely "invisible" for the first page. Hard to describe so I've made a video.
I'm out of ideas, because I simply don't know where the problem does came from. I hope that somebody can point me to the correct direction.



Timestamp where the issue appears: https://www.youtube.com/watch?v=g5pGtKIv...tu.be&t=29

Code of my dialog manager:
https://github.com/sualfred/script.embua...ain.py#L60

Debug log:
payofofofe.kodi (paste)
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#2
Totally strange. If I temporary increase the item and focusedlayout by 100 pixel in the width the issue is does not happen. And only for the container with images. What is this......
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#3
Ok, found the issue.

It's because close() doesn't deletes the window and each time it was reopened from stack it was passing onInit() again where I was adding items to the container controls. A simple self.first_load bool to check if it's the first time that this window is going to be loaded did the trick.
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#4
Thread marked solved.
Got a Kodi problem? Provide us with a full Debug log (wiki) || Usefull pages: First time user (wiki) || Troubleshooting (wiki) || Free content (wiki) || Forum rules (wiki) || VPN policy (wiki)
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
<focusedlayout> memory/UI rendering bug issue with doModal and history stack - Help!00