home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Skins and Design
Design Guidelines - Best Practices
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="morpheus_xx" data-source="post: 1035529" data-attributes="member: 48495"><p>I also prefer to have a consistent screen layout (means not to hide labels if content is missing). While we can implement fallback texts already using MultiBinding, it would cause a lot of (XAML-)overhead for each label. A new "FallbackContent" property would be easier.</p><p>Another, probably the architectural best way, is a converter, which simply returns the text, or fallbacktext. This way the Label control doesn't need to be extended and the converter can be used inside any other place where texts are required.</p></blockquote><p></p>
[QUOTE="morpheus_xx, post: 1035529, member: 48495"] I also prefer to have a consistent screen layout (means not to hide labels if content is missing). While we can implement fallback texts already using MultiBinding, it would cause a lot of (XAML-)overhead for each label. A new "FallbackContent" property would be easier. Another, probably the architectural best way, is a converter, which simply returns the text, or fallbacktext. This way the Label control doesn't need to be extended and the converter can be used inside any other place where texts are required. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Skins and Design
Design Guidelines - Best Practices
Contact us
RSS
Top
Bottom