Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Library : Other (not classified elsewhere) » why not StaticText::SetData != StaticText::SetText
Re: why not StaticText::SetData != StaticText::SetText [message #30018 is a reply to message #30017] Fri, 03 December 2010 12:09 Go to previous messageGo to previous message
kohait00 is currently offline  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..
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [bug report]problem about processing WM_PAINT message
Next Topic: CtrlCore.h const correctnes fixes
Goto Forum:
  


Current Time: Sun Aug 24 19:17:40 CEST 2025

Total time taken to generate the page: 0.00349 seconds