218 replies to this topic

[littlesat]

Search the skin.ply for Volume.... and you can find it yourself...

And what widget/lable do you want to change exactly??? I mean now the size...

Edited by littlesat, 11 January 2012 - 13:56.

[greatred]

littlesat I`m not asking how to do this, I allready have this as a skin_user.xml. My question/concern was if this can be implemented generally in the skin? But it looks like I`m the only who finds that changing volume on top of other screens is not looking nice

As to the size I was reffering to line #707

<widget name="epg_description" position="540,110" size="680,500" transparent="1" font="Regular;26" />

[littlesat]

Done

[ims]

But it looks like I`m the only who finds that changing volume on top of other screens is not looking nice

the volume could be moved left to PIG and with less width ... dont know - there is 85 pixels only.

edit: and y-position as is.

Edited by ims, 11 January 2012 - 14:34.

[littlesat]

There is nothing to avoid that volume button stuff.... The same is valid for the mute sign... If someone has a suggestion were to place it better I hear it

[Rob van der Does]

The same is valid for the mute sign... If someone has a suggestion were to place it better I hear it

Is it really important to see the mute-icon? You could leave it out completely.

[Robinson]

So I kindly ask littlesat to consider changing the size of the font to a little smaller, please.
I mean the event description after pressing INFO on the remote.

Can i suggest following :

font="Regular; 22"

Thanks, greatred, for your suggestion.
By the way, what is the size in the current image?

[ims]

For Volume could be enought x to 25, it seems well and it is in zone without all others things.

Or 40. I saw on it via webif only ...

Edited by ims, 11 January 2012 - 14:46.

[littlesat]

And with overscan?

[greatred]

Mine is currently @ 20,center and it fits very well in the area that is not used by any of the labels,widgets etc.

[ims]

If is used x = 25, then it is in center of this area. Overscan - dont know. I am not see on it on TV now, cannot tell.

For Mute: y set to 25. There it is time to time over text, but i think, mute has priority info in this cases ( imho ).

Volume:

  <screen name="Volume" title="Volume" position="25,245" size="35,230" backgroundColor="transpBlack" zPosition="1" flags="wfNoBorder">

Edited by ims, 11 January 2012 - 15:28.

[ims]

Better will be x=30.

[littlesat]

This is to close regards to the overscan... You need al least 50...

[theparasol]

This is to close regards to the overscan... You need al least 50...

Aren't we making exceptions for a very small amount of televisions? I personally don't care for users of overscan televisions. Just get a telly that won't overscan at all that much or just use another skin that will fit within your to much overscanned tv.

[ims]

50 is conflict with PIG (with its hiden picture - then must not be transparency background for volume)

Edited by ims, 11 January 2012 - 16:59.

[greatred]

With all the "templates" magic in PLiHD, making an alternative version for properly scanned TV`s should be possible? If there only was support in e2skinner for templates I would love to help. Unfortunately working on a plain xml file is for me still very time consuming. Cheers littlesat I know you make this because there is nothing better to do these days

[Robinson]

Text in EPG info is big for me now, btw

So I kindly ask littlesat to consider changing the size of the font to a little smaller, please.
I mean the event description after pressing INFO on the remote.

Do you have any suggestions how small.... could you change by yourself in skin.xml and forward what you want? Just a statement "smaller" is not specific enough to me...

I have just changed 26 to 24. It looks much better and I think most of us will agree that 26 is too big.
<widget name="epg_description" position="540,110" size="680,500" transparent="1" font="Regular;24" />
Do you think you could introduce this change to PLi-HD skin permanently?
This is under <!-- EPG Stuff -->:

<screen name="EventView" title="Eventview" position="0,0" size="1280,720" flags="wfNoBorder">
	<panel name="SelectionTemplate"/>
	<panel name="ButtonTemplate_4"/>
	<panel name="KeyMenuTemplate"/>
	<widget name="channel" position="85,370" size="435,42" transparent="1" foregroundColor="secondFG" font="Regular;22" halign="left" />
	<widget name="datetime" position="85,440" size="435,30" transparent="1" font="Regular;22" halign="left" />
	<widget name="duration" position="85,485" size="435,30" transparent="1" font="Regular;22" halign="left" />
	<widget name="epg_description" position="540,110" size="680,500" transparent="1" font="Regular;24" />
	<eLabel text="Next:" position="85,590" size="63,26" zPosition="2" font="Regular; 22" foregroundColor="white" transparent="1" />
	<widget source="session.Event_Next" render="Label" position="148,590" size="435,26" font="Regular;22" halign="left" foregroundColor="secondFG" transparent="1">
	  <convert type="EventName">Name</convert>
	</widget>
  </screen>

[littlesat]

I personally don't care for users of overscan televisions.

It is the standaard skin... so we have to take care...

[theparasol]

Is it possible to code in enigma / define something like overscan variables.
Standard they are like 50 (much overscan) and can be altered by setting something in the menu of the box.
That would be the best solution. But can it be integrated / coded in skin and enigma2?

[littlesat]

The ET boxes can downscale the complete skin.. but for a common skin we should do it for all boxes...

I do not want to support different skins, such like HD en EHD... but everyone can create a fork of my orriginal... Please not it is already a lot of work to support one skin....

Probably the volume buttom may fit horizontally on top of the screen... smaller end also includes a small mute sign (on top of it when required...). But currently I have no time to gimp.

Edited by littlesat, 11 January 2012 - 20:52.