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.
Note: This affects both VS and XS.
Steps to reproduce:
1) Create a new storyboard project
2) Open the storyboard in the iOS Designer
3) Zoom out
2) Add a view controller to the storyboard by dragging it from the toolbox to the design surface.
The location of the control when the MouseUp event fires is the exact location it is added on the design surface
The location of the control differs from the location of the MouseUp event.
This is occurring as of:
Alan and I have discussed this, but it is still unsupported and so should be filed publicly.
Xcode allows addition, manipulation, and deletion of view controllers from the zoomed-out state, but not views or controls.
This is fixed in master and 5.0 now. There are cases where our co-ordinates might be off by a few pixels, but since the user is already working in a non-pixel-accurate zoomed out state, this it not an issue which warrants keeping this bug report open.
I have checked this issue with the latest XS 5.0 build.Now in Zoomed out state, If we add control like tab bar it moves to some pixel but in acceptable limit and for control like GlView ,View controller etc Location of the control not differs when we add on design surface.
Below is the screencast for the same:
Windows 7/MAC 10.8.4
XS 5.0(build 866)
Hence verifying this issue.