Project

General

Profile

Defect #271

getTimeLine and maxCount issue

Added by Robert Ivens about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Start date:
04/23/2011
Due date:
% Done:

0%

Estimated time:
Browser (if web client):

Description

When I set the maxCount to 40 and get the timeline it shows the first 40, when I set it back to 20 I get message 21 till 40 it seems. Not the first 20.
When I get the timeline again then it loads correct again.

History

#1

Updated by Patrick Talbot about 13 years ago

Hum... I have seen that they are implementing some kind of pagination in the JTwitter lib, will look closer at how this is done, there must be something missing in my call.

#2

Updated by Patrick Talbot about 13 years ago

  • Status changed from New to In Progress

Cannot reproduce with 0.8.1 - please confirm

#3

Updated by Robert Ivens about 13 years ago

I still see this. I can only 'reset' this pagination by calling another function like getDirectMessages()

#4

Updated by Patrick Talbot about 13 years ago

  • Status changed from In Progress to New
#5

Updated by Patrick Talbot about 13 years ago

It doesn't make any sense at all.
Each calls to the API is using it's own loop with a page parameter starting at 1 (this is a local parameter of the method)...

#6

Updated by Patrick Talbot about 13 years ago

  • Status changed from New to In Progress

Seems fixed to me with 0.8.4 - please confirm

#7

Updated by Robert Ivens about 13 years ago

Sorry this is 0.8.3.
When I get the timeline(20) and then move to 40 it starts from 17 till 57. Only way to get (the real) 1 till 40 then is to getDirectMessages().

#8

Updated by Patrick Talbot about 13 years ago

Robert Ivens wrote:

Sorry this is 0.8.3.
When I get the timeline(20) and then move to 40 it starts from 17 till 57. Only way to get (the real) 1 till 40 then is to getDirectMessages().

I think it is fixed in 0.8.4 - update /plugins/twitter/jtwitter.jar along with /plugins/twitter.jar
Working fine now for me

#9

Updated by Robert Ivens about 13 years ago

Seems to work fine now in 0.8.4

#10

Updated by Patrick Talbot about 13 years ago

  • Status changed from In Progress to Closed

I think so too. Closing this one.

Also available in: Atom PDF