external/yambar
1
0
Fork 1
mirror of https://codeberg.org/dnkl/yambar.git synced 2025-06-16 08:15:40 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

module: remove ready_fd

Browse source 
All modules are expected to handle a call to content() after having
been instantiated.

I.e. modules *cannot* even expect run() to have started running.
This commit is contained in:
Daniel Eklöf 2019-01-13 15:25:39 +01:00
parent 65cfcfb2de
commit acdeff3b6e
14 changed files with 27 additions and 66 deletions
Download patch file Download diff file Expand all files Collapse all files

7
modules/battery.c
View file

@ -248,10 +248,8 @@ run(struct module_run_context *ctx)
struct private *m = ctx->module->private;
int base_dir_fd = initialize(m);
if (base_dir_fd == -1) {
module_signal_ready(ctx);
if (base_dir_fd == -1)
return -1;
}
LOG_INFO("%s: %s %s (at %.1f%% of original capacity)",
m->battery, m->manufacturer, m->model,
@ -269,7 +267,6 @@ run(struct module_run_context *ctx)
if (status_fd == -1 || capacity_fd == -1 || energy_fd == -1 ||
power_fd == -1 || udev == NULL || mon == NULL)
{
module_signal_ready(ctx);
goto out;
}
@ -277,7 +274,7 @@ run(struct module_run_context *ctx)
udev_monitor_enable_receiving(mon);
update_status(ctx->module, capacity_fd, energy_fd, power_fd, status_fd);
module_signal_ready(ctx);
bar->refresh(bar);
while (true) {
struct pollfd fds[] = {