303 replies to this topic

[DimitarCC]

Yes that should be fixed. Also you idea in the beguining to be filled in the short desc is good idea. I am not so good at Python so some thing are dificult to understand. I couldnt find the place where cur_event is filled in with that 6 elements. Anyway if you can add that will be great! Also i was think for addign primetime coloring (time intervals configurable). Also in your version the current function attached to green button crash enigma. so i was redirect it to toggleRecord. It should be think to attach another functions to color buttons since timer is enough to be attached to red button! What do you think?

Prime time colouring would be nice, but we need to make sure the performance will not be impacted by adding too much in the build fund.

Yes you are right. But this will be just 2 or 3 more "if"s and 2 or 3 more variables i guiess performance impact will not be much!
If you can try to implement that things (i will implement primetime coloring but we have to decide time intervals to be in the skin on in the config) and we will se performance impact! if is too bad we will remove some things!

[littlesat]

I just tested it... but I did not see any picons at all???

[awx]

I just tested it... but I did not see any picons at all???

One change was made to make picons disabled by default, so that old skins still look as they did before.
You either can change the variable isPicon in the source to 1 by default or set the attribute in the skin to enable them.

[awx]

Yes that should be fixed. Also you idea in the beguining to be filled in the short desc is good idea. I am not so good at Python so some thing are dificult to understand. I couldnt find the place where cur_event is filled in with that 6 elements. Anyway if you can add that will be great! Also i was think for addign primetime coloring (time intervals configurable). Also in your version the current function attached to green button crash enigma. so i was redirect it to toggleRecord. It should be think to attach another functions to color buttons since timer is enough to be attached to red button! What do you think?

Prime time colouring would be nice, but we need to make sure the performance will not be impacted by adding too much in the build fund.

Yes you are right. But this will be just 2 or 3 more "if"s and 2 or 3 more variables i guiess performance impact will not be much!
If you can try to implement that things (i will implement primetime coloring but we have to decide time intervals to be in the skin on in the config) and we will se performance impact! if is too bad we will remove some things!

It doesn't hurt to try and see, I would suggest to allow that to be in the config and not the skin.

[littlesat]

So you need a modified skin to get the picons....

Did you already use autoscale... ?

[awx]

So you need a modified skin to get the picons....

Did you already use autoscale... ?

I have not used autoscale yet as I have not found it for MultiContentPixmap's, which is what is currently being used for drawing the grid. A much larger change would be need to implement this, unless I missed something and there is a way to still do this.

[awx]

Yes that should be fixed. Also you idea in the beguining to be filled in the short desc is good idea. I am not so good at Python so some thing are dificult to understand. I couldnt find the place where cur_event is filled in with that 6 elements. Anyway if you can add that will be great! Also i was think for addign primetime coloring (time intervals configurable). Also in your version the current function attached to green button crash enigma. so i was redirect it to toggleRecord. It should be think to attach another functions to color buttons since timer is enough to be attached to red button! What do you think?

Prime time colouring would be nice, but we need to make sure the performance will not be impacted by adding too much in the build fund.

Yes you are right. But this will be just 2 or 3 more "if"s and 2 or 3 more variables i guiess performance impact will not be much!
If you can try to implement that things (i will implement primetime coloring but we have to decide time intervals to be in the skin on in the config) and we will se performance impact! if is too bad we will remove some things!

Do you need self["Event"] in your skin or was this only for getting the description?

[littlesat]

unless I missed something and there is a way to still do this.

I suggest that is also why I do not have picons. My picons are on an USB stick....

[awx]

unless I missed something and there is a way to still do this.

I suggest that is also why I do not have picons. My picons are on an USB stick....

The method for loading is based on how it is done in Picon, but its possible I have not ported it correctly or misinterpreted how it works.

[DimitarCC]

Yes that should be fixed. Also you idea in the beguining to be filled in the short desc is good idea. I am not so good at Python so some thing are dificult to understand. I couldnt find the place where cur_event is filled in with that 6 elements. Anyway if you can add that will be great! Also i was think for addign primetime coloring (time intervals configurable). Also in your version the current function attached to green button crash enigma. so i was redirect it to toggleRecord. It should be think to attach another functions to color buttons since timer is enough to be attached to red button! What do you think?

Prime time colouring would be nice, but we need to make sure the performance will not be impacted by adding too much in the build fund.

Yes you are right. But this will be just 2 or 3 more "if"s and 2 or 3 more variables i guiess performance impact will not be much!
If you can try to implement that things (i will implement primetime coloring but we have to decide time intervals to be in the skin on in the config) and we will se performance impact! if is too bad we will remove some things!

Do you need self["Event"] in your skin or was this only for getting the description?

Well self["Event"] is needed for short description and for the progress rendering only! If that can be implemented in another way then self["Event"] is not needed

[awx]

Yes that should be fixed. Also you idea in the beguining to be filled in the short desc is good idea. I am not so good at Python so some thing are dificult to understand. I couldnt find the place where cur_event is filled in with that 6 elements. Anyway if you can add that will be great! Also i was think for addign primetime coloring (time intervals configurable). Also in your version the current function attached to green button crash enigma. so i was redirect it to toggleRecord. It should be think to attach another functions to color buttons since timer is enough to be attached to red button! What do you think?

Prime time colouring would be nice, but we need to make sure the performance will not be impacted by adding too much in the build fund.

Yes you are right. But this will be just 2 or 3 more "if"s and 2 or 3 more variables i guiess performance impact will not be much!
If you can try to implement that things (i will implement primetime coloring but we have to decide time intervals to be in the skin on in the config) and we will se performance impact! if is too bad we will remove some things!

Do you need self["Event"] in your skin or was this only for getting the description?

Well self["Event"] is needed for short description and for the progress rendering only! If that can be implemented in another way then self["Event"] is not needed

Ok, I will leave it as is for now.
Here is an updated version

New Changes
--------------------


Add a setup option to enable merging of short/extended desc
Fix service title not being displayed
Allow configuring a few more options using the setup menu
Add an option to allow choosing to use short/long title
Draw event names in a bounded box inside the the event rect
Add coloring of currently playing events
Readded Event variable since it is used in many skins
added ability to completly disable service title and use only picon
Add a name/label for the red button
Fix timerAdd so that it calls the correct function
Allow setting to concat short and full description as some providers combine both.

Attached Files

•  MergedGraphMultiEpg.1.0.6.tar.gz   11.07KB   8 downloads

[DimitarCC]

OK!
With that source i will start to implement primetime coloring! I hope until end of the day it will be finished!
I was thinking....maybe will be good to add that in somekind of SVN or something so to can merge easy and to can see eachy the changes! What do you think?

[awx]

OK!
With that source i will start to implement primetime coloring! I hope until end of the day it will be finished!
I was thinking....maybe will be good to add that in somekind of SVN or something so to can merge easy and to can see eachy the changes! What do you think?

I was hoping to get these merged in to the PLi repo, but I am not sure if I should just post the patches now or wait for some more feedback. If it does not get merged in then we can create fork the current PLi one and use that to maintain this source.

[DimitarCC]

OK!
With that source i will start to implement primetime coloring! I hope until end of the day it will be finished!
I was thinking....maybe will be good to add that in somekind of SVN or something so to can merge easy and to can see eachy the changes! What do you think?

I was hoping to get these merged in to the PLi repo, but I am not sure if I should just post the patches now or wait for some more feedback. If it does not get merged in then we can create fork the current PLi one and use that to maintain this source.

Yes maybe you are right! I want to ask you...is there a way to be implemented time pick up box in the config screen? I dont know is there control that can do that work! So if you can give me directions for that i will be glad!

[DimitarCC]

OK!
With that source i will start to implement primetime coloring! I hope until end of the day it will be finished!
I was thinking....maybe will be good to add that in somekind of SVN or something so to can merge easy and to can see eachy the changes! What do you think?

I was hoping to get these merged in to the PLi repo, but I am not sure if I should just post the patches now or wait for some more feedback. If it does not get merged in then we can create fork the current PLi one and use that to maintain this source.

Yes maybe you are right! I want to ask you...is there a way to be implemented time pick up box in the config screen? I dont know is there control that can do that work! So if you can give me directions for that i will be glad!

Ok maybe i have an idea for somekind of input!

[awx]

OK!
With that source i will start to implement primetime coloring! I hope until end of the day it will be finished!
I was thinking....maybe will be good to add that in somekind of SVN or something so to can merge easy and to can see eachy the changes! What do you think?

I was hoping to get these merged in to the PLi repo, but I am not sure if I should just post the patches now or wait for some more feedback. If it does not get merged in then we can create fork the current PLi one and use that to maintain this source.

Yes maybe you are right! I want to ask you...is there a way to be implemented time pick up box in the config screen? I dont know is there control that can do that work! So if you can give me directions for that i will be glad!

Ok maybe i have an idea for somekind of input!

I think you just need to use ConfigClock and that should be fine.

[DimitarCC]

Ahh OK! I was watch the source and i was found example of that usage! Thanks!

[ims]

I dont know, if is problem in old code too, but when length of label hide text in position, where is some nat.character (epg broadcasted as 2chars), then you can see:

Attached Files

•  mepg.jpg   47.11KB   58 downloads

[awx]

I dont know, if is problem in old code too, but when length of label hide text in position, where is some nat.character (epg broadcasted as 2chars), then you can see:

I will take a look at that, any chance you can give me an example character code, to test with? Just to be sure I am testing the right thing.

[littlesat]

I was hoping to get these merged in to the PLi repo,

That can be done... but first it has to get out of the "beta" stage... and also e.g. picons from USB sticks and autoscale should work of course... So there is work to do I suggest.