Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
This issue also affects C# files.
After reopening the project, the "sub"-file rests in the new position -- very weird and unintuitive.
Redirect from https://github.com/aBothe/Mono-D/issues/295
This is a feature for grouping related files e.g CodeBehind.
Why does this work for all files? I accidentally dragged a .png file into another .png file – what does this mean? This seems like an unintended consequence of code that is too general.
Created attachment 4527 [details]
Yo dawg I heard you like pngs to I put a png in your png so you can png while you ping
There is no reliable, correct way to determine for two files whether it makes sense to group them. Only the user can decide that. And why can png files not be related? E.g. you could choose to group icon variants.
This breaks the user's model about how files and folders behave. I am familiar with the concept of code-behind files and I immediately assumed this was a bug – imagine the confusion that an errant file-on-file drag-and-drop will instill in the vast majority of our users, despite the fact that I agree with your use case.
I will think of something we can do to mitigate this confusion; perhaps we can subtly change the top-level icon for grouped files to indicate that this is a feature, not a bug. Also, offering a simple "Ungroup Files" item on the parent node could be useful for unpacking these groups.
Do we really need this feature? file nesting is usually handled by add-ins, it doesn't look like something users should be able to directly manipulate.
Bug 13875 may also be caused by this.