UI to set one widget as master and others are the slave or a button to adopt the master settings

[DanielFloeter]

Use the "API for external use" #114

[markkap]

+1 to set a widget as default for settings of new widgets. -1 to master/slave I think default setting does almost the same and it is more elegant

[DanielFloeter]

So "set as default" can be also a good name. With "default" you have the mentioned collision with the widget default settings. But this is what I called and implement as "adopt to the master" button.

Master/slave is to administrate or change settings, only at one widget and change all my slave widgets.

[markkap]

master and slave is too confusing as you can never know what will be the
exact impact of a change on the master on all the widgets.

"Adopt setting" for chose settings from another widget can also be a nice
idea, maybe better than a default...but the UI will be hard

On Sun, Oct 23, 2016 at 9:40 AM, Daniel Flöter [email protected]
wrote:

So "set as default" can be also a good name. With "default" you have the
mentioned collision with the widget default settings. But this is what I
called and implement as "adopt to the master" button.

Master/slave is to administrate or change settings, only at one widget and
change all my slave widgets.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#118 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJnmnbOWWi5E3JWyBZK70T-cs5V88ivks5q2wFggaJpZM4KeD77
.

[markkap]

Was thinking about it now.... we need a "button" to select the widget as template, sstore the widget id in an option and use it to populate new widgets