Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
# Steps to reproduce
Create a label on a controller
set the layout constraints (may be done automatic)
change a value of a constraint
# Expected behaviour
Th property editor should represent the actual value as stated in the document outline
When changed, the value in the document outline should change
Moving to another constraint the value in the property editor should reveal the selected constraints value
# Actual behaviour
The value in the property editor does not "follow" the navigation in the document outline. When you change ie the trailing constraint to 40 and press enter then the value is updated in the document outline. However, when you then select the leading constraint (which is ie on the value 20) and do nothing, the you see the value in the document outline changed to 40 (the value of the previous constrain you where editing) when saving the storyboard.
# Supplemental info (logs, images, videos)
# Test environment (full version information)
Moving to Component: iOS Designer for visibility from the right team.
This issue has importance critical. Are there any plans yet when this can be looked into? Has the right team noticed it?
It's something that slows down the development quite a bit.
Hugging and compression for a view has the same problem btw, but I guess that might be for another issue.
I understand that there are a lot of priority number 1 issues, but this one is really a b**ch to work with. Half of the time my GUI is totally disordered because changes I accidentally made to the properties because of this bug.
It is already reported over half a year ago. When is this going to be picked up. Have you ever tried wording with the storyboard designer and adjust constraints in the document overview on a controller with more than 15 elements?
Try doing that, and you will go solve this bug right away.
And also the new Visual Studio 2017 for MAC has the same problem. I will try to do the same with my customers. Confirm its a critical bug, but not going to solve. I don't think they would like that.
Thanks for floating this issue up again. We've got it patched internally and it should ship as part of the next major release.
I believe the initial importance level was set externally, not by our own team which resulted in the issue being improperly triaged. We should have addressed it before now.
Fixed in version 220.127.116.11 (master)
Author: Alan McGovern
Commit: 81800f3713b98d8f2795fc8c9fc881c01055d902 (xamarin/md-addins)
Included in Commit: d95b3751000dc59c32e0345f93d526082087d733 (xamarin/XamarinVS)
Have verified the bug on 18.104.22.168 taken from master. Issue is seems to be fixed in the above mentioned version.
Hence marking the bug is verified.
Windows machine - VS 2017
Gist Info : https://gist.github.com/mohakbarokar/f125e8f64806eec6b2565f76f1ae9a25