Bug 5445 - Files shown with "Show All Files" no longer are shown after multiple files included
Summary: Files shown with "Show All Files" no longer are shown after multiple files in...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Shell ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-31 20:38 UTC by Chuck Savage
Modified: 2016-10-19 13:08 UTC (History)
4 users (show)

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:

Description Chuck Savage 2012-05-31 20:38:09 UTC
1) Right click a folder that has multiple files that are not included in the project.  
2) Choose from the folder's context menu Display Options > Show All Files
3) Pick some (2 or more) of the non-included files and include them.

The other non-included files will no longer appear even though, if you look, the check for Show All Files is still checked for the folder.  You have to uncheck/re-check (or refresh) to display them again.

Choosing just one file to include has the expected behavior.
Comment 1 Saurabh 2015-11-03 07:37:17 UTC
I have checked this Issue with latest builds and not getting this Issue. This is the screencast for the same: http://www.screencast.com/t/ASMskGtGGkUo

=== Xamarin Studio ===

Version 5.10 (build 862)
Installation UUID: 2939b8b4-8977-42bd-82d6-100275ccd9cd
	Mono 4.2.1 (explicit/5a86dd3)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402010098

=== Xamarin.Profiler ===

Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 7.0 (8227)
Build 7A220

=== Xamarin.Mac ===

Version: (Enterprise Edition)

=== Xamarin.Android ===

Version: (Enterprise Edition)
Android SDK: /Users/360_macmini/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.3    (API level 10)
		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)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)

SDK Tools Version: 24.4
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.1

Java SDK: /usr
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)

=== Xamarin Android Player ===

Version: 0.3.4
Location: /Applications/Xamarin Android Player.app

=== Xamarin.iOS ===

Version: (Enterprise Edition)
Hash: de3c24f
Branch: master
Build date: 2015-10-16 19:13:32-0400

=== Build Information ===

Release ID: 510000862
Git revision: 0e2efcd3ac1b3ef308efcf30f8b79f067bbc1718
Build date: 2015-11-02 12:30:17-05
Xamarin addins: 324393d2c1dea5192ded0b45497691f404538e3d
Build lane: monodevelop-lion-cycle6

=== Operating System ===

Mac OS X 10.10.5
Darwin Hello.local 14.5.0 Darwin Kernel Version 14.5.0
    Wed Jul 29 02:26:53 PDT 2015
    root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64

@Chunk, Could you please check with latest build and let us know if you are still getting this behavior?
Comment 2 iain 2016-10-18 12:11:28 UTC
This seems to be fixed in recent versions
Comment 3 Saurabh 2016-10-19 13:08:54 UTC
As per comment#1 and comment#2, changing the status to verified