Jump to content


Photo

autotimer-problem with newest series-plugin


  • Please log in to reply
10 replies to this topic

#1 erice

  • Senior Member
  • 39 posts

0
Neutral

Posted 17 February 2016 - 19:24

hello

the current autotimer on the feed is not compatible with the newest series-plugin by betonme (popup with info).

greetings

eric



Re: autotimer-problem with newest series-plugin #2 Dimitrij

  • PLi® Core member
  • 10,336 posts

+352
Excellent

Posted 17 February 2016 - 19:43

Where did you get this information?


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: autotimer-problem with newest series-plugin #3 erice

  • Senior Member
  • 39 posts

0
Neutral

Posted 17 February 2016 - 20:48

Where did you get this information?

the popup with the info appears on my system: autotimer is depreceated, please update

openpli4 with latest updates, autotimer from pli-feed (plugins), newest seriesplugin from github betonme, et9200, serienrecorder

it seems, that there is a new autotimer-version 4.08, the pli-autotimer is based on a former version (i think so)



Re: autotimer-problem with newest series-plugin #4 Dimitrij

  • PLi® Core member
  • 10,336 posts

+352
Excellent

Posted 17 February 2016 - 20:58

https://github.com/O...aster/autotimer


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: autotimer-problem with newest series-plugin #5 erice

  • Senior Member
  • 39 posts

0
Neutral

Posted 18 February 2016 - 00:32

????

betonme´s autotimer is now 4.0.9 (opendream/1 day old), his seriesplugin is 5.4.3 (2 days old)

when i use his autotimer instead of the one on OPENPLI, i get a greenscreen by entering the configuration (please see crashlog).

with the pli-version of autotimer seriesplugin makes a popup.

is it possible to modify the autotimer again?

thanks in advance

Attached Files



Re: autotimer-problem with newest series-plugin #6 littlesat

  • PLi® Core member
  • 57,242 posts

+702
Excellent

Posted 18 February 2016 - 07:33

Looks like a bug in that 3rd party autotimer... I would recommend use PLi's one instead...

   464.414>   File "/usr/lib/enigma2/python/mytest.py", line 200, in processDelay
<   464.416>     callback(*retval)
<   464.417>   File "/usr/lib/enigma2/python/Plugins/Extensions/AutoTimer/AutoTimerOverview.py", line 283, in menuCallback
<   464.419>     editingDefaults = True
<   464.420>   File "/usr/lib/enigma2/python/mytest.py", line 289, in open
<   464.423>     dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
<   464.424>   File "/usr/lib/enigma2/python/mytest.py", line 232, in instantiateDialog
<   464.426>     return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
<   464.427>   File "/usr/lib/enigma2/python/mytest.py", line 249, in doInstantiateDialog
<   464.429>     dlg = screen(self, *arguments, **kwargs)
<   464.430>   File "/usr/lib/enigma2/python/Plugins/Extensions/AutoTimer/AutoTimerEditor.py", line 422, in __init__
<   464.436>     AutoTimerEditorBase.__init__(self, timer, editingDefaults)
<   464.436>   File "/usr/lib/enigma2/python/Plugins/Extensions/AutoTimer/AutoTimerEditor.py", line 181, in __init__
<   464.438>     self.createSetup(timer)
<   464.439>   File "/usr/lib/enigma2/python/Plugins/Extensions/AutoTimer/AutoTimerEditor.py", line 185, in createSetup
<   464.441>     self.name = NoSave(ExtendedConfigText(default = timer.name, fixed_size = False))
<   464.443>   File "/usr/lib/enigma2/python/Plugins/Extensions/AutoTimer/AutoTimerEditor.py", line 79, in __init__
<   464.444>     mapping[0] += ";"
<   464.445> TypeError: 'tuple' object does not support item assignment

Edited by littlesat, 18 February 2016 - 07:35.

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


Re: autotimer-problem with newest series-plugin #7 Dimitrij

  • PLi® Core member
  • 10,336 posts

+352
Excellent

Posted 18 February 2016 - 08:00

 

????

betonme´s autotimer is now 4.0.9 (opendream/1 day old), his seriesplugin is 5.4.3 (2 days old)

when i use his autotimer instead of the one on OPENPLI, i get a greenscreen by entering the configuration (please see crashlog).

with the pli-version of autotimer seriesplugin makes a popup.

is it possible to modify the autotimer again?

thanks in advance

 

Version openPLi same as betonme autotimer version with regard to seriesplugin,only one exception not plugin version https://github.com/o...c/plugin.py#L21

I can add this to the code, but really that's the problem?

Can you ask about it betonme?

 

P.S.don't use ihad version it is incompatible pli


Edited by Dimitrij, 18 February 2016 - 08:04.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: autotimer-problem with newest series-plugin #8 Dimitrij

  • PLi® Core member
  • 10,336 posts

+352
Excellent

Posted 18 February 2016 - 09:22

Ok.

found

https://github.com/b...sPlugin.py#L123

In the evening, do a patch, wait ...


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: autotimer-problem with newest series-plugin #9 erice

  • Senior Member
  • 39 posts

0
Neutral

Posted 18 February 2016 - 11:54

Ok.

found

https://github.com/b...sPlugin.py#L123

In the evening, do a patch, wait ...

very fine,

thanks



Re: autotimer-problem with newest series-plugin #10 Dimitrij

  • PLi® Core member
  • 10,336 posts

+352
Excellent

Posted 19 February 2016 - 06:27

done


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: autotimer-problem with newest series-plugin #11 littlesat

  • PLi® Core member
  • 57,242 posts

+702
Excellent

Posted 19 February 2016 - 08:04

But now we still need good builds and feeds.... So please hold-on!


Edited by littlesat, 19 February 2016 - 08:04.

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



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users