Hello,
next question about TMDb skin: size of star.png has been increased from 100x100 to 150x150 and it doesn't fit anymore to the screen. How I can scale it smaller to fit size 100x100 ?
EDIT : I fixed it by using scale="1"
<ePixmap position="e-400,165" size="100,100" zPosition="0" pixmap="/usr/lib/enigma2/python/Plugins/Extensions/tmdb/pic/star.png" transparent="1" alphatest="blend" scale="1"/>
Last edited by Orlandox; 20-08-23 at 16:56.
Huevos (20-08-23)
Hello,
how to this can be shown on 'SoftwareUpdateChoices' ? Now I can only see "Perform a settings backup," and on a second line just the top of "making a backup before updating"
https://github.com/OpenViX/enigma2/b...Update.py#L284
choices.append((_("Perform a settings backup,") + '\n\t' + _("making a backup before updating") + '\n\t' + _("is strongly advised."), "backup"))
Get a screengrab of the page.
But anyway if there is only room for one line it is not going to show.
And anyway it is crap breaking up a sentence like that. It should be one translatable unit with %s or line feeds inside the gettext.
It does not make sense having three lines of text in a list item. I've moved the the warning message to the end of self["text"]. You well need to tweak the translations.
https://github.com/OpenViX/enigma2/c...1033041804f454
Orlandox (07-09-23)
Thank you. Done that and it looks good now !
I was happy too soon. When you select '3', after that we have odd situation again: starting from line 350.
https://github.com/OpenViX/enigma2/b...Update.py#L350
Can it be fixed like this ?
Code:if answer[1] == "menu": if config.softwareupdate.updateisunstable.value == 1: message = _("The current update may be unstable.") + "\n" + _("Are you sure you want to update your %s %s?") % (getMachineBrand(), getMachineName()) + "\n(%s " % self.total_packages + _("Packages") + ")" elif config.softwareupdate.updateisunstable.value == 0: message = _("Do you want to update your %s %s?") % (getMachineBrand(), getMachineName()) + "\n(%s " % self.total_packages + _("Packages") + ")" choices = [(_("View the changes"), "changes"), (_("Upgrade and reboot system"), "cold")] if not self.SettingsBackupDone and not config.softwareupdate.autosettingsbackup.value and config.backupmanager.backuplocation.value: choices.append((_("Perform a settings backup"), "backup")) if isPluginInstalled("ViX") and not config.softwareupdate.autosettingsbackup.value and config.backupmanager.backuplocation.value: message += "\n" + _("Making a settings backup before updating is highly recommended.")
What exactly is the problem?
Same texts, but little differencies:
for example:
https://github.com/OpenViX/enigma2/b...wareUpdate.py#L354 -> message = _("Do you want to update your %s %s ?") % (getMachineBrand(), getMachineName()) + "\n(%s " % self.total_packages + _("Packages") + ")"
https://github.com/OpenViX/enigma2/b...wareUpdate.py#L269 -> message = _("Do you want to update your %s %s?") % (getMachineBrand(), getMachineName()) + packagesMsg
Then this is too long to fit : https://github.com/OpenViX/enigma2/b...wareUpdate.py#L358 -> choices.append((_("Perform a settings backup, making a backup before updating is strongly advised."), "backup"))
Now it needs double translations, because small differencies (i.e. space missing).
Try this version.
The whole thing is horrible though from a translation point of view. It is all split into small units so the translator has no control over the order.
deltec (07-11-23)
Now everything looks good, thank you.
deltec (07-11-23)
Hello,
I tried ColorButtonsSequence and ButtonSequence. Can I define more buttons on ButtonSequence ? And some screens are missing buttons. For example "PluginBrowser" is missing key_left, key_0 and key_right. Also "EPGSearch" is missing key_info and key_menu. So they must be added manually and ButtonSequence looses its meaning.
So is it possible to add those buttons to python code ?
The buttons in ButtonSequence (e.g. TEXT, MENU, HELP, INFO) lead to other screens. In contrast, the buttons you are talking about in PluginBrowser are just a list sorting function. And also the key_0 is an exception being displayed there (no other screen uses that), so personally I don't think those hooks should be added to the python code. Where they are buttons that open other screens they have already been added everywhere in enigma python code (as far as I know).
As for EPGSearch that should be fixed, but unfortunately we don't have write access for every plugin.