This is an incomplete solution. Any issue with the production skins will require the emergency skin to be available. If the emergency skin does become activated the issues will still be there.
Regards,
Ian.
This is an incomplete solution. Any issue with the production skins will require the emergency skin to be available. If the emergency skin does become activated the issues will still be there.
You think?? You're pretty much stating the obvious there.
The default_skin is not simply a repository of images. It is a fully fledged and viable skin. In fact in all the other images it is known as the emergency skin. This skin is used as a fallback should any of the nominated skins fail to load. It also has a significantly more important role. This skin provides screen definitions for all key screens in Enigma2. Any core screen that is not represented in the current skin will be provided by the emergency skin.peteru wrote: ↑Mon Apr 06, 2020 17:06The "default skin" is only used to provide some graphic elements to code that has paths to skin_default hardcoded and to third party plugins that have not been skinned in the Beyonwiz skins (although most of the time these have embedded skins anyway). It is not a full skin solution for the firmware and it was never intended to be so.
With the knowledge and experience I now have working with OpenATV, OpenPLi, OpenViX and the other images working with me I now appreciate how wrong is this comment.peteru wrote: ↑Mon Apr 06, 2020 17:06The Beyonwiz firmware requires skinning features that are simply not supported by skins that are not specifically developed and maintained for the Beyonwiz firmware. The About screen is one such example, but there are many other instances scattered through the code base.
All the images have their own "custom" experience. That is no way negates the need to have a properly working emergency skin.peteru wrote: ↑Mon Apr 06, 2020 17:06This is intentional, to provide a custom Beyonwiz user experience. The entire reason why the Beyonwiz distro was created (way back before I inherited it) was to provide a user experience that was different enough from the other distros that a simple re-skin was not possible.
It really pains you to have to reply to me. Too bad, deal with it!peteru wrote: ↑Mon Apr 06, 2020 17:06I think the issue here is that the author of OverlayHD is putting the cart before the horse. Third party skins are an optional extra and it is the responsibility of the skin authors to make skins compatible with the images that they purport to support. Not the other way around.
And here is your real problem. You constantly rejected my efforts and refused to accept my code submissions. I was a keen and vigilant supporter of the Beyonwiz firmware. You told me that my changes were making Beyonwiz firmware different from upstream and making you task of merging from upstream more difficult. You then directed me to stop making changes to the Beyonwiz firmware and instead make them to the upstream repositories. You assured me that when I could get my changes accepted you would then merge them. That has never happened. The massive merge and update task with which you don't want to deal is one of your own making.peteru wrote: ↑Mon Apr 06, 2020 17:06I am tired of the constant tirade about this topic as well as other disparaging comments about the firmware. This seems to have escalated again lately. The source code is out there and anyone is free to fork it. If someone is interested in making progress faster than I can, they can do an upstream merge (and I mean a full merge with commit history, not just a source code dump), conflict resolution, testing and then they can submit a pull request with the commented merge resolution commit history. If they are not willing to do that work (and there's a lot to be done), then they should stop whining.