Py3status: Regression in "group": cycles on its own, does not respect button_{next,prev}

[maximbaz]

Since https://github.com/ultrabug/py3status/commit/910b74d39bbd3ca43a93426c72ce13a610216691 I have a very weird behavior:

• Modules in group cycle on their own, i.e. I see the first module, then suddenly the second module shows up, then the first one again, etc.
• Configured button_{next,prev} have no effect, instead they scroll only on mouse wheel up and down

I confirm that https://github.com/ultrabug/py3status/commit/910b74d39bbd3ca43a93426c72ce13a610216691 is the first bad commit

Here's my exact config:

group cpu {
  button_next = 1
  button_prev = 0

  sysdata {
    cache_timeout = 1
    thresholds = { 'cpu': [(0, 'good'), (25, 'degraded'), (80, 'bad')] }
    format = '[\?color=cpu 󰀐   {cpu_usage:.0f}%]'
  }

  conky {
    format = '󰀐  {top name 1} {top cpu 1}%'
  }
}

group ram {
  button_next = 1
  button_prev = 0

  sysdata {
    cache_timeout = 1
    thresholds = { 'mem': [(0, 'good'), (60, 'degraded'), (80, 'bad')] }
    format = '[\?color=mem 󰀌   {mem_used_percent:.0f}%]'
  }

  conky {
    format = '󰀌  {top_mem name 1} {top_mem mem 1}%'
  }
}

[lasers]

Try https://github.com/ultrabug/py3status/tree/group-cycling

Too focused on non-urgent that I didn't check cycle value.

[maximbaz]

Yes sir, it fixes the issue! Please feel free to merge it in master, you have my approval 👍

[lasers]

Closed via #1757.

[kozross]

Will there be a bugfix release?

[maximbaz]

cc @ultrabug

[lasers]

Temporary fix. You can set cycle with a large number like 21600 (6 hours).

[kozross]

@lasers Sure, will do that for the moment.

[ultrabug]

Thanks a lot guys, I've released 3.18 !