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.
When editing width and height layout constraints in the Xamarin iOS Designer if you try to set the multiplier field to a decimal (e.g. 0.25 or .25), the value is rounded to the nearest whole number and thrown out.
Layout constraint multipliers should be able to be set, and calculate as decimals.
1) File > New > Project > iPhone > Blank App
2) Right click the project in the Solution Explorer pane and click Add > New Item > Empty Storyboard
3) Once the designer has loaded and the Toolbox pane has populated, find and drag a new View Controller onto the storyboard
4) Drag a new Image View onto that View Controller
5) Click the Image View until the Width Constraint handle is visible (the width "bone")
6) Click and drag the Width Constraint handle onto the underlying View Controller
7) View the Width Constraint you've just created by ensuring the Image View is highlighted, and then opening the Properties pane > Layout tab
8) Double click the Width Constraint to edit it
9) Edit the width constraint property "Multiplier" field, and enter either 0.25 or .25, then hit enter
10) Upon hitting enter, the field will turn to 0, which is incorrect
11) You can repeat steps 7 & 8 from here to verify that the value does not get saved properly
Let me know if any other details are needed...
Also, my version information:
Visual Studio: 15.2 (26430.14) Release
*** This bug has been marked as a duplicate of bug 55888 ***
Thanks for reporting the issue - it has already been fixed and the patch is shipping as part of the 15.3 series. I expect that to go to stable relatively soon, but it is already available as a preview release.