Teletext improvements
Re: Teletext improvements #21
Re: Teletext improvements #22
Posted 7 December 2013 - 22:38
the subtitle rendering is probably missing a
m_dc->islocked()
check.
Each painter / dc operation is checking the lock, it seems.
That's how the issue should have been fixed I think.
Hi pieterg,
I have debugged it and found the error:
In lib/gdi/grc.cpp in procedure blitScale I have added a eDebug which shows that m_dc->islocked() is always 0. Then I tried to find out which islocked method is called. It's not the gFBDC::islocked! It's the virtual islocked method in gDC (grc.h).
Ok, then I thought, the variable m_dc must be of type gDC, otherwise it should be called gFBDC::islocked. But at runtime typeid(m_dc).name() says "5gFBDC". So it's type is gFBDC. Why is then the virtual method called?
I found the answer. It's because the islocked method in gFBDC has a const qualifier:
int islocked() const {....};
After removing const it works. A little bit strange.
Here is a patch.
I guess with it Littlesat can revert his tuxtxt subtitle workaround (I have tested with the subtitles and it works without the patch)
Attached Files
Re: Teletext improvements #23
Posted 7 December 2013 - 23:55
Looks like it might have been working earlier this year
43ed3b0a (Mike Looijmans 2013-07-28 12:49:58 +0200 35) int islocked() const { return fb->islocked(); }
A reminder that we really should pay attention at the compiler warnings
(and enable -Woverloaded-virtual, if we didn't so already)
Re: Teletext improvements #24
Re: Teletext improvements #25
Re: Teletext improvements #26
Re: Teletext improvements #27
Posted 11 December 2013 - 20:56
Ok, I see the patch is applied and littlesat has reverted the workarounds. I guess you get now problems applying my patches (http://openpli.org/f...ndpost&p=388940). I'll rewrite them in the next days and post them here again.
Re: Teletext improvements #28
Re: Teletext improvements #29
Re: Teletext improvements #30
Posted 25 January 2014 - 20:36
I really like the idea of adding keymap.xml support to teletext (I would then add KEY_CHANNELUP and KEY_CHANNELDOWN for "page up" and "page down"). Unfortunately merging patches into files from the repository is exceeding my skills. I would really appreciate if this addition could be commited. What are the plans / schedule for that? Thanks..
Edited by quad, 25 January 2014 - 20:40.
Re: Teletext improvements #31
Re: Teletext improvements #32
Posted 26 January 2014 - 00:02
http://openpli.org/f...ndpost&p=390836
Please post here a little info when you commit it!
Edited by betacentauri, 26 January 2014 - 00:03.
Re: Teletext improvements #33
Re: Teletext improvements #34
Re: Teletext improvements #35
Posted 26 January 2014 - 16:02
$ git am -s ../tuxtxt_git_0001-Teletext-improvements.patch.txt Applying: Teletext improvements c:/######/tuxtxt/.git/rebase-apply/patch:212: trailing whitespace . #ifndef HAVE_TRIPLEDRAGON error: patch failed: tuxtxt/plugin/plugin.py:16 error: tuxtxt/plugin/plugin.py: patch does not apply Patch failed at 0001 Teletext improvements The copy of the patch that failed is found in: c:/######/tuxtxt/.git/rebase-apply/patch When you have resolved this problem, run "git am --resolved". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort".
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Teletext improvements #36
Re: Teletext improvements #37
Posted 26 January 2014 - 20:27
Strange! What did you do?
$ git clone git://git.code.sf.net/p/openpli/tuxtxt Klone nach 'tuxtxt'... remote: Counting objects: 263, done. remote: Compressing objects: 100% (212/212), done. remote: Total 263 (delta 129), reused 107 (delta 50) Empfange Objekte: 100% (263/263), 173.72 KiB | 303.00 KiB/s, done. Löse Unterschiede auf: 100% (129/129), done. Prüfe Konnektivität... Fertig $ cd tuxtxt $ git am -s tuxtxt_git_0001-Teletext-improvements_v2.patch.txt Wende an: Teletext improvements $
Important: Both patches must be applied! One in tuxtxt git and one in the e2 git.
Re: Teletext improvements #38
Re: Teletext improvements #39
Posted 5 February 2014 - 20:09
Hi quad,
that means that the patch could be applied without problems.
I didn't do another function test, but it should still work.
You can send pm to pieterg, but I guess he reads the forum and have no time to review it.
Re: Teletext improvements #40
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users