Bug 10635 - GridLayout not accepting children
Summary: GridLayout not accepting children
Status: RESOLVED DUPLICATE of bug 10597
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Designer ()
Version: 4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2013-02-25 05:33 UTC by Claudio Mezzasalma
Modified: 2013-03-12 12:11 UTC (History)
0 users

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 DUPLICATE of bug 10597

Description Claudio Mezzasalma 2013-02-25 05:33:20 UTC
Description of Problem:

GridLayout doesn't accept children views by dragging them in from the toolbox. Writing them manually in the XML works ok.

Steps to reproduce the problem:
1. Open a Layout file
2. Create a GridLayout
3. Drag a view in the GridLayout

Actual Results:

Nothing is dragged in the GridLayout, no child appended to the GridLayout

Expected Results:

A new child view should be created

How often does this happen? 

Always

Additional Information:

API14 (Ice Cream Sandwich project)
Comment 1 Lluis Sanchez 2013-03-12 12:11:30 UTC

*** This bug has been marked as a duplicate of bug 10597 ***