Closed dhsdshdhk closed 5 years ago
thanks for your feedback. can you provide more details about the query settings? and did you check what kind of data is in the detail view?
I got it. Looks like a paging bug in the Twitter API. I created a workaround, the build will be provided as soon as possible.
btw: in extended mode you should adjust the column settings, full_text
replaces text
, see https://developer.twitter.com/en/docs/tweets/tweet-updates.html
in extended mode you should adjust the column settings, full_text replaces text
Yes. As you see in the screenshot I first activated full_text
, then it wasn't showing anything after the cutoff, so I activated text
as well and found out the values were there, instead of where they should have been.
I updated the latest release. Thanks again for opening the issue!
I fetched some data using tweet_mode extended and noticed two problems.
Screenshot:
Running on Windows 10, latest version.