Bug 12398 - Frame.Location no longer allows assignment
Summary: Frame.Location no longer allows assignment
Alias: None
Product: iOS
Classification: Xamarin
Component: Pre-release ()
Version: 6.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-05-25 10:19 UTC by hani
Modified: 2014-11-21 09:05 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 hani 2013-05-25 10:19:32 UTC
On the beta channel v6.3.5.43 can no longer assign a new point to location object

Doing this 

PointF loc = lblFleetName.Frame.Location;
lblDriverStatus.Frame.Location = loc;

now throws the following error during compile

Error CS1612: Cannot modify a value type return value of `MonoTouch.UIKit.UIView.Frame'. Consider storing the value in a temporary variable (CS1612) (Passenger.iOS)
Comment 1 Sebastien Pouliot 2013-05-25 12:21:19 UTC
That's normal. The new `mcs`compiler is better and detect that you're assigning to a value type (not an object reference). 

IOW the code was not doing what you think it was (check the values, before and after, using the old compiler).
Comment 2 Mike Gledhill 2014-11-21 09:05:21 UTC
November 2014.

This is flagged as being a "resolved feature".

Really ?

This is still a bug.
If I hover over the Location tag, it still tells me that this is a { get; set; } value.
It isn't.

If setting this value isn't allowed, at least tell the Intellisense to stop misleading us.

Xamarin Studio for Mac, v5.5.3  (build 6)