Cycling feeds

The cycling functionality has a confusing UI. Hopefully that will be cleaned up, but it works like this:

'Next' in the following indicates 'next' or 'previous'. It isn’t entirely obvious that this is next or previous as inforss currently cycles through in creation order (as far as I can tell) rather than the alphabetical menu order.

The "Next" button on the headline bar (if enabled) is effective whether or not the cycling is enabled, despite the positioning in the option screen.

If cycling is set to random, then inforss will skip 1 to 10 (random) items in the selected direction (which is not quite the same as random) either on clicking next or each cycling interval.

Note that when you cycle (either with the next / previous buttons or when cycling is enabled), inforss will not switch between feeds and groups. So if your currently selected item is a group, next will select another group. If it is a feed, next will select another feed.

If you click next:

• if cycling is enabled

  • if cycling with groups is enabled and this is a group

    • skip to the next feed within the group

  • otherwise

    • skip to the next feed / group

  • and restart the cycling timer

• otherwise (cycling is not enabled)

  • if the current feed is a group which is a playlist

    • cycle to the next feed in the playlist

  • otherwise

    • cycle to the next feed / group

  • This is moderately confusing if one of your groups is a playlist because next/prev gets stuck in it!

Feeds which are not marked as enabled ("activity" ticked in the option screen) will be skipped in the cycling process.

Groups and feeds will still be fetched at the normal intervals. However because cycling perforce inserts a gap between fetches, it is likely that feeds in groups may be fetched more or less simultaneously.

Note that it you set set cycle feeds in group and don’t set cycle feeds, the setting is ignored. The UI shouldn’t permit this (and the code shouldn’t work like that).