U++ framework: U++ Library : Other (not classified elsewhere) » why not StaticText::SetData != StaticText::SetText

Home » U++ Library support » U++ Library : Other (not classified elsewhere) » why not StaticText::SetData != StaticText::SetText

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

why not StaticText::SetData != StaticText::SetText [message #30016]

Fri, 03 December 2010 11:29

kohait00
Messages: 939
Registered: July 2009
Location: Germany

Experienced Contributor

hi guys

StaticText and Label have empty GetData() / SetData()
and one cant set the text trough them. but it'd be great
is there a reason why?

wo why not mapping GetData / SetData to GetText / SetText
i.e.:

virtual void SetData(const Value& v) { SetText(AsString(v)); }
virtual Value GetData() const { return GetText(); }

note the conversion above, to surely be able to display everyting..

or do StaticText / Label have special implications in terms of Ctrl usage?

i know of DataPusher, which is sort of sth like the same, isn't it?
but for StaticText Label, it'd be really great as well

Report message to a moderator

Re: why not StaticText::SetData != StaticText::SetText [message #30017 is a reply to message #30016]

Fri, 03 December 2010 11:56

koldo
Messages: 3458
Registered: August 2008

Senior Veteran

I agree.

Best regards
Iñaki

Report message to a moderator

Re: why not StaticText::SetData != StaticText::SetText [message #30018 is a reply to message #30017]

Fri, 03 December 2010 12:09

kohait00
Messages: 939
Registered: July 2009
Location: Germany

Experienced Contributor

i asked mirek once for ProgressIndicator...
http://www.ultimatepp.org/forum/index.php?t=msg&goto=293 35&#msg_29335

hi response is sort of logical,

Quote:

Not quite sure it is completely right:

ProgressIndicator is kind of static value - user cannot change it. So far the policy was that only widgets that are editable have Value.

The reason is that if you want to store all user supplied values in the dialog, you can simply go through all widgets and store the value if it is not Value::Void - that indicates that the widget does not have associated value.

but i'd prefer to have them all be accessible via the GetSetData as well, and in case of restoring sth..just make sure that exceptions are reinitialized well after restoring..

Report message to a moderator