Bug 5764 - Component adding/ordering broken in Document Outline (VS2010)
Summary: Component adding/ordering broken in Document Outline (VS2010)
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 4.2.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2012-06-19 18:01 UTC by Justin Johnson
Modified: 2012-06-21 12:37 UTC (History)
1 user (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 FIXED

Description Justin Johnson 2012-06-19 18:01:40 UTC
(this bug exists in version 4.2.2, haven't tested in latest version)

Dragging components into many Layout/View types is difficult to do accurately in the designer view in many cases. The user should be able to drag components into valid containers in the Document Outline pane to make accurate hierarchy easier.

It appears that this functionality is intended: When dragging, I see the standard windows drag/drop cursor flicker briefly to be replaced by the cursor indicating that the component cannot be dropped.
Comment 1 Lluis Sanchez 2012-06-21 12:37:49 UTC
This is already fixed. The fix will be included in the next release.