Jump to content


Photo

merge requests for PLi's git


  • Please log in to reply
1748 replies to this topic

Re: merge requests for PLi's git #621 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 August 2014 - 16:26

@athoik

 

would you please test patch level 62 for dreambox STBs ?

 

so if it is ok use kernel 3.2.62 for them


Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #622 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 14 August 2014 - 16:59

Last time i checked 3.2.61 and it was ok. Since 3.2.61 there are no MIPS changes, so probably 3.2.62 will work just fine.

Actually dvb drivers should upgraded for all DMM models (new drivers are out more than a month), i will provide a patch soon.
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: merge requests for PLi's git #623 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 20 August 2014 - 11:42

In this commit has been added a groupwise sort mechanism: http://sourceforge.n...1f1d4489b56c6c/

But it is forgotten that in skin, in widget movie_sort, also need to add the icon to display groupwise sort.
This patch in skin_default, at the end of movie_sort added additional newtop.png, to display  groupwise sort.
I do not know, maybe need to create a new icon for this, but in my opinion newtop represents the same, and they can be used.

 

Remember that this icon needs to be added also in skins of the image, for example in PLiHD.

Attached Files



Re: merge requests for PLi's git #624 littlesat

  • PLi® Core member
  • 57,187 posts

+699
Excellent

Posted 20 August 2014 - 18:57

Thanks for the icon.... The commit explained that we still need an icon....

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: merge requests for PLi's git #625 captnoord

  • Member
  • 22 posts

+10
Neutral

Posted 21 August 2014 - 12:01

replaced mix of type integer typedef's with the supplied ones from stdint.h

 

__u8 -> uint8_t

__u16 -> uint16_t

__u32 -> uint32_t

 

https://github.com/C...ed-integer-type

 

some parts of the code where already using those, some where not.



Re: merge requests for PLi's git #626 captnoord

  • Member
  • 22 posts

+10
Neutral

Posted 21 August 2014 - 18:43

hmmm cherrypick the commit might be easier:

https://github.com/C...73400578d95df5d



Re: merge requests for PLi's git #627 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 22 August 2014 - 10:10

replaced mix of type integer typedef's with the supplied ones from stdint.h

 

__u8 -> uint8_t

__u16 -> uint16_t

__u32 -> uint32_t

 

https://github.com/C...ed-integer-type

 

some parts of the code where already using those, some where not.

Cool! Exactly what I like to see. Stdint is good. Will cherry-pick.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: merge requests for PLi's git #628 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 23 August 2014 - 18:28

Commited.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: merge requests for PLi's git #629 captnoord

  • Member
  • 22 posts

+10
Neutral

Posted 24 August 2014 - 22:40

Thanks...

Re: merge requests for PLi's git #630 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 2 September 2014 - 18:39

If in the channel list I called menu, then in log, I have several errors:

[ePNG] couldn't open /usr/share/enigma2/skin_default/buttons/key_.png 

The reason is that the in ChoiceList, in ChoiceEntryComponent is called LoadPixmap while not the quick keys to display.
Here is patch which adds an additional key check, and if it does not exist, then do not use LoadPixmap.
But maybe this needs to discuss?
Maybe is skin which has its own key_.png, which is displayed when there is no quick keys? Then this patch will break them.

Attached Files



Re: merge requests for PLi's git #631 MiLo

  • PLi® Core member
  • 14,055 posts

+298
Excellent

Posted 7 September 2014 - 14:12

Good idea, no need to attempt to load images that don't exist.

While at it, using "%s" instead of +key+ in the string formatting will prevent a crash when key is not a string. I'll push something equivalent.


Real musicians never die - they just decompose

Re: merge requests for PLi's git #632 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 7 September 2014 - 14:41

Thanks.



Re: merge requests for PLi's git #633 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 7 September 2014 - 14:51

I found another place where looking for images that do not exist.

It is in Screens/LanguageSelection, where searches firstly png with file in the name, instead of index.
I wanted to offer a patch, but then I thought that it was wororound, to use own png.
But does anyone really use its own country flags, instead of the enigma?



Re: merge requests for PLi's git #634 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 7 September 2014 - 16:33

Maybe someone is interested.
Why can not delete services in all channel lists (providers, satellites, all ...)?
I understand that these lists as a database, from which build a bouquets, but if they are repeating or non-working channels, would be good to delete them, to creating a bouquet such of on computer, could be used only channels that work.

But check whether the channel works, is possible only in the all channel list.
This patch is added to possibility completly delete channels in general (not bouquets) lists.

Attached Files



Re: merge requests for PLi's git #635 littlesat

  • PLi® Core member
  • 57,187 posts

+699
Excellent

Posted 7 September 2014 - 17:56

Thanks, applied....


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: merge requests for PLi's git #636 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 7 September 2014 - 19:19

Thanks



Re: merge requests for PLi's git #637 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 8 September 2014 - 11:32

This function defies the whole concept of enigma2. We've had the discussion quite a few times. The "all channels" is what it says "all channels" and not "your own master bouquet". The background scanning will replace the services you deleted anytime. When you install a new servicelist or do a scan yourself, all services will be initial as well.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: merge requests for PLi's git #638 littlesat

  • PLi® Core member
  • 57,187 posts

+699
Excellent

Posted 8 September 2014 - 13:47

Did we already apply #623?

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: merge requests for PLi's git #639 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 8 September 2014 - 14:28

This function defies the whole concept of enigma2.

Exactly. Beats me why anybody would be interested in (changing) the all-services list?
It's a database for the box; no need to use the list yourself.

Re: merge requests for PLi's git #640 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 8 September 2014 - 14:55

Did we already apply #623?

No, I understand that you expect a new icon instead of using the existing one.

 

This function defies the whole concept of enigma2.

Exactly. Beats me why anybody would be interested in (changing) the all-services list?
It's a database for the box; no need to use the list yourself.

But you can simply not use it.
A large part of what I suggest, I personally do not use, but it has asked for users, for which it is very important.




35 user(s) are reading this topic

0 members, 35 guests, 0 anonymous users