Fix: Workaround label constructor selecting bool instead nana::string when called with nana::char_t* which silently brake a lot of code
Maybe there are more elegant solutions... The second constructor was eliminated in: Commit: f4924ef2f8600fafa82d3fc0d1c4d5f9eea0c738 [f4924ef] Parents: e0ee42d184 Author: Jinhao <cnjinhao@hotmail.com> Date: Sonntag, 2. August 2015 19:37:36 Labels: develop add throw() for some functions
This commit is contained in:
parent
c059bd256a
commit
ae3c9f6357
@ -58,6 +58,7 @@ namespace nana
|
|||||||
label();
|
label();
|
||||||
label(window, bool visible);
|
label(window, bool visible);
|
||||||
label(window, const nana::string& text, bool visible = true);
|
label(window, const nana::string& text, bool visible = true);
|
||||||
|
label(window parent, const nana::char_t* text, bool visible = true) :label(parent, nana::string(text),visible) {};
|
||||||
label(window, const rectangle& = {}, bool visible = true);
|
label(window, const rectangle& = {}, bool visible = true);
|
||||||
label& transparent(bool); ///< Switchs the label widget to the transparent background mode.
|
label& transparent(bool); ///< Switchs the label widget to the transparent background mode.
|
||||||
bool transparent() const throw();
|
bool transparent() const throw();
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user