Tixati will restart in the same screen position it was closed at. Well I closed it where only a small corner was on screen, when I restarted it, the conformation dialog was off screen where I couldn't get to it so it was impossible to move it or access any functions. Fortunately I was able to grab it as it was restarting to pull it over enough to get to the dialog box so this needs to be fixed where the start dialog box comes on screen center no matter where tixati is closed at. thx team

Will add here:

Would be nice to have position of bottom pane (with "details", "peers", "trackers") saved on exit. Now the position is reset to the small size so I need to resize it every time tixati is started.

The items in RSS feed are not sorted properly when sorting by "Item Added Time". They get split in two groups, and each of the groups is sorted ok but the overall sort is wrong. So in effect right now it shows items from the following months: 12 11 10 9 12 11 10 9.

This should be fixed in v2.87, which will be released very soon.

I saw the changelog of 2.87 mention sorting (tho it mentions "Last Update" instead of "Item Added time" column) and was hoping it was fixed, but now I am on 2.88 and still see the same wrong sorting

In addition, items added from RSS no longer honor the "Move on complete" setting (tried with it set either on the category or on the rss feed itself). I spotted this issue back on 2.84 too and it still remains on 2.88; Not sure which much older version I had before but it worked properly.

These issues are being worked on and should be fixed in the next version.

Hi, I confirm the "move on complete" setting works ok from feeds now in 2.89

Also, I figured out the reason for the feed items sorting issue. The short of it is, items that are CURRENTLY present in the feed are always considered newest by tixati, even if they are older than some historic items. I.e. look at the "items in feed" and "items out of feed" stats for a feed... "items in feed" always get sorted as newer than "items out of feed" regardless of the actual timestamp.

Function/option Sequential on downloading files does not work correctly since versions 2.8x.
When it comes to peer clients like libTorrent it just doesn't work.
Therefore I am still using 2.61.

> Function/option Sequential on downloading files does not work correctly since versions 2.8x.
> When it comes to peer clients like libTorrent it just doesn't work.
> Therefore I am still using 2.61.

This works fine for me and always has. Remember that torrent clients REQUEST parts from other peers. They don't demand. The peers supply what they have based on the preferences the requesting client may provide, or what they have been SET to provide, which may appear more random. Some clients (like Tixati can be, on a torrent-by-torrent basis) may be set to a super-seeding mode where regardless of what is requested they provide the LEAST-shared parts in the swarm to keep the torrent healthier. If everyone downloaded sequentially, who would have the end parts of all the files? It's better for everyone that there is some randomness in the swarm coverage to maximise completion.

So much has been fixed since that old version, you are rather foolish not to upgrade and there's certainly no bug relevant to this thread in my experience. The problem is not the software but your understanding/expectation of how torrent clients work.