Home Dashboard Directory Help
Search

TextAlignment Doesn't Work For Label, Text & Money Controls In Grids Any More by Yann Duran


Status: 

Resolved
 as Other Help for as Other


15
0
Sign in
to vote
Type: Bug
ID: 682596
Opened: 8/1/2011 4:24:33 PM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

In B2 the "horizontal alignment" setting affected the *control* itself, based on the width that was available from its parent container, centering, or right-aligning the control in that width. I didn't use it (mainly because the results were a bit weird for me), but it made sense for it to do so. The "text alignment" setting did exactly what it said, it aligned the *text* within the control (& was the only way to get the text aligned as required). I used that setting to center, or right-align many displayed values. This behavior was consistent across all controls. Only column headings remained "out of whack", always being left-aligned no matter what alignment was chosen for the column's control (but that's a different problem).

Now, in RTM, all of the text alignments that I've set for "label" or "money" controls (there may be others that I haven't used, or tested) are now *ignored*, & the setting that formerly aligned the *control* is now the only way for *text* in those controls to be aligned the way I want. BUT, for a "label" control, "text" control, and "summary" control, the behavior remains the way it used to be.

Now it's bad enough that the behavior was changed so radically in the first place, "by design", as it means that controls that were given a specific desired behavior by the developer suddenly started behaving differently, but the BIG problem is that the behavior is now *inconsistent*, depending on which control you're dealing with.

The major problem is that there is now inconsistencies in the way you have to set alignment for different controls.

This post in the LS forum, http://social.msdn.microsoft.com/Forums/en-US/lightswitch/thread/5a0296a6-0ffd-4883-91f2-e214f7c26790/, contains more details & discussion.

The issue has also been confirmed by Eric Gruber.

"I'm clear on the issue you're seeing now, unfortunately I don't have a very satisfying answer. It looks like the change was an unintentional regression specific to those properties on controls within the grid. "
Details
Sign in to post a comment.
Posted by Microsoft on 1/16/2012 at 3:55 PM
We are closing this for now. If you have more data or information to provide, feel free to reactivate this bug.
Posted by Yann Duran on 1/3/2012 at 4:17 PM
Hi Doug,

Thanks for taking the time to provide that update. And also thank you SO much for actually including your name. I wish ALL replies from any MS employee had a name.

Yann
Posted by Microsoft on 1/3/2012 at 10:34 AM
Hi Yann,

Just a quick update here. This bug is active, not resolved. The Connect bug status did not sync with the resolution in our internal bug database, and the Connect team is looking into that. But the bug is active, and is currently under investigation. Apologies for the sync issue with Connect.

Doug Turnure
Visual Studio PM
Posted by Microsoft on 12/20/2011 at 12:24 PM
Thank you for your feedback. This issue is being reviewed directly with the original poster to ensure the right scenario is being tracked.
Posted by Yann Duran on 10/20/2011 at 5:30 PM
Why has this been set to "won't fix", without so much as a word of explanation as to "why"?

Not only is this behavior *wrong*, it's *inconsistent* across controls!

Having created control extensions myself, I can see why this behavior is happening, & it's easy enough to "fix".

Yann
Sign in to post a workaround.