Reply to thread

Message

<blockquote data-quote="amilewski" data-source="post: 210386" data-attributes="member: 29177">Hi to all MP users and developers,I'm constructing new grabber which uses <a href="http://www.rzeczpospolita.pl/tv" target="_blank">http://www.rzeczpospolita.pl/tv</a> web site, listings looks pretty usefull and contain many information.Almost all work is done except one thing: site lists only 25 records, so I need to shift to next set of records, I use LIST_OFFSET with maxlistings=&quot;25&quot; to accomplish that. WebEPG reads and parse correctly first page (25 records) with LIST_OFFSET=0, then it promotes to next page with LIST_OFFSET=25 (and gets 20 records as for today), then instead of promoting to the next day it looks for next page with LIST_OFFSET=50 (it will get 0 records of course), then it uses LIST_OFFSET=75 and so forth untill I kill webepg.exe.Please look at attached grabber and webepg.log files, it seems that webepg misses the point where (list count)&lt;(maxlistings), even on pages where (list count)=0. In the log file you can see that webepg wrongly plays with Listing Count considering it 26 where it should be 0 (as in WebEPG Designer).thanks in advance</blockquote>

[QUOTE="amilewski, post: 210386, member: 29177"] Hi to all MP users and developers, I'm constructing new grabber which uses [URL]http://www.rzeczpospolita.pl/tv[/URL] web site, listings looks pretty usefull and contain many information. Almost all work is done except one thing: site lists only 25 records, so I need to shift to next set of records, I use LIST_OFFSET with maxlistings="25" to accomplish that. WebEPG reads and parse correctly first page (25 records) with LIST_OFFSET=0, then it promotes to next page with LIST_OFFSET=25 (and gets 20 records as for today), then instead of promoting to the next day it looks for next page with LIST_OFFSET=50 (it will get 0 records of course), then it uses LIST_OFFSET=75 and so forth untill I kill webepg.exe. Please look at attached grabber and webepg.log files, it seems that webepg misses the point where (list count)<(maxlistings), even on pages where (list count)=0. In the log file you can see that webepg wrongly plays with Listing Count considering it 26 where it should be 0 (as in WebEPG Designer). thanks in advance [/QUOTE]

Verification