86 replies to this topic

[Dimitrij]

mrvica

 

ver. 2.7 -add support fullhd skin (thanks mrvica)

https://github.com/D...bc19332edd3dbc5

[catastrofus]

When in the PLi feed?

[kadiro1312]

Please Sir:

*-  When in the PLi feed?????

[WanWizard]

After the next build, which I think is scheduled for tomorrow afternoon.

[catastrofus]

Nice!

[WanWizard]

Both OpenPLi 4 and OpenPLi 6.1 were succesfully build yesterday.

[mrvica]

			if config.plugins.SetupZapSelector.event.value == "2":
						#descriptionName = event.getShortDescription()
						descriptionName = event.getExtendedDescription()
						#if descriptionName is None or descriptionName == "":
						#	descriptionName = event.getExtendedDescription()
						if descriptionName is None:
							descriptionName = ""
					if config.plugins.SetupZapSelector.duration.value:

@Dimitrij, can you check the feed version once again, some hd screens are not working, (event name and description, duration type progress bar)

another issue, the description is not working with DVB-T, DVB-S ok, this patch fixes it (do not use short description), change this in plugin.py

 

 

 

[hispanico]

Sry guys but which is last version and where i can download last rel ?

 

Thank

Hispa

[Dimitrij]

 

Short description work fine for me.

Maybe:

					descriptionName = event.getShortDescription()
					if not descriptionName:
					  descriptionName = event.getExtendedDescription()
					if not descriptionName:
					  descriptionName = ""

 

can you check the feed version once again, some hd screens are not working, (event name and description, duration type progress bar)

Please show a screenshot of the settings and these channels

Edited by Dimitrij, 25 January 2018 - 21:07.

[mrvica]

I mean description width DVB-T, can you test DVB-T, DVB-S is ok with short description, the patch you suggested doesn´t work, the sam as before, I am here at the moment in Croatia and can test DVB-T, if someone else can confirm this, with extended description all ok, about the screens, just load one hd skin and try all screens, you´ll see it, by the way, hd screens are too small, take mines, I made both hd and fhd screens bigger

[Dimitrij]

For PLI-FULLHD skin not problem.

 

DVB-T,  short description...

please write text description

[catastrofus]

Bij PLi4 zie ik nog steeds de kleine variant van de "History Zap Selector"...

Terug van PLi6.1 na 2 volledige hangs (wel pingable maar niet inlogbaar) in 4 weken (2 x dvb-c waar een opname liep en 1 vrije dvb-c waar ik naar aan het kijken was) ben ik er eigenlijk wel helemaal klaar mee. Wat een kutzooi.

Waarom zie ik dan nog steeds die kleine "History Zap Selector" bij pli4? Uiteraard gebruik ik de PLiFullNightHD skin.

 

 

 

Both OpenPLi 4 and OpenPLi 6.1 were succesfully build yesterday.

Edited by catastrofus, 26 January 2018 - 21:32.

[WanWizard]

You are replying to an English language thread.

 

Primary requirement for something "stable" is that it doesn't change. So we don't make changes to a stable image, unless it is required (for example because of a serious bug) before the next release. And if nobody reports that a serious bug is fixed, its version in the stable build will not be updated.

[catastrofus]

Sorry, english thread. Thanks for your automated reply This answer will self destruct in 5, 4, 3, 2, 1 second!

[WanWizard]

Nothing automated about it.

 

If nobody asks, nothing happens. Don't expect us to read every post in detail, and expect us to understand what it is about, and that something needs to happen.

 

Someone has to give the release team a kick and ask for a repo rev to be updated.

[catastrofus]

Huh?

 

Nothing automated about it.

 

If nobody asks, nothing happens. Don't expect us to read every post in detail, and expect us to understand what it is about, and that something needs to happen.

 

Someone has to give the release team a kick and ask for a repo rev to be updated.

 

Sure, this was your remark:

 

Both OpenPLi 4 and OpenPLi 6.1 were succesfully build yesterday.

 

This is about the 'history zap selector':

 

After the next build, which I think is scheduled for tomorrow afternoon.

[catastrofus]

Ok, the build of the "History Zap Selector" failed for pli4? Because the required change isn't visible (and obviously will not be) after flashing pli4 and using autorestore? Yes, this zap selector is included within the autobackup...

It's just a question because one of the members (you!) said it will be visible for those guys running pli4. But I think I'm wrong or my expectations are too high.

[WanWizard]

Everything in a stable build is pinned on commit hash. So if a repository has new commits, they will not be used in the build until the hash is manually updated. This is because the stable build should contain only tested code, and the build must be reproducable.

This in comparison to the old "beta" images, where nothing was pinned, so you got a build with whatever was available at buildtime. Tested or not, broken or not. The current "develop" branch still follows that principle.

 

If I have given the impression I had done that, sorrry. Maybe I'd planned to do it, but I forgot. There are a lot of things going on privately, I don't have a lot of time for the hobby at the moment.

 

I will see if I can find the time this weekend for the build this Monday. Send me a reminder via PM so I don't forget (again).

[WanWizard]

Found it, I did update 6.1, but I didn't update 4. Which has now been done: https://github.com/O...ea9de05b9e08842

[first_damned]

Great plugin, Thank you


Sent from my iPhone using Tapatalk