Label alignment reseting


I have an wierd problem where the text alignment resets to leftside when the bound property is updated. I don't know why this would happen, all graphics in the view are made trought the xaml so nothing should affect the alignment.


Have anyone seen something similar before?


Best Answer


  • ClintStLaurentClintStLaurent USUniversity ✭✭✭✭✭

    Similar... I've seen text alignment do funny things like that before. But nothing on such a basic situation as you described.
    I would see alignment change if the same instance of a page was taken down and put back up... Or if the width of the containing grid changed. In the end I found it unreliable. So I played games with putting a label in a grid and changing the alignment of the label relattive to the grid, instead of changing the textalignment of the label.

    I've not seen a label alignment change just for the binded text property changing. It seem that if some so very rudimentary were happening everywhere it would have raised a lot of flags by now.

    A bug isn't a bug until it happens on a physical device. Is this happening on a real device, or an emulator?
    What OS and device?

  • TobiasLavingTobiasLaving SEMember ✭✭

    Thanks for quick response!

    This happens on both device and emulator, tested different version of OS but all of the display the same problem.
    Weird thing is that this is only affecting some of the labels not all of them. And not always the same over different platforms...

    The problem can be "reseted" by tilting the screen on the side and then back upp again. The problem happens when I use and reload function on another tab, thus getting new values.

    Any idea to bypass this? Using grids you say?

  • SagarPanwalaSagarPanwala USMember ✭✭

    @ClintStLaurent : Did you reported to bug zilla in xamarin ? Please report there, looks like Xamarin Team not seeing this forum. It will help many developers.

  • ClintStLaurentClintStLaurent USUniversity ✭✭✭✭✭
    edited October 4

    @SagarPanwala Bugzilla has been dead for over a year. That's no where you report issues any longer. They are now reported at the nuget issues page.

    And yes, it was reported there even though it was automatically carried over from bugzilla. Then they closed it; I don't remember why. They simply don't want to fix it.

    CC: @DavidOrtinau @JGoldberger
    Hey David... Is there any point re-reporting this bug? Everyone knows about. It comes up at least once a month here in the forum. But it seems like y'all just aren't interested in fixing it because it been reported (3 times by me alone) either to bugzilla or the current issues system. And somehow it mysteriously falls off the system or gets closed.

  • SagarPanwalaSagarPanwala USMember ✭✭

    @ClintStLaurent : I faced the same issue too many times, but not reported, because this forums has lack of supervision from Dev Team(Perhaps).

Sign In or Register to comment.