Bug 14080 - Constraints have regressed
Summary: Constraints have regressed
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS Designer ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: 5.0
Assignee: Alan McGovern
Depends on:
Reported: 2013-08-19 15:00 UTC by Alan McGovern
Modified: 2014-05-01 09:19 UTC (History)
4 users (show)

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 or GitHub 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:

Description Alan McGovern 2013-08-19 15:00:33 UTC
There are several bugs in constraints. These can all be reproed using a single button on a ViewController when in constraint design mode:

1) The button cannot be aligned to either the right margin or the right edge of the ViewController.
2) Any time a trailing constraint would be placed on the right edge of the button the button ends up in the wrong place
3) If the button is enlarged so it's right edge is on the right margin or right edge of the ViewController and then the button is moved, it loses it's Width constraint.
4) The button cannot be aligned to the bottom edge or bottom margin of the ViewController.
Comment 1 Alan McGovern 2013-08-29 15:01:48 UTC
All of these issues stemmed from the same minor bug which I fixed (with a test) last week.
Comment 2 Mohit Kheterpal 2014-05-01 09:19:22 UTC
Today I have checked this issue and now these issues does not exist as shown in screencast : http://www.screencast.com/t/begOLGaMJ5

Hence closing this issue.

Environment info :
=== Xamarin Studio ===

Version 5.0 (build 827)
Installation UUID: 449f40dd-b3f1-4028-9a6b-cca0d1a2307d
	Mono 3.4.0 ((no/c3fc3ba)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 304000204

=== Apple Developer Tools ===

Xcode 5.1.1 (5085)
Build 5B1008

=== Xamarin.iOS ===

Version: (Starter Edition)
Hash: d3d795d
Build date: 2014-04-30 19:56:48-0400

=== Xamarin.Android ===

Version: 4.12.4 (Starter Edition)
Android SDK: /Users/360logicaxamarinmacmini/Desktop/android-sdk-macosx
	Supported Android versions:
		1.6   (API level 4)
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		3.2   (API level 13)
		4.0   (API level 14)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.3   (API level 18)
		4.4   (API level 19)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

=== Xamarin.Mac ===


=== Build Information ===

Release ID: 500000827
Git revision: 747fa219a4d670fe65968695bc1c8256b093e3c5
Build date: 2014-04-30 19:24:15-04
Xamarin addins: 1d9c0d1af3a11562e387a4739b0af66f8339f4cc

=== Operating System ===

Mac OS X 10.8.4
Darwin 360Logicas-Mac-mini.local 12.4.0 Darwin Kernel Version 12.4.0
    Sun Mar 10 18:01:10 PDT 2013
    root:xnu-2050.24.6~1/RELEASE_X86_64 x86_64