Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signals for GUI #302

Open
michaelheilmann opened this issue Sep 7, 2016 · 0 comments
Open

Signals for GUI #302

michaelheilmann opened this issue Sep 7, 2016 · 0 comments
Assignees
Milestone

Comments

@michaelheilmann
Copy link
Contributor

michaelheilmann commented Sep 7, 2016

The GUI shall use the signals library.
For instance, a button typically provides the clicked signal:

class Button ... {
    ....
public:
   idlib::signal<void()> Clicked;
   ....
};

Reasonable class hierarchies will drastically reduce the number of signals a component at the bottom of the component hierarchy has to define: For instance, a button typically derives from a component that already defines the signals Signal<void()> TextChanged; and Signal<void()> FontChanged;.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants