Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.43 Safari/530.5 Build Identifier: 20090621-0832 Ctrl + F6 & Ctrl + E seem to perform similar functionality. It would be useful if we could access the Recently Accessed Files (Even if they have been closed) so that User need not use the project explorer every time using Ctrl + E. Similarly, Jump to caller Option should be provided where this option lists down the method callers allowing Users to select. Jump to Caller Options is available is Source Insight 3.5. which is very much userful. Reproducible: Always Steps to Reproduce: 1. Just open a file & Close it. 2. No shortcut for re-opening the recently opened file. 3. Similarly, Jump to Caller option not available.
Alt+F, 1-9 does that help?
Dear Prakash, Thanks for the udpate. Alt-F 1-9 is limited to very few files. It would be very useful if we could have a recent list window for many files as in VC++ or Source Insight 3.5. I've enclosed both the VC++ & Source Insight images for your kind reference. Once the window List emerges, Users can keen in the few letters as in Ctrl + E of Eclipse to select the files. Moreover, Source Insight provides one additional feature where if there are multiple files of the same name in different projects . For Ex- AndroidManfiest.xml in Android project1 & project2 then, User can choose selection by AndroidManifest.xml(project2) to select the files.
Created attachment 146259 [details] Initial Windows List in Source Insight
Created attachment 146260 [details] Alternative Option to view all the recently viewed files in Source Insight
Created attachment 146261 [details] Windows List in VC++
Perhaps an enhancement to Quick Access
Remy is now responsible for watching the [EditorMgmt] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
