diff options
author | Robin Gareus <robin@gareus.org> | 2017-07-01 21:11:14 +0200 |
---|---|---|
committer | Robin Gareus <robin@gareus.org> | 2017-07-01 21:19:56 +0200 |
commit | b976bf8986290e8f4812a50e7fdd98b9cbeb4249 (patch) | |
tree | 75cffb9761a024943c18e502a3d84e3607954a55 /gtk2_ardour/color_theme_manager.h | |
parent | 221902138938a47f32b925f7e37602230e9de538 (diff) |
NO-OP whitespace & foratting of header files
Diffstat (limited to 'gtk2_ardour/color_theme_manager.h')
-rw-r--r-- | gtk2_ardour/color_theme_manager.h | 38 |
1 files changed, 19 insertions, 19 deletions
diff --git a/gtk2_ardour/color_theme_manager.h b/gtk2_ardour/color_theme_manager.h index 104bca847b..9049c8b744 100644 --- a/gtk2_ardour/color_theme_manager.h +++ b/gtk2_ardour/color_theme_manager.h @@ -41,7 +41,7 @@ class ArdourDialog; class ColorThemeManager : public OptionEditorMiniPage { - public: +public: ColorThemeManager(); ~ColorThemeManager(); @@ -62,13 +62,13 @@ class ColorThemeManager : public OptionEditorMiniPage Gtk::Widget& tip_widget(); - private: +private: Gtk::Button reset_button; Gtk::Notebook notebook; /* handls response from color dialog when it is used to - edit a derived color. - */ + * edit a derived color. + */ void palette_color_response (int, std::string); Gtk::ScrolledWindow palette_scroller; @@ -76,29 +76,29 @@ class ColorThemeManager : public OptionEditorMiniPage ArdourCanvas::Container* palette_group; /* these methods create and manage a canvas for use in either the - palette tab or in a separate dialog. Different behaviour is - accomplished by changing the event handler passed into the - allocation handler. We do it there because we have to rebuild - the canvas on allocation events, and during the rebuild, connect - each rectangle to the event handler. - - the alternative is one event handler for the canvas and a map - of where each color rectangle is. nothing wrong with this - but the per-rect event setup is simpler and avoids building - and looking up the map information. - */ + * palette tab or in a separate dialog. Different behaviour is + * accomplished by changing the event handler passed into the + * allocation handler. We do it there because we have to rebuild + * the canvas on allocation events, and during the rebuild, connect + * each rectangle to the event handler. + * + * the alternative is one event handler for the canvas and a map + * of where each color rectangle is. nothing wrong with this + * but the per-rect event setup is simpler and avoids building + * and looking up the map information. + */ ArdourCanvas::Container* initialize_palette_canvas (ArdourCanvas::Canvas& canvas); void build_palette_canvas (ArdourCanvas::Canvas&, ArdourCanvas::Container&, sigc::slot<bool,GdkEvent*,std::string> event_handler); void palette_canvas_allocated (Gtk::Allocation& alloc, ArdourCanvas::Container* group, ArdourCanvas::Canvas* canvas, sigc::slot<bool,GdkEvent*,std::string> event_handler); void palette_size_request (Gtk::Requisition*); /* handles events from a palette canvas inside the palette (derived - colors) tab - */ + * colors) tab + */ bool palette_event (GdkEvent*, std::string name); /* allows user to edit a named color (e.g. "color 3") after clicking - on it inside the palette tab. - */ + * on it inside the palette tab. + */ void edit_palette_color (std::string); struct ColorAliasModelColumns : public Gtk::TreeModel::ColumnRecord { |