Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 15 of 129

Thread: OpenVix Custom EPG

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #11

    Title
    Forum Supporter
    Donated Member
    Join Date
    Jun 2014
    Posts
    1,321
    Thanks
    614
    Thanked 418 Times in 270 Posts
    Quote Originally Posted by abu baniaz View Post
    Are the following possible?
    I'll answer the questions in turn...

    1. Remove enigma2 from depends in control file. It is not required for install and I can't imagine anyone using this on an image that does not have enigma2
    I have removed this.

    2. Add Blue HD skin as a depends. This means that you will always install the current one from plugins server
    The problem with this is user may not actually want Blue HD skin installed. The plugin only replaces a modded skin .xml file.

    It would be easier if admin/mods were to allow these skin .xml changes to github and included in future Vix releases!?! I can confirm that using these modded skin .xml files without the plugin installed (or any other modded epg files) doesn't result in any errors/crashes or anything. It appears the skin just ignores widget names if it can't find them within the modded epg files. I'm happy to submit these few changes if okay with admin/mods?

    3. Try using Use epg_custom.png, else epg.png. This removes the need for one of the backing up processes
    See my proposal for question 2. This is better/easier option.

    4. Is there a possibility that the debug print comments can state that a modified version is being used. Makes it easier to diagnose issues.
    Good idea. I could only see one debug print statement which i've amended. I've also added the following debug statement to all plugin .py files:
    Code:
    [OpenVix Custom EPG] OpenVix Custom EPG is installed.....
    This then mentions the name of the file that is modded. Hopefully, this will aid with diagnosing issues as you can just search for "Custom EPG" in debug logs to see if/what modded epg file is being used, if any.

    5. As far as I can see, the removal process only deals with the .pyo files, not .py files. So removal is not complete. Workaround is to use .pyo files in ipk or to add the .py files in removal process
    The package provider, opkg, in this case handles removal of additional files installed when removed using opkg. I can confirm .py files are actually removed by opkg package.

  2. The Following 2 Users Say Thank You to bbbuk For This Useful Post:

    abu baniaz (28-05-16),Andy_Hazza (28-05-16)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.