Bug 24274 - Parameter order matters when using AbsoluteLayout
Summary: Parameter order matters when using AbsoluteLayout
Status: VERIFIED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.3
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-11-05 04:50 UTC by Tumis
Modified: 2015-02-05 07:32 UTC (History)
4 users (show)

Tags:
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:
Status:
VERIFIED FIXED

Description Tumis 2014-11-05 04:50:41 UTC
When using AbsoluteLayout and setting AbsoluteLayout.SetLayoutBounds and AnchorX for a child it works differently when setting parameters in different order.
Best to see it on BoxViewClock example (http://developer.xamarin.com/samples/BoxViewClock/)
swapping lines 99 and 100 with line 94 in file BoxViewClockPage.cs,
from:
                boxView.AnchorX = 0.51;
                boxView.AnchorY = handParams.Offset;

                AbsoluteLayout.SetLayoutBounds(boxView,
                    new Rectangle(center.X - 0.5 * width,
                                  center.Y - offset * height,
                                  width, height));
(above works ok)
to:
                boxView.AnchorX = 0.51;
                boxView.AnchorY = handParams.Offset;

                AbsoluteLayout.SetLayoutBounds(boxView,
                    new Rectangle(center.X - 0.5 * width,
                                  center.Y - offset * height,
                                  width, height));
(above works wrong)
The clock handles (boxviews) are positioned+rotated incorrectly. Looks like the anchors are treated as pixel positions rather than percentage values.

It is not possible to define it correctly in xaml.
Trying to set the same values in xaml always produces wrong result:
<BoxView x:Name="secondHand" Color = "Accent" AbsoluteLayout.LayoutBounds="191,122,3,191" AnchorX="0.51" AnchorY="0.85"></BoxView>
(Tried this on Android device and Xamarin Android Player)
Comment 1 Tumis 2014-11-05 04:54:35 UTC
Sorry, A copy/paste error.
The following works ok:

                AbsoluteLayout.SetLayoutBounds(boxView,
                    new Rectangle(center.X - 0.5 * width,
                                  center.Y - offset * height,
                                  width, height));

                boxView.AnchorX = 0.51;
                boxView.AnchorY = handParams.Offset;
Comment 2 Udham Singh 2014-11-05 06:06:36 UTC
I have checked this issue by following the instructions provided in bug description and getting the same behaviour mentioned in bug. Please refer the screencast : http://www.screencast.com/t/bXVHDoOstwk

Environment Info :

=== Xamarin Studio ===

Version 5.5.3 (build 6)
Installation UUID: ce927b2a-2c07-44c5-b186-09cfdafba6dc
Runtime:
	Mono 3.10.0 ((detached/e204655)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000023

=== Xamarin.Android ===

Version: 4.18.1 (Business Edition)
Android SDK: /Users/xamarin76/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.0    (API level 11)
		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)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Apple Developer Tools ===

Xcode 6.0.1 (6528)
Build 6A317

=== Xamarin.Mac ===

Version: 1.10.0.18 (Business Edition)

=== Xamarin.iOS ===

Version: 8.4.0.16 (Business Edition)
Hash: 80e9ff7
Branch: 
Build date: 2014-10-22 15:09:12-0400

=== Build Information ===

Release ID: 505030006
Git revision: fbe3e9453daf6a3bb9a9709ed22bec35f7c9056b
Build date: 2014-10-23 13:08:38-04
Xamarin addins: e44add2b39de4dd57c0742bb2e620dfad84c64c6

=== Operating System ===

Mac OS X 10.9.4
Darwin Xamarin76s-Mac-mini.local 13.3.0 Darwin Kernel Version 13.3.0
    Tue Jun  3 21:27:35 PDT 2014
    root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
Comment 3 Jason Smith [MSFT] 2015-02-05 06:03:34 UTC
This is resolved
Comment 4 Udham Singh 2015-02-05 07:32:49 UTC
I have checked this issue with Xamarin.Forms 1.3.3.6321-pre2 and now this is working fine. Hence closing this issue. Screencast : /Users/xamarin76/Desktop/26757.png

Environment Info : 

Xamarin.Forms 1.3.3.6321-pre2 

Mac OS X 10.9.5
Xamarin Studio 5.7.1 (build 17)
Mono 3.12.0 ((detached/a813491)
GTK+ 2.24.23 (Raleigh theme)
Xcode 6.1.1 (6611)
Xamarin.iOS 8.6.1.24 (Business Edition)
Xamarin.Android 4.20.0.28 (Business Edition)