2018-10-09, 22:53
Fwiw, I have installed all the different versions of Titan. All of them have the resolution change problem when quitting an external player and they are useless. All of them.
Quickly switching to Estuary, the problem does not occur.
I proceeded to try Aeon MQ7 for Kodi v18 Leia. It too has the problem.
I then installed Aeon Nox SiLVO 5 for v.18. It does not have the problem and works as it should.
I adjusted nothing for any of these skins. Just installed and went directly to Avatar, played it briefly, and exited the MPC player.
A working skin returned me to KODI in focus ready for interaction.
A non-compliant skin reduced KODI to a quarter of its size in the top left corner and any attempt to interact resulted in a crashed app.
Not sure how many skins I'll have to go through to find more working ones? At least we know there is one besides Estuary.
As the RC of KODI v.18 draws nearer, perhaps many of these skins that think they are ready for prime time will update to fully working order. Maybe not.
I suppose there could be some gremlin in my system and my system alone that prompts this behavior in some skins but I doubt it. Nothing special going on here afaict.
Quickly switching to Estuary, the problem does not occur.
I proceeded to try Aeon MQ7 for Kodi v18 Leia. It too has the problem.
I then installed Aeon Nox SiLVO 5 for v.18. It does not have the problem and works as it should.
I adjusted nothing for any of these skins. Just installed and went directly to Avatar, played it briefly, and exited the MPC player.
A working skin returned me to KODI in focus ready for interaction.
A non-compliant skin reduced KODI to a quarter of its size in the top left corner and any attempt to interact resulted in a crashed app.
Not sure how many skins I'll have to go through to find more working ones? At least we know there is one besides Estuary.
As the RC of KODI v.18 draws nearer, perhaps many of these skins that think they are ready for prime time will update to fully working order. Maybe not.
I suppose there could be some gremlin in my system and my system alone that prompts this behavior in some skins but I doubt it. Nothing special going on here afaict.