Bug 44739 - Property editor of constraints of document overview does not reflect actual value in storyboard
Summary: Property editor of constraints of document overview does not reflect actual v...
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.2.0 (C8)
Hardware: Macintosh Mac OS
: --- critical
Target Milestone: 15.3
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-09-26 13:59 UTC by Robert van Hoornaar
Modified: 2017-05-29 12:00 UTC (History)
12 users (show)

Tags: potentialC8SR2
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
VERIFIED FIXED

Description Robert van Hoornaar 2016-09-26 13:59:04 UTC
# 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)
Comment 1 Jose Gallardo 2016-09-26 20:20:28 UTC
Moving to Component: iOS Designer for visibility from the right team.
Comment 2 Vinicius Jarina 2016-11-15 17:53:16 UTC
http://www.screencast.com/t/2ffScWINV
Comment 3 Andreas B 2017-02-10 16:28:02 UTC
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.
Comment 4 Robert van Hoornaar 2017-04-19 08:07:01 UTC
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.
Comment 5 Robert van Hoornaar 2017-05-22 13:07:49 UTC
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.
Comment 6 Alan McGovern 2017-05-23 14:15:31 UTC
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.
Comment 7 xamarin-release-manager 2017-05-27 14:35:21 UTC
Fixed in version 4.6.0.177 (master)

Author: Alan McGovern
Commit: 81800f3713b98d8f2795fc8c9fc881c01055d902 (xamarin/md-addins)
Included in Commit: d95b3751000dc59c32e0345f93d526082087d733 (xamarin/XamarinVS)
Comment 8 Jacky Waswani 2017-05-29 12:00:28 UTC
Have verified the bug on 4.6.0.177 taken from master. Issue is seems to be fixed in the above mentioned version.

Hence marking the bug is verified.

Tested on:
Windows machine - VS 2017
Gist Info : https://gist.github.com/mohakbarokar/f125e8f64806eec6b2565f76f1ae9a25

Screencast: https://www.screencast.com/t/uOJwFm4Ta8l