77 replies to this topic

[Rob van der Does]

You only have to ask if you want some information.

Good to hear that, but that doesn't make up for VTi being closed source, which is against the VU⁺ license and hence illegal.

[plnick]

The python function is called from listboxservice.cpp (I wrote servicelist.cpp in my previous post, that was a fault) as  ePyObject that's all

[littlesat]

Then come with the servicelist.cpp source  I would like to know how how you did call ePyObject....

 

But in between I committed a different solution without swapping to a helper in python...

Edited by littlesat, 23 July 2014 - 19:01.

[plnick]

int is_recording = 0;
		if ((show_rec_service || show_rec_icon) && isPlayable)
		{
			ePyObject pArgs = PyTuple_New(1);
			PyTuple_SET_ITEM(pArgs, 0, PyString_FromString(ref.toString().c_str()));
			ePyObject pRet = PyObject_CallObject(m_recservice_fnc, pArgs);
			Py_DECREF(pArgs);
			if (pRet)
			{
				is_recording = PyInt_AsLong(pRet);
				Py_DECREF(pRet);
			}
			if (is_recording && show_rec_service)
			{
				if (m_color_set[serviceRecordingColor])
					painter.setForegroundColor(m_color[serviceRecordingColor]);
				else
					painter.setForegroundColor(gRGB(0xB40431));
			}
		}

 

 

void eListboxServiceContent::setRECServiceFunction(ePyObject func)
{
	if (m_recservice_fnc)
		Py_DECREF(m_recservice_fnc);
	m_recservice_fnc = func;
	if (m_recservice_fnc)
		Py_INCREF(m_recservice_fnc);
}

 

 

As I wrote before, you will not use it due to your coding standards ...

Edited by plnick, 23 July 2014 - 19:05.

[Erik Slagter]

Dont try to mount shares that are not online so the box doesnt freeze 

 

i would love that feature.

We have had this discussion so many times before. Even if the mounting returns immediately, it would buy you nothing, because every access after that would still take ages. The mounting is not the problem. The problem is mounting and then "removing" the server in one way or another.

[Dimitrij]

littlesat

Thanks!

http://sourceforge.n...9c715ba080be70/

[littlesat]

So you did the same as I did for the picon renderer...

For the picon renderer I made this swap due to I prefer to use just one and the same python renderer....

 

In between alternatives should be also fixed... and (not tested yet) the you can check if a specific service is recorded now also from python...

...probalby this function needs to be relocated somewhere else, but for the time being I suggest this is OK for now.

Edited by littlesat, 23 July 2014 - 20:18.

[Rob van der Does]

Dont try to mount shares that are not online so the box doesnt freeze 
 
i would love that feature.

We have had this discussion so many times before. Even if the mounting returns immediately, it would buy you nothing, because every access after that would still take ages. The mounting is not the problem. The problem is mounting and then "removing" the server in one way or another.

Not when using 'autofs'.

[plnick]

I don't know what you did with picon renderer, this is a "standard" call which can be found at different places in e2 ....

 

So the topic "mark recorded services in servicelist" is solved and closed for me.

 

 

But I see no reason to call us lamers if you believe this is correct, then please delete my account here.

[Rob van der Does]

But I see no reason to call us lamers if you believe this is correct, then please delete my account here.

My dictionary doesn't even know the word. Nor does Google translate

But you agree that VTi has illegally made closed source of the open source they use as basis?

[Erik Slagter]

We have had this discussion so many times before. Even if the mounting returns immediately, it would buy you nothing, because every access after that would still take ages. The mounting is not the problem. The problem is mounting and then "removing" the server in one way or another.

Not when using 'autofs'.

Autofs relieves the symptoms by umounting after some time whenever a share is not used. As long as any file is open on the share though, which is often the case, it won't umount, so you're still screwed. Also autofs uses some timeout (I don't know what we use). IOW you may get lucky or you still may be screwed. It's not "the" solution.

[littlesat]

Thanks plnick.... with sharing that small part of your code we could at least use the same font color to mark recordings...

[Dimitrij]

But I see no reason to call us lamers if you believe this is correct, then please delete my account here.

Please accept apologies from everyone.

[plnick]

I accept apologies from everyone, but there is no reason to call us lamers (= idiots) without any action from us. Nobody of VTi was involved in this discussion here but we were called lamers  (see post of littlesat).

 

Please delete my account now !

Thank you !

[delavega]

Dont try to mount shares that are not online so the box doesnt freeze 

 

i would love that feature.

Then use 'autofs'.

didnt work

[delavega]

 

We have had this discussion so many times before. Even if the mounting returns immediately, it would buy you nothing, because every access after that would still take ages. The mounting is not the problem. The problem is mounting and then "removing" the server in one way or another.

Not when using 'autofs'.

 

Autofs relieves the symptoms by umounting after some time whenever a share is not used. As long as any file is open on the share though, which is often the case, it won't umount, so you're still screwed. Also autofs uses some timeout (I don't know what we use). IOW you may get lucky or you still may be screwed. It's not "the" solution.

exactely!

[Gi 9995 Owner]

Please accept apologies from everyone.

+1

I sincerely regret that I became the unwitting cause of the quarrel.

[hemertje]

I accept apologies from everyone, but there is no reason to call us lamers (= idiots) without any action from us. Nobody of VTi was involved in this discussion here but we were called lamers  (see post of littlesat).

 

Please delete my account now !

Thank you !

 

please accept our OpenPLi apologies to you

Littlesat did speak for him self, not on behalve of the OpenPLi team

[malakudi]

Lamer is a jargon or slang name originally applied in cracker and phreaker culture to someone who did not really understand what he or she was doing. Today it is also loosely applied by IRC, BBS, and online gaming users to anyone perceived to be contemptible. In general, the term has come to describe someone who is willfully ignorant of how things work.

http://en.wikipedia.org/wiki/Lamer

 

Maybe not lamers, since they do understand how enigma2 works. But indeed lamers since they don't understand how GPL works. And VU's enigma2 is a fork of DMM's enigma2, so licensed under GPL. Release your sources if you don't want to be called lamers.

 

 

 

[Rob van der Does]

But indeed lamers since they don't understand how GPL works. And VU's enigma2 is a fork of DMM's enigma2, so licensed under GPL. Release your sources if you don't want to be called lamers.

That is indeed what I was referring to. A clone of a very old DM-repos, when all E2 was still open source (GPL).

And VU even has that license on their website; to be obeyed by everyone using thier OI.

BTW: The same applies to BH. Very strange to see that although both VTi & BH have an easy job as they use 100% OI, while all PLi-based images have to work hard to get literally all VU-images to work....

Edited by SatKiekerd, 24 July 2014 - 03:56.