Yes because in my opinion that must be like that because in some languages the min could be before the number or so on. But that is the old same discussion.....
ViX doesnt complain about that warning so no reason to change it.
Posted 19 December 2023 - 10:02
Yes because in my opinion that must be like that because in some languages the min could be before the number or so on. But that is the old same discussion.....
ViX doesnt complain about that warning so no reason to change it.
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 19 December 2023 - 10:10
I think you are confused between errors and warnings.
A compiler error is when your program is wrong, and the compiler has no idea how to produce runnable code from it.
A compiler warning is where the compiler can't guarantee your code will run, even though the code is valid.
Certain code syntax will always cause warnings because "the compiler can't guarantee your code will run", e.g. dynamic values.
If you promote those warnings to errors you make it impossible to compile valid code.
I'll just post this again. A warning is not an error. Errors should only show when the compiler has no idea how to produce runnable code. What has happened in PLi is wrong because it means it is not possible to run valid C++ syntax. The warning shows because the compiler doesn't know what the dynamic values are, not because there is an error.
Edited by Huevos, 19 December 2023 - 10:10.
Posted 19 December 2023 - 10:43
def setFontsize(self): self.ServiceNumberFont = gFont(self.ServiceNameFontName, self.ServiceNameFontSize + config.usage.servicenum_fontsize.value) self.ServiceNameFont = gFont(self.ServiceNameFontName, self.ServiceNameFontSize + config.usage.servicename_fontsize.value) self.ServiceInfoFont = gFont(self.ServiceInfoFontName, self.ServiceInfoFontSize + config.usage.serviceinfo_fontsize.value) self.ServiceNextInfoFont = gFont(self.ServiceNextInfoFontName, self.ServiceNextInfoFontSize + config.usage.serviceinfo_fontsize.value) self.ServiceRemainingInfoFont = gFont(self.ServiceRemainingInfoFontName, self.ServiceRemainingInfoFontSize + config.usage.serviceinfo_fontsize.value) self.l.setElementFont(self.l.celServiceName, self.ServiceNameFont) self.l.setElementFont(self.l.celServiceNumber, self.ServiceNumberFont) self.l.setElementFont(self.l.celServiceInfo, self.ServiceInfoFont) self.l.setElementFont(self.l.celServiceNextInfo, self.ServiceNextInfoFont) self.l.setElementFont(self.l.celServiceInfoRemainingTime, self.ServiceRemainingInfoFont) if "perc" in config.usage.show_event_progress_in_servicelist.value: self.l.setElementFont(self.l.celServiceEventProgressbar, self.ServiceInfoFont)
self.ServiceNumberFont = gFont(self.ServiceNameFontName, self.ServiceNameFontSize + config.usage.servicenum_fontsize.value)
Maybe Number?
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Posted 19 December 2023 - 10:47
Yes you are right... That is wrong in ViX too...I didnt noticed it. Will change
OK. here https://github.com/O...igma2/pull/3880
Edited by DimitarCC, 19 December 2023 - 10:52.
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 19 December 2023 - 17:28
[listboxservice] fixed event default color and time remaining
Edited by Dimitrij, 19 December 2023 - 17:41.
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Posted 20 December 2023 - 12:35
Overlapping of event info and progressbar not fixed(two lines and next event).
OK. Here is new try:
https://github.com/O...igma2/pull/3884
I hope is fixed. Keep in mind that i can not test that since i dont have EPG that long most of the time
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 20 December 2023 - 12:52
Interesting is that i dont get overlapping here even with the old code...
nextevent2.jpg 129.38KB 1 downloads
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 20 December 2023 - 13:32
Resolved by my self.
When you toggle to the views in channel selections, where before you changed the userbouquet goes back to user bouquet you originally had.
Edited by littlesat, 20 December 2023 - 13:37.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 20 December 2023 - 17:23
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 21 December 2023 - 11:21
So i found a logical mistake that i made in last PR... I correct that with this https://github.com/O...igma2/pull/3885
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
0 members, 6 guests, 0 anonymous users