Hi Zeros,
Thanks and good luck.
Regards,
Ian.
Posted 12 August 2018 - 10:46
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 12 August 2018 - 10:52
Hi Zeros,
Just in case:
—
a) Add the font line to the section of the skin.
b ) Add the parameter lines to the section of the file.
—
Did you do that for me in the file you added?
The skin.xml and keymap.xml files have been edited with the changes so you, and others, can compare the files and see how the changes look in practice.
Regards,
Ian.
Posted 12 August 2018 - 10:57
Edited by zeros, 12 August 2018 - 11:01.
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 12 August 2018 - 20:11
I was comparing files with the original and bringing out changes in font and parameters.
My test is prepared and I will do it in tomorrow morning.
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 12 August 2018 - 21:30
I got the following text in GSOD:
--
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Components/ActionMap.py", line 49, in action
File "/usr/lib/enigma2/python/Plugins/Extensions/YouTube/YouTubeSearch.py", line 244, in openKeyboard
File "/usr/lib/enigma2/python/mytest.py", line 287, in openWithCallback
dlg = self.open(screen, *arguments, **kwargs)
File "/usr/lib/enigma2/python/mytest.py", line 297, in open
dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
File "/usr/lib/enigma2/python/mytest.py", line 240, in instantiateDialog
return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
File "/usr/lib/enigma2/python/mytest.py", line 264, in doInstantiateDialog
dlg.applySkin()
File "/usr/lib/enigma2/python/Components/GUISkin.py", line 154, in applySkin
File "/usr/lib/enigma2/python/Components/GUISkin.py", line 57, in createGUIScreen
File "/usr/lib/enigma2/python/Screens/VirtualKeyBoard.py", line 682, in buildVirtualKeyBoard
self.markSelectedKey()
File "/usr/lib/enigma2/python/Screens/VirtualKeyBoard.py", line 713, in markSelectedKey
self.list[self.selectedKey / self.keyboardWidth].append(MultiContentEntryPixmapAlphaBlend(pos=(x, 0), size=(self.key_sel.size().width(), self.height), png=self.key_sel))
AttributeError: 'NoneType' object has no attribute 'size'
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 13 August 2018 - 05:08
I add the place of the error.
def markSelectedKey(self):w, h = skin.parameters.get("VirtualKeyboard",(45, 45))if self.previousSelectedKey is not None:self.list[self.previousSelectedKey /12] = self.list[self.previousSelectedKey /12][:-1]width = self.key_sel.size().width()try:x = self.list[self.selectedKey/12][self.selectedKey % 12 + 1][1]except IndexError:self.selectedKey = self.max_keyx = self.list[self.selectedKey/12][self.selectedKey % 12 + 1][1]self.list[self.selectedKey / 12].append(MultiContentEntryPixmapAlphaTest(pos=(x, 0), size=(width, h), png=self.key_sel))self.previousSelectedKey = self.selectedKeyself["list"].setList(self.list)
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 13 August 2018 - 05:18
Hi Zeros,
Are you sure that you are using *my* "VirtualKeyBoard.py"? The source code you posted above is *not* my code.
The width of the keyboard grid is now 14 cells and not 12 and I don't use a hard coded width I use a variable.
Can you please check what code you are actually using.
Regards,
Ian.
Posted 13 August 2018 - 05:50
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 13 August 2018 - 13:50
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 13 August 2018 - 14:53
Hi Zeros,
The OpenPLi skins have a different layout than I expected. The "Directories.py" doesn't have the location rescue code of OpenViX and Beyonwiz. The images not being found is causing the crash.
I will update the installation kit, the instructions and the sample skin for you. That should address all the issues.
Regards,
Ian.
Posted 13 August 2018 - 15:25
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 13 August 2018 - 16:16
Hi Zeros,
Attached are the corrected files. You will need to install the keyboard images files into the correct location. Follow the updated instructions and the crash should go away.
Please note that I am unable and unwilling to change all the skins out there to match the new VirtualKeyBoard code. This should be done by the appropriate skin maintainers. The shin changes in the test kit are simply a guide on what could / should be done.
Regards,
Ian.
Posted 13 August 2018 - 20:56
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 13 August 2018 - 21:49
Official OpenPLi Skin are maintained here:
https://github.com/l...esat/skin-PLiHD
Won't it be better for testing to create your keyboard with an alternate name and screen name that won't try to reuse the existing one, and find a way to be able to select the keyboard that we want to use. I guess this will ease life of people willing to test your new keyboard layout.
Pr2
NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.
Wanna help with OpenPLi Translation? Please read our Wiki Information for translators
Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)
AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
Posted 14 August 2018 - 02:50
Hi Pr2,
Official OpenPLi Skin are maintained here:
https://github.com/l...esat/skin-PLiHD
Won't it be better for testing to create your keyboard with an alternate name and screen name that won't try to reuse the existing one, and find a way to be able to select the keyboard that we want to use. I guess this will ease life of people willing to test your new keyboard layout.
The idea is that the new VirtualKeyBoard is to be a drop in replacement for the old code. Modifying the code to support the co-existence of both versions would modify the conditions and defeat the purpose of these tests.
Once I get some more test results I will either address any remaining issues and retest or I will submit the code with a view to it totally replacing the old version.
Regards,
Ian.
0 members, 34 guests, 0 anonymous users