Bug 13769 - Selection handle don't take translation attribute into account
Summary: Selection handle don't take translation attribute into account
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Designer ()
Version: unspecified
Hardware: PC Mac OS
: Low normal
Target Milestone: master
Assignee: Jérémie Laval
URL:
Depends on:
Blocks:
 
Reported: 2013-08-05 23:23 UTC by Jérémie Laval
Modified: 2017-07-18 16:32 UTC (History)
2 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:
RESOLVED NOT_REPRODUCIBLE

Description Jérémie Laval 2013-08-05 23:23:39 UTC
http://screencast.com/t/kiz9xfOw7

In this example, the lower black FrameLayout has a translationY set.
Comment 1 Lluis Sanchez 2013-10-24 14:15:05 UTC
The Android SDK is not giving the translated position of the widget, so this doesn't have an easy solution. Eclipse and Android Studio have the same problem. Lowering priority since I have no plans to fix this for now.
Comment 2 Jason DeBoever 2017-07-18 16:32:01 UTC
Thanks so much for taking the time to submit this report! I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.1, and I was unable to hit the problem. If this issue is still occurring for you, please reopen this report and attach a reproduction, ideally starting with a new template project and then adding just the code necessary to demonstrate the issue