Bug 35564 - [Xib Support] Incorrect frame for UISwitch in Table Cell in Xib
Summary: [Xib Support] Incorrect frame for UISwitch in Table Cell in Xib
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS Designer ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Vinicius Jarina
Depends on:
Reported: 2015-11-04 23:29 UTC by Alex Corrado [MSFT]
Modified: 2016-01-27 19:54 UTC (History)
6 users (show)

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

Example xib (1.84 KB, application/octet-stream)
2015-11-04 23:29 UTC, Alex Corrado [MSFT]

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 Alex Corrado [MSFT] 2015-11-04 23:29:51 UTC
Created attachment 13681 [details]
Example xib

1) Create new Table Cell xib template in XS (also works with a table cell added to a xib in VS)
2) Add a UISwitch to the cell
3) Select the UISwitch and observe that the selection rectangle is not the right shape/size

Attached an example xib for convenience.
Comment 1 Alan McGovern 2015-11-05 01:38:11 UTC
This is how it looks in Xcode. Is it also how it looks in our designer? http://screencast.com/t/Gg3ZLr2N

If so it looks like the problem is just the the frame written to the xml is incorrect. We should look into the 'drop' part of our drag drop and make sure the frame is correct then, then we should make sure it's correct after we render and update the xml with the actual frames. It works for me locally.