Hi list!
I just wanted to realease a updated package of the Enigma skin which now uses a modded version of the 'Vera'-font. Now it is possible to view the 'WarEagle'-icons. this mod was kindly provided by Frank Jepsen. See the changelog and the readme for more information.
The skin is available on my homepage (http://home.pages.at/brougs78) or directly via the following link: http://count.primawebtools.de/dlcountx.php?encid=40102&id=108230
Here the changelog: 2005.07.05: Version 0.3a - added finnish translation (thanks to Rolf Ahrenberg) - added the 'Misc'-section in Enigma.trans to keep the log clean of some annoying 'no translation found for ...'-messages (thanks to Rolf Ahrenberg) - altered the condition for the styling (text with variable width or fixed width) of 'MenuText' to comply with vdr-1.3.25 (thanks to C.Y.M) - now using a modified version of the 'Vera'-font which was kindly provided by Frank Jepsen. It includes the 'WarEagle'-icons (see README for more info). The monospaced font in the command-window is still the original VeraMono.ttf
Bye and have fun, Andreas Brugger
Andreas Brugger wrote:
Hi list!
I just wanted to realease a updated package of the Enigma skin which now uses a modded version of the 'Vera'-font. Now it is possible to view the 'WarEagle'-icons. this mod was kindly provided by Frank Jepsen. See the changelog and the readme for more information.
Thanks Andreas, the new skin looks really great.
Regards, C.
C.Y.M wrote:
Andreas Brugger wrote:
Hi list!
I just wanted to realease a updated package of the Enigma skin which now uses a modded version of the 'Vera'-font. Now it is possible to view the 'WarEagle'-icons. this mod was kindly provided by Frank Jepsen. See the changelog and the readme for more information.
Thanks Andreas, the new skin looks really great.
I forgot to mention a few things.. :) There appears to be three missing fonts in this new release.
FontBold.ttf Font.ttf FontMonoSpaced.ttf
Jul 5 12:07:55 sid vdr[8094]: ERROR: Font file (/etc/vdr/plugins/text2skin/fonts/FontBold.ttf) could be opened or read, or simply it is broken Jul 5 12:07:55 sid vdr[8094]: ERROR: Text2Skin: Couldn't load font FontBold.ttf:24 Jul 5 12:07:55 sid vdr[8094]: ERROR: Font file (/etc/vdr/plugins/text2skin/fonts/Font.ttf) could be opened or read, or simply it is broken Jul 5 12:07:55 sid vdr[8094]: ERROR: Text2Skin: Couldn't load font Font.ttf:22 Jul 5 12:08:29 sid vdr[8094]: ERROR: Font file (/etc/vdr/plugins/text2skin/fonts/FontMonoSpaced.ttf) could be opened or read, or simply it is broken Jul 5 12:08:29 sid vdr[8094]: ERROR: Text2Skin: Couldn't load font FontMonoSpaced.ttf:22
Secondly, I was curious about a feature request. Would it be possible to view the number of the channels as the are being entered, like vdr's default skins do?
Best Regards, C.
C.Y.M schrieb:
Thanks Andreas, the new skin looks really great.
Thanks. ;-)
I forgot to mention a few things.. :) There appears to be three missing fonts in this new release.
FontBold.ttf Font.ttf FontMonoSpaced.ttf
Jul 5 12:07:55 sid vdr[8094]: ERROR: Font file (/etc/vdr/plugins/text2skin/fonts/FontBold.ttf) could be opened or read, or simply it is broken Jul 5 12:07:55 sid vdr[8094]: ERROR: Text2Skin: Couldn't load font FontBold.ttf:24 Jul 5 12:07:55 sid vdr[8094]: ERROR: Font file (/etc/vdr/plugins/text2skin/fonts/Font.ttf) could be opened or read, or simply it is broken Jul 5 12:07:55 sid vdr[8094]: ERROR: Text2Skin: Couldn't load font Font.ttf:22 Jul 5 12:08:29 sid vdr[8094]: ERROR: Font file (/etc/vdr/plugins/text2skin/fonts/FontMonoSpaced.ttf) could be opened or read, or simply it is broken Jul 5 12:08:29 sid vdr[8094]: ERROR: Text2Skin: Couldn't load font FontMonoSpaced.ttf:22
This is a text2skin-feature. ;-) It searches for the fonts in /etc/vdr/plugins/text2skin/fonts first and in the Skin-directory afterwards. As the fonts are in the latter text2skin logs an error. To avoid this, the only way is to put the fonts in the /etc/vdr/plugins/text2skin/fonts-directory.
Secondly, I was curious about a feature request. Would it be possible to view the number of the channels as the are being entered, like vdr's default skins do?
What do you mean with that?
This is a text2skin-feature. ;-) It searches for the fonts in /etc/vdr/plugins/text2skin/fonts first and in the Skin-directory afterwards. As the fonts are in the latter text2skin logs an error. To avoid this, the only way is to put the fonts in the /etc/vdr/plugins/text2skin/fonts-directory.
Thanks, got it. :)
Secondly, I was curious about a feature request. Would it be possible to view the number of the channels as the are being entered, like vdr's default skins do?
What do you mean with that?
Well, with a default vdr skin (ie; sttng), as soon as I press a number on the remote, it shows up on the OSD. For example, if the channel I want to switch to is "127", then as soon as I press "1", it shows up in the OSD. But, this is an issue with all text2skin skins. The complete channel number shows up after all of the numbers have all been entered and vdr switches to the channel. Text2skin doesn't show the numbers of the channel on the OSD as they are being pressed.
Best Regards, C.
C.Y.M kirjoitti:
Secondly, I was curious about a feature request. Would it be possible to view the number of the channels as the are being entered, like vdr's default skins do?
What do you mean with that?
Well, with a default vdr skin (ie; sttng), as soon as I press a number on the remote, it shows up on the OSD. For example, if the channel I want to switch to is "127", then as soon as I press "1", it shows up in the OSD. But, this is an issue with all text2skin skins. The complete channel number shows up after all of the numbers have all been entered and vdr switches to the channel. Text2skin doesn't show the numbers of the channel on the OSD as they are being pressed.
I don't have this problem. I'm using text2skin CVS from about 2005-06-07 and a skin named enElchi.
C.Y.M schrieb:
Well, with a default vdr skin (ie; sttng), as soon as I press a number on the remote, it shows up on the OSD. For example, if the channel I want to switch to is "127", then as soon as I press "1", it shows up in the OSD. But, this is an issue with all text2skin skins. The complete channel number shows up after all of the numbers have all been entered and vdr switches to the channel. Text2skin doesn't show the numbers of the channel on the OSD as they are being pressed.
Can't confirm this. Here the numbers show up immediatly ... same behaviour as in the default skins ...
Anssi Hannula wrote:
C.Y.M kirjoitti:
Secondly, I was curious about a feature request. Would it be possible to view the number of the channels as the are being entered, like vdr's default skins do?
What do you mean with that?
Well, with a default vdr skin (ie; sttng), as soon as I press a number on the remote, it shows up on the OSD. For example, if the channel I want to switch to is "127", then as soon as I press "1", it shows up in the OSD. But, this is an issue with all text2skin skins. The complete channel number shows up after all of the numbers have all been entered and vdr switches to the channel. Text2skin doesn't show the numbers of the channel on the OSD as they are being pressed.
I don't have this problem. I'm using text2skin CVS from about 2005-06-07 and a skin named enElchi.
Hmm.. ok. Thats good to know. Then it must be specific to the Enigma skin.. I have not tried enElchi.
Thanks, C.
C.Y.M wrote:
I don't have this problem. I'm using text2skin CVS from about 2005-06-07 and a skin named enElchi.
Hmm.. ok. Thats good to know. Then it must be specific to the Enigma skin.. I have not tried enElchi.
Nope, I'm using enigma (though I'm still at version 0.2) and I don't have this problem.
bye
Andreas Brugger wrote:
C.Y.M schrieb:
Well, with a default vdr skin (ie; sttng), as soon as I press a number on the remote, it shows up on the OSD. For example, if the channel I want to switch to is "127", then as soon as I press "1", it shows up in the OSD. But, this is an issue with all text2skin skins. The complete channel number shows up after all of the numbers have all been entered and vdr switches to the channel. Text2skin doesn't show the numbers of the channel on the OSD as they are being pressed.
Can't confirm this. Here the numbers show up immediatly ... same behaviour as in the default skins ...
I did make a small change so the skin can display 5 digit channel numbers.. but thats the only thing I changed. Hmm..maybe its my fault.
I changed these coordinates.. in several places:
@@ -55,10 +55,10 @@ <rectangle x1="107" x2="-1" y1="-128" y2="-125" color="TopBG"/>
<!-- channel-info --> - <text x1="110" x2="182" y1="-159" y2="-124" color="TopTxtShad" align="center" font="FontBold.ttf:26,85">{ChannelNumber}</text> - <text x1="107" x2="179" y1="-160" y2="-125" color="TopTxtFG" align="center" font="FontBold.ttf:26,85">{ChannelNumber}</text> - <text x1="186" x2="-5" y1="-159" y2="-124" color="TopTxtShad" align="left" font="FontBold.ttf:26,85">{ChannelName}</text> - <text x1="183" x2="-8" y1="-160" y2="-125" color="TopTxtFG" align="left" font="FontBold.ttf:26,85">{ChannelName}</text> + <text x1="110" x2="209" y1="-159" y2="-124" color="TopTxtShad" align="center" font="FontBold.ttf:26,85">{ChannelNumber}</text> + <text x1="107" x2="206" y1="-160" y2="-125" color="TopTxtFG" align="center" font="FontBold.ttf:26,85">{ChannelNumber}</text> + <text x1="213" x2="-5" y1="-159" y2="-124" color="TopTxtShad" align="left" font="FontBold.ttf:26,85">{ChannelName}</text> + <text x1="210" x2="-8" y1="-160" y2="-125" color="TopTxtFG" align="left" font="FontBold.ttf:26,85">{ChannelName}</text>
<!-- EPG-date "now" --> <rectangle x1="107" x2="-1" y1="-120" y2="-78" color="ChEpgNowBG"/>
C.Y.M wrote:
Andreas Brugger wrote:
C.Y.M schrieb:
Well, with a default vdr skin (ie; sttng), as soon as I press a number on the remote, it shows up on the OSD. For example, if the channel I want to switch to is "127", then as soon as I press "1", it shows up in the OSD. But, this is an issue with all text2skin skins. The complete channel number shows up after all of the numbers have all been entered and vdr switches to the channel. Text2skin doesn't show the numbers of the channel on the OSD as they are being pressed.
Can't confirm this. Here the numbers show up immediatly ... same behaviour as in the default skins ...
I did make a small change so the skin can display 5 digit channel numbers.. but thats the only thing I changed. Hmm..maybe its my fault.
I changed these coordinates.. in several places:
I'll bet that its not my changes that broke it but the fact that I still missed a spot. Somewhere on the screen that comes up when the keys are entered, needs to also be widened for 5 digits. Its probably still overlapping something which is preventing it from displaying. I'll keep looking.
Regards, C.
C.Y.M schrieb:
I'll bet that its not my changes that broke it but the fact that I still missed a spot. Somewhere on the screen that comes up when the keys are entered, needs to also be widened for 5 digits. Its probably still overlapping something which is preventing it from displaying. I'll keep looking.
Do you have the same problem with a "plain" Enigma-skin?
Andreas Brugger wrote:
C.Y.M schrieb:
I'll bet that its not my changes that broke it but the fact that I still missed a spot. Somewhere on the screen that comes up when the keys are entered, needs to also be widened for 5 digits. Its probably still overlapping something which is preventing it from displaying. I'll keep looking.
Do you have the same problem with a "plain" Enigma-skin?
Yes, I still get the problem with a "plain" copy of Enigma-skin. For me, the problem started to occur when I upgraded to text2skin 1.0.
Regards, C.
C.Y.M wrote:
Andreas Brugger wrote:
C.Y.M schrieb:
I'll bet that its not my changes that broke it but the fact that I still missed a spot. Somewhere on the screen that comes up when the keys are entered, needs to also be widened for 5 digits. Its probably still overlapping something which is preventing it from displaying. I'll keep looking.
Do you have the same problem with a "plain" Enigma-skin?
Yes, I still get the problem with a "plain" copy of Enigma-skin. For me, the problem started to occur when I upgraded to text2skin 1.0.
It is possible that the difference is because you are using PAL and I am using NTSC.
Regards, C.
C.Y.M schrieb:
Yes, I still get the problem with a "plain" copy of Enigma-skin. For me, the problem started to occur when I upgraded to text2skin 1.0.
It is possible that the difference is because you are using PAL and I am using NTSC.
This is weired ... never heard of such a behaviour. But I don't think that it has anything to do with PAL/NTSC. Have you updated some libs (ImageMagick for expample) after compiling the plugin? Maybe you should ask Sascha, if he has an explanation for that.
C.Y.M wrote:
Yes, I still get the problem with a "plain" copy of Enigma-skin. For me, the problem started to occur when I upgraded to text2skin 1.0.
I now see the problem too, but it doesn't occur always: If I want to go channel 1472, I first press 1, then 4. At this point, if channel 14 exists, there's no problem, but if channel 14 doesn't exist, the number doesn't show in the screen. The number returns when I press 7, because 147 exists. Then I press 2.
No problem with vdr default skins.
Anssi Hannula wrote:
C.Y.M wrote:
Yes, I still get the problem with a "plain" copy of Enigma-skin. For me, the problem started to occur when I upgraded to text2skin 1.0.
I now see the problem too, but it doesn't occur always: If I want to go channel 1472, I first press 1, then 4. At this point, if channel 14 exists, there's no problem, but if channel 14 doesn't exist, the number doesn't show in the screen. The number returns when I press 7, because 147 exists. Then I press 2.
No problem with vdr default skins.
Thanks for the reply. This is also exactly what I am seeing here. If the channel numbers do not exist, then the numbers do not display. There is also a similar problem I have with VDR where lets say I have two channels; 14 and channel 147. I can not switch to channel 147 because by the time I press 1 and 4, VDR tunes to channel 14 before I can press 7.
Best Regards, C.
C.Y.M wrote:
Anssi Hannula wrote:
C.Y.M wrote:
Yes, I still get the problem with a "plain" copy of Enigma-skin. For me, the problem started to occur when I upgraded to text2skin 1.0.
I now see the problem too, but it doesn't occur always: If I want to go channel 1472, I first press 1, then 4. At this point, if channel 14 exists, there's no problem, but if channel 14 doesn't exist, the number doesn't show in the screen. The number returns when I press 7, because 147 exists. Then I press 2.
No problem with vdr default skins.
Thanks for the reply. This is also exactly what I am seeing here. If the channel numbers do not exist, then the numbers do not display. There is also a similar problem I have with VDR where lets say I have two channels; 14 and channel 147. I can not switch to channel 147 because by the time I press 1 and 4, VDR tunes to channel 14 before I can press 7.
The following patch seems to fix the problem. Although, I can't seem to figure out why the default vdr skins have a trailing "-" sign as I enter the channel keys, and this does not. Please let me know if anyone spots a problem with this fix.
Best Regards,
-
Andreas Brugger -
Anssi Hannula -
C.Y.M -
Luca Olivetti