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 #1061 littlesat

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 18 February 2017 - 10:55

Thanks....

What you did with some parameters setting to None and then later when it is None catch the default I did not except... Sorry..

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


Re: merge requests for PLi's git #1062 tension

  • Senior Member
  • 119 posts

+4
Neutral

Posted 18 February 2017 - 23:26

Typo?

--- openpli4/openpli-enigma2/lib/python/Screens/RecordPaths.py
+++ openpli4/openpli-enigma2/lib/python/Screens/RecordPaths.py
@@ -168,7 +168,7 @@
 				self.entrydirname.value = res
 			if config.usage.allowed_timeshift_paths.value != self.lasttimeshiftdirs:
 				tmp = config.usage.allowed_timeshift_paths.value
-				default = self.instantrec_dirname.value
+				default = self.timeshift_dirname.value
 				if default not in tmp:
 					tmp = tmp[:]
 					tmp.append(default)


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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 19 February 2017 - 07:54

No....

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


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

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 19 February 2017 - 08:36

Check out the new cleanups :)


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


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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 19 February 2017 - 08:46

Omh...(£o£)

Edited by littlesat, 19 February 2017 - 09:00.

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


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

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 19 February 2017 - 10:24

And again more :)


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


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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 19 February 2017 - 10:45

It takes a lot of time..... Please "break" or calm down...

What you also can do is make one commit that just removes the ; at the end...

And one commit that just cleans the if's from not required ( )....

And one commit that contains if x != None to of x is not None:

And one commit for not required imports...

We just told you to make separate.... but somehow we have to get in the middle.... Now we clean up different types .... and by file we could have multiply cleanuptypes...

 

Keep it at one type of clean up..... and all that differs but in separate...


Edited by littlesat, 19 February 2017 - 10:50.

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


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

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 19 February 2017 - 11:28

pp, I am still not seeing patches broken down into small chunks AND DESCRIBED HERE. What you're doing here is "throwing over the fence".


Edited by Erik Slagter, 19 February 2017 - 11:28.

* 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 #1069 tension

  • Senior Member
  • 119 posts

+4
Neutral

Posted 19 February 2017 - 23:06

Why not?

 

Attached File  1_0_1_2197_5_13E_EEEE0000_0_0_0.jpg   75.34KB   4 downloads

 

 



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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 19 February 2017 - 23:22

Are you sure this is a bug?

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


Re: merge requests for PLi's git #1071 tension

  • Senior Member
  • 119 posts

+4
Neutral

Posted 19 February 2017 - 23:42

Yes. It should not get as timeshift dirname the style <default> which if selected crashes enigma.

I never used this timeshift setting, i looked for the bug after reading the code :) .



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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 20 February 2017 - 11:13

So it is OK as it is now?


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


Re: merge requests for PLi's git #1073 tension

  • Senior Member
  • 119 posts

+4
Neutral

Posted 20 February 2017 - 13:03

Yes. After that little fix playing with locationbox for adding or removing new/old timeshift paths, no more ends up with a fake entry in

timeshift dirname configselection box (fake named <default>, originating by a default value for instant rec dirname i presume).

Hi.


Edited by tension, 20 February 2017 - 13:06.


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

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 27 February 2017 - 14:48

https://github.com/O...nigma2/pull/799

https://github.com/O...lugins/pull/248

https://github.com/O...plugins/pull/11

 

Use 'is' and 'is not' instead of '==' and '!=' for 'None' values :)


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


Re: merge requests for PLi's git #1075 fairbird

  • Senior Member
  • 413 posts

+20
Neutral

Posted 28 February 2017 - 14:38

Hello all my friends ...

Can you please add some option to allow to change value of (self.progressBarWidth) in ServiceList.py ?!

As photos shown 

 

self.progressBarWidth = 100

 

Attached File  1.jpg   289.5KB   3 downloads

 

self.progressBarWidth = 52

 

Attached File  2.jpg   250.16KB   3 downloads

 

Because the default value is 52 and that value with some FHD skin if choose percentage doesn't appear correctly ..

 

Attached File  3.jpg   134.83KB   3 downloads

 

Thank you


DM500s
DM800

DM800se

DM920UHD


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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 28 February 2017 - 16:05

self.progressBarWidth can be defined by the skin... so the skin could reserve more room...


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


Re: merge requests for PLi's git #1077 fairbird

  • Senior Member
  • 413 posts

+20
Neutral

Posted 28 February 2017 - 17:54

Thank you my friend ..

Yes I know that .. But I'm ask if possible to add option and we can control of progressBarWidth.

Such as (Number of channels shown in channel selection list)


Edited by fairbird, 28 February 2017 - 17:55.

DM500s
DM800

DM800se

DM920UHD


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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 28 February 2017 - 18:15

Another config is not preferable... especially because the skin defines the space

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


Re: merge requests for PLi's git #1079 fairbird

  • Senior Member
  • 413 posts

+20
Neutral

Posted 28 February 2017 - 18:22

Thank you my friend


DM500s
DM800

DM800se

DM920UHD


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

  • PLi® Core member
  • 57,063 posts

+698
Excellent

Posted 28 February 2017 - 18:24

No real thanks I think because I'm in the withhold mode... :)

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



28 user(s) are reading this topic

0 members, 28 guests, 0 anonymous users