pgrondek/polybar-dwm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
polybar-dwm/src/modules/systray.cpp

66 lines
1.5 KiB
C++
Raw Normal View History

wip(systray): Add module base
2017-01-01 21:28:28 +01:00
#if DEBUG
#include "modules/systray.hpp"
module: Implement action router (#2336) * module: Implement proof of concept action router Action implementation inside module becomes much cleaner because each module just registers action names together with a callback (pointer to member function) and the action router does the rest. * Make input function final This forces all modules to use the action router * modules: Catch exceptions in action handlers * Use action router for all modules * Use action_ prefix for function names The mpd module's 'stop' action overwrote the base module's stop function which caused difficult to debug behavior. To prevent this in the future we now prefix each function that is responsible for an action with 'action_' * Cleanup * actions: Throw exception when re-registering action Action names are unique inside modules. Unfortunately there is no way to ensure this statically, the next best thing is to crash the module and let the user know that this is a bug. * Formatting * actions: Ignore data for actions without data This is the same behavior as before. * action_router: Write tests
2021-01-04 10:25:52 +01:00
wip(systray): Add module base
2017-01-01 21:28:28 +01:00
#include "drawtypes/label.hpp"
module: Implement action router (#2336) * module: Implement proof of concept action router Action implementation inside module becomes much cleaner because each module just registers action names together with a callback (pointer to member function) and the action router does the rest. * Make input function final This forces all modules to use the action router * modules: Catch exceptions in action handlers * Use action router for all modules * Use action_ prefix for function names The mpd module's 'stop' action overwrote the base module's stop function which caused difficult to debug behavior. To prevent this in the future we now prefix each function that is responsible for an action with 'action_' * Cleanup * actions: Throw exception when re-registering action Action names are unique inside modules. Unfortunately there is no way to ensure this statically, the next best thing is to crash the module and let the user know that this is a bug. * Formatting * actions: Ignore data for actions without data This is the same behavior as before. * action_router: Write tests
2021-01-04 10:25:52 +01:00
#include "modules/meta/base.inl"
wip(systray): Add module base
2017-01-01 21:28:28 +01:00
#include "x11/connection.hpp"
#include "x11/tray_manager.hpp"
POLYBAR_NS
namespace modules {
template class module<systray_module>;
/**
* Construct module
*/
systray_module::systray_module(const bar_settings& bar, string name_)
: static_module<systray_module>(bar, move(name_)), m_connection(connection::make()) {
module: Implement action router (#2336) * module: Implement proof of concept action router Action implementation inside module becomes much cleaner because each module just registers action names together with a callback (pointer to member function) and the action router does the rest. * Make input function final This forces all modules to use the action router * modules: Catch exceptions in action handlers * Use action router for all modules * Use action_ prefix for function names The mpd module's 'stop' action overwrote the base module's stop function which caused difficult to debug behavior. To prevent this in the future we now prefix each function that is responsible for an action with 'action_' * Cleanup * actions: Throw exception when re-registering action Action names are unique inside modules. Unfortunately there is no way to ensure this statically, the next best thing is to crash the module and let the user know that this is a bug. * Formatting * actions: Ignore data for actions without data This is the same behavior as before. * action_router: Write tests
2021-01-04 10:25:52 +01:00
m_router->register_action(EVENT_TOGGLE, &systray_module::action_toggle);
wip(systray): Add module base
2017-01-01 21:28:28 +01:00
// Add formats and elements
m_formatter->add(DEFAULT_FORMAT, TAG_LABEL_TOGGLE, {TAG_LABEL_TOGGLE, TAG_TRAY_CLIENTS});
if (m_formatter->has(TAG_LABEL_TOGGLE)) {
m_label = load_label(m_conf, name(), TAG_LABEL_TOGGLE);
}
}
/**
* Update
*/
void systray_module::update() {
if (m_label) {
m_label->reset_tokens();
m_label->replace_token("%title%", "");
}
broadcast();
}
/**
* Build output
*/
bool systray_module::build(builder* builder, const string& tag) const {
if (tag == TAG_LABEL_TOGGLE) {
actions: Separate data from action string Modules now no longer need to manually parse the action string and extract data from it.
2020-05-24 00:36:16 +02:00
builder->action(mousebtn::LEFT, *this, EVENT_TOGGLE, "", m_label);
wip(systray): Add module base
2017-01-01 21:28:28 +01:00
} else if (tag == TAG_TRAY_CLIENTS && !m_hidden) {
builder->append(TRAY_PLACEHOLDER);
} else {
return false;
}
return true;
}
/**
* Handle input event
*/
module: Implement action router (#2336) * module: Implement proof of concept action router Action implementation inside module becomes much cleaner because each module just registers action names together with a callback (pointer to member function) and the action router does the rest. * Make input function final This forces all modules to use the action router * modules: Catch exceptions in action handlers * Use action router for all modules * Use action_ prefix for function names The mpd module's 'stop' action overwrote the base module's stop function which caused difficult to debug behavior. To prevent this in the future we now prefix each function that is responsible for an action with 'action_' * Cleanup * actions: Throw exception when re-registering action Action names are unique inside modules. Unfortunately there is no way to ensure this statically, the next best thing is to crash the module and let the user know that this is a bug. * Formatting * actions: Ignore data for actions without data This is the same behavior as before. * action_router: Write tests
2021-01-04 10:25:52 +01:00
void systray_module::action_toggle() {
wip(systray): Add module base
2017-01-01 21:28:28 +01:00
m_hidden = !m_hidden;
broadcast();
}
module: Implement action router (#2336) * module: Implement proof of concept action router Action implementation inside module becomes much cleaner because each module just registers action names together with a callback (pointer to member function) and the action router does the rest. * Make input function final This forces all modules to use the action router * modules: Catch exceptions in action handlers * Use action router for all modules * Use action_ prefix for function names The mpd module's 'stop' action overwrote the base module's stop function which caused difficult to debug behavior. To prevent this in the future we now prefix each function that is responsible for an action with 'action_' * Cleanup * actions: Throw exception when re-registering action Action names are unique inside modules. Unfortunately there is no way to ensure this statically, the next best thing is to crash the module and let the user know that this is a bug. * Formatting * actions: Ignore data for actions without data This is the same behavior as before. * action_router: Write tests
2021-01-04 10:25:52 +01:00
} // namespace modules
wip(systray): Add module base
2017-01-01 21:28:28 +01:00
POLYBAR_NS_END
#endif
Reference in a new issue Copy permalink