Posts by saragusa

    Good evening and congratulations for the beautiful image. It also runs very well on OpenSpa, but some elements of the 1st infobar frame are missing, as shown in the screenshot. Xtraevent present and active in the image.



    Modimg.jpg

    Ipk telnet code version don't work...


    Screenshot_2023-01-09-21-03-37-358.jpg

    Great Lululla ...👏👏👏


    I only point out the following differences compared to version 2.4:


    1. The MatriConfluencExp Menu - setup is missing (screenshoot 1 and 2);


    2. The info events do not appear in the infobar, above the covers (screenshoot 3);


    3. The genre events do not appear in the channel list, even though the OpenSpa image is higher than 7, ie it is 8.1.


    Thanks again for the great work.


    11 (1).jpg


    10 (1).jpg


    1_0_19_BBE_3A2_110_EEEE0000_0_0_0_20220626211331.jpg

    try now overwrite xml in folder skin

    if you can, since I did not understand some points, put an arrow (like the Indians) where the problem is

    Thank you

    Ok Lululla .

    If I understand correctly, i have to overwrite all the xml files present in the folder of the installed skin MetrixConfluenceExp (use/share/enigma2/) with correspondent xml files present in the folder of your attached zipped file MetrixConfluencExpXml-Pro-OpenSpa. That's right?

    Thank's Lululla .

    Here the report of test.

    Image: OpenSpa, 8.1 version py3.

    Skin installed: Your Last_skin_pro.zip

    1. problem positionersetup/motore setting: resolved (screenshot 1);

    2. virtualkeyboard OpenSpa: not resolved (screenshot 2);

    3. poster genre in channel list: not appears (screenshot 3);

    4. multichoice Channel list & infobar - Skinsetting Metrixconfluepro: not present (screenshot 4). Only channel list available is that of default, in screenshot 3;

    5- Transparent Epg not visibile in infobar up the cover (screenshot 5);

    6 - In dragon skin for OpenSpa, ver. 1.2, issues 2, 4 and 5 are resolved, issues 1 and 3 not resolved (ipk skin file attached).

    IMG_20220709_121305.jpg


    IMG_20220709_123609.jpg


    IMG_20220709_121225.jpg


    IMG_20220709_121247_5CS.jpg


    IMG_20220709_122830.jpg

    update skin x openspa 8.0 py3 vers 1.3

    x the problem of the motor I can not understand the problem not having the motor


    update skin x openspa 8.0 py3 vers 1.3

    x the problem of the motor I can not understand the problem not having the motor

    Hi dragon .

    The "positionersetup" system plugin is identical for all skins for ATV image. Just change the template. If you replace in xml file of your OpenSpa version skin, the "positioner setup" script of the last version Lululla skin, i think the problem will be solved. I'm not a skinner, otherwise i would have already done it ... I can be a betatester if you want ...👍👍👍

    Ok. Clear. I thought that you, having already solved the problem for ATV image (and your last version skin works perfectly with OpenSpa image, except for the virtualkeyboard ...) you could easily solve it for OpenSpa as well. That's all.. Maybe he could check out dragon ... if he has time ... :upside down face:

    Ok. But i think the problem is the same of that it was for your 2.2 skin version and that you solved with 2.3. Starting from dragon 1.2 version (last version for OpenSpa), can't you go back to the positionersetup script? Basically it's the same as the atv skin (yours), only the virtualkeybord template changes, and obviously you don't touch that ... I can be a betatester, if you want ...

    Hi Lululla , hi dragon ,

    i noticed that the "positioner setup" systemplugin is not implemented in the skin. Or better... It exists and is installed by default, but the options in that plugin don't work.... This is a big problem because it's a fundamental plugin for those (like me...) that have a motorized system... Could you take a look please?

    try


    v.2.3

    Ok, thank's Lululla . Problem "positioner setup" is solved. The only problem, now, is the virtualkeyboard, that in my image (OpenSpa 8.0) appears as in the attached screenshot. I know for OpenSpa is necessary dragon version (1.1 ver.), but it shows the "first" problem "positioner setup"...


    IMG_20220704_081639.jpg

    a little update (fix color button and xCaid)

    Excuse me @dragon@, is it normally compatibile by OpenSpa?

    hello the skin 1.1 specific x openspa 8.0 py3 the virtualkey problem has been solved ... that's why I released 1.1 ...

    not to be confused with the versions x openatv .. I specified it as the attached version 1.1 specifies x openspa8.0 in py3 only x that versio

    Yes, of corse @dragon@, I knew ... But I thought that the latest change made by Lululla in the ATV 2.1 version (fix PosterX, fix rendering, etc.) were compatible with OpenSpa. That's all...

    Hi biko .

    Can you solve the incompatibility problem of your skin with OpenSpa virtualkeyboard, pls? Issue occours when your skin is installed on OpenSpa image, py2 and py3 version. Same problem also exists for KIII and Dragon skins... In attach two screenshoot of the problem...

    Thank's...


    P.S.:

    In this skin:


    https://mega.nz/file/NZ1hHRLI#X9IhHYgcVN00jYbp0l8vEOA2vvX_r0GnghM7bRoRL4o


    the problem is already resolved...😉


    IMG_20220622_090943.jpgIMG_20220622_090932.jpg

    Same problem for me: same poster for now and next event... But, sorry biko , ... but this problem was not solved ??



    Congratulations for the great job ...

    I have only one observation to make: in the motor configuration menu (Main Menu - Reception-Positioner setup), only the first configuration function (highlighted-yellow arrow) works and all the others are not implemented, as indicated by the red arrows in the attached photo. Could you solve the problem? Thank you.

    6d9d83d44.jpg


    A thousand thanks. It works perfectly ... Only, i think, the font size and the overall optimization of the "positioner setup" screen should be adjusted (also the other screens in the "reception" menu should actually be 'adjusted' ...)....

    If all the screens were optimized like the one in the photo I attached in my previous post, it would be perfect ....


    Tank you again... :hello 1: