45 replies to this topic

[Rob van der Does]

I am not sure where this reaction comes from.
 
The remark was that if you make something that is tightly integrated with Enigma, or should be tightly integrated with Enigma, don't make it a plugin, but integrate it?
 
That doesn't strike me as something you should become angry about?

Exactly!
I often notice such angriness in Ims's reactions on simple questions. No idea why that's the case.
Anyway: I never intended to offend anyone at all; I was just wondering and hence asked a question.


But now that I am asking: this is (as far as I know) the second time some private repos is being used for stuff that's (more or less) basic stuff for OpenPLi (the other one being Littlesat's skins).
That doesn't strike me as a good idea either; why not use the PLi-repos?

[Rob van der Does]

As the plugin has been modified, to behave like a real plugin (see https://github.com/i...00b3c85b481c83c  and https://github.com/OpenPLi/enigma2/commit/50bfe625941878272d05f0d461a90c813f51b687) I conclude that my questions were valid (although no answer was given on GITHUB).

 

But: the result is a crash on (up-to-date) PLi 6.2.

 

 enigma2_crash_1529552558.zip   4.54KB   4 downloads

 

 

[ims]

pears and apples

[Rob van der Does]

No idea what you mean, but the crash is real and makes MovieManager useless.

[ims]

On the other hand, you have saved the e2 code cleanness

[Rob van der Does]

I still have no idea what you mean, but the crash is still present and makes MovieManager useless.
Any chance for a fix?

[littlesat]

Traceback (most recent call last):

  File "/usr/lib/enigma2/python/mytest.py", line 208, in processDelay

    callback(*retval)

  File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 1208, in doneContext

  File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 2027, in do_moviemanager

  File "/usr/lib/enigma2/python/mytest.py", line 297, in open

    dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)

  File "/usr/lib/enigma2/python/mytest.py", line 240, in instantiateDialog

    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)

  File "/usr/lib/enigma2/python/mytest.py", line 257, in doInstantiateDialog

    dlg = screen(self, *arguments, **kwargs)

TypeError: __init__() takes exactly 3 arguments (4 given)

[littlesat]

Look like we need to give one argument less -or- arrange that the extra argument is accepted -or- arrange the argument is passed in some kind if different way.

[ims]

Nothing is needed ... Mister RvdD wants using 6.2 with develop plugin version. He mixes pears with apples, thats all !

[Rob van der Does]

@IMS: Why do you think that?

Mister RvdD is simply using release 6.2 with the MovieManager from the feeds. He hasn't made any modifications himself.
Is anybody really testing this on release?

[ims]

But in feeds is not 1,73 version. In feeds is pinned version from 03/2018 - see .

 

 

 

 

[Rob van der Does]

What can I say more then I already did: release 6.2 + MovieManager from the feeds. Nothing more, nothing less.

Does anybody actually test a release image with the plugin from the feeds?

[Rob van der Does]

Sorry, but it seems I uploaded the wrong crashlog.

Here's the correct one:  enigma2_crash_1529658125.zip   4.54KB   2 downloads

 

I'm very sorry about that

[WanWizard]

Does anybody actually test a release image with the plugin from the feeds?

 

Structurally? No. I wish we had a volunteer for that, but tedious jobs are not high on anybody's agenda it seems.

[ims]

It is same ... 6.2 version cannot run 1.73 version. MovieManager is from 1.73 standallone plugin. Call it with code in 6.2 is impossible. And as I saw into reporefs.conf for 6.2, in feeds must be version from 03.2018 only. Last version is for develop only...

[Rob van der Does]

It is same ... 6.2 version cannot run 1.73 version. MovieManager is from 1.73 standallone plugin. Call it with code in 6.2 is impossible. And as I saw into reporefs.conf for 6.2, in feeds must be version from 03.2018 only. Last version is for develop only...

I even de-installed the plugin, made sure there were no left-overs, and installed it again from the feeds. Only then I let the crash happen and retrieved the crashlog.

So yes, as I said multiple times now: this is what's on the PLi-6.2 feeds.

Did you actually try it, instead of denying the issue?

[ims]

I do not know how you, but I am still at work ... afternoon I wil try it.

[WanWizard]

I double checked, the version in the 6.2-release feed is enigma2-plugin-extensions-moviemanager_2.0+git20+30c22dc-r0.0, which is build from commit hash 30c22dc9a148bd0919b230563e91139201113361, which is dated March 10th 2018.

 

If that doesn't work, it is not related to any change in the plugin after that date.

[Rob van der Does]

 

It is same ... 6.2 version cannot run 1.73 version. MovieManager is from 1.73 standallone plugin. Call it with code in 6.2 is impossible. And as I saw into reporefs.conf for 6.2, in feeds must be version from 03.2018 only. Last version is for develop only...

I even de-installed the plugin, made sure there were no left-overs, and installed it again from the feeds. Only then I let the crash happen and retrieved the crashlog.

So yes, as I said multiple times now: this is what's on the PLi-6.2 feeds.

Did you actually try it, instead of denying the issue?

 

To be 200% sure I reflashed (online) and auto-restored the box: same crash (on trying to open the plugin)

Edited by Rob van der Does, 22 June 2018 - 13:00.

[Rob van der Does]

FYI: in ui.py it says 'VERSION = "1.43" ', which would indicate the build date 10-03-2018.