104 replies to this topic

[littlesat]

The added tripple dragon stuff does not allow me to commit this...!!!!!

[betacentauri]

Strange! I don't understand that. Will try again this evening.
What error message do you get?
And you mean you cannot commit it to git. Or do you have problems to compile it?

[theparasol]

Litllesat just states you should wipe all tripple dragon stuff since this is an unsupported device and adding any code fur such devices is not granted by the team...

[littlesat]

I just did commit it... I had a different teletext patch on my pc...

[betacentauri]

Litllesat just states you should wipe all tripple dragon stuff since this is an unsupported device and adding any code fur such devices is not granted by the team...

 

Hi,

 

I didn't add new stuff for triple dragon. It is already included.

See commit:

http://sourceforge.n...c1bd51015b8d32/

[betacentauri]

I just did commit it... I had a different teletext patch on my pc...

 

Ah, that was the reason. Thanks!

[theparasol]

Well, this morning on my xp1000 after hitting the teletext its only reacting to buttons mute, volume up/down and thats it...

 

So for xp1000 users teletext is now broken.

[theparasol]

.... just a moment... could be my loss... almost sure of it

Edited by theparasol, 7 February 2014 - 10:10.

[jort38]

On my Vu+ duo I can still browse.

 

Added function volume up and down works now (happy!)

 

Donot know what else to test / check

[theparasol]

confirm my loss, just flashed the latest image for xp1000 works like a charm... reason was my gstreamer1.0 image not updated to latestest teletext changes, lets say half = broken...

[mge]

volume up / down works, but until this change I was able to change to split screen views with vol up / down. How can I do this now?

 

 

[don't know if split screen is the right word. That's what I mean: left side txt, right side live tv or 4:3 txt and little live tv on the right bottom side.]

[jort38]

Channel up / down

[mge]

thanks!

 

channel down ==> split screen

channel up ==> small type / large type

[quad]

Betacentauri, I would like to use this on my Gigablue Quad with the openATV image. Browsing their git repository, I could see that you have checked in at least parts of your "teletext improvements" there, e.g. in https://github.com/o...s/tuxtxtapp.cpp . But I doesn't seem to work with openATV, and I could not event find "Tuxtxt" at https://github.com/o...gins/Extensions to check what may be missing. Do you think you could have a look and add what is necessary? Thanks a lot ...

[betacentauri]

Hi,

I need to speak with Captain about it. It's a little bit difficult because ALL teams using oe-alliance core need to adapt their enigma2 sources. If they don't do it, teletext is broken. And it's difficult to say every team needs to do it at the same day.
But I have an idea. I hope Captain likes it...

By the way. Does teletext still work in the OpenATV image?

Edited by betacentauri, 23 February 2014 - 18:23.

[quad]

It'n not broken yet in openATV

[betacentauri]

Again offtopic:

It's included tomorrow in OpenATV 4

[ims]

I think, changes in TXT (in last month?) corrupt something there in E2, when are used picons in oled.

When I go (DM800SE) to teletext and then I close teletext, there is corrupted OLED (white oled, or big text from EPG over clock etc ...) and reboot of box helps only.

 

Long time I am using in user_skin:

  <screen name="InfoBarSummary" position="0,0" size="96,64">
    <widget position="0,0" render="Picon" size="100,60" source="session.CurrentService" zPosition="0">
	<convert type="ServiceName">Reference</convert>
    </widget>
    <widget source="session.RecordState" render="FixedLabel" text="Rec" position="5,41" size="24,12" font="FdLcD;12" zPosition="1" noWrap="1" backgroundColor="black" foregroundColor="fullred" halign="center" valign="center">
	<convert type="ConditionalShowHide"></convert>
    </widget>
    <widget source="session.Event_Now" render="Progress" position="0,62" size="96,2" borderWidth="0" transparent="1" pixmap="skin_default/progress_small.png" backgroundColor="#800000" zPosition="1">
	<convert type="EventTime">Progress</convert>
    </widget>
  </screen>

Edited by ims, 2 March 2014 - 09:53.

[betacentauri]

Strange because I only removed
eRCInput::getInstance()->lock();
and unlock, so that the remote is controlled by e2 and not by the tuxtxt libs when teletext is active.

eDBoxLCD::getInstance()->lock();
is still there. So the OLED is controlled by the tuxtxt libs when teletext is active. And I can't see that I did change something regarding it in the tuxtxt libs.

[littlesat]

There are as far we understand bugs in the drivers of DMM....