Code Explorer not opening any object

[LukeHSC]

WHen I have CodeExplorer running and refreshed, it does not open any object (Form, Module, Class). I am double clicking on the parent in the tree and also the daugthers, nothing ... :

am I missing something ? I am wanting to use this as a replacement to Project Explorer.
Using MSAccess v2010

[retailcoder]

Definitely not what's supposed to happen. Does navigation work off the search results toolwindow (e.g. "find all references" results), and/or off the inspection results toolwindow?

[retailcoder]

Do you have logging enabled? If not, enable it at TRACE level, it's possible a COM exception is being thrown/swallowed. Having a stack trace might help diagnose.

[retailcoder]

The Pending parser state button should be saying Ready ...something isn't right, I'd definitely be curious to see the logs. Does it work if you click the refresh button that says Pending in the Rubberduck commandbar and then try double-clicking again?

[LukeHSC]

I forced a ‘refresh’ on the Code Explorer twice, now it works ….hmmm… I have turned on the logging to TRACE and if happens again will let you know. One request – I did have the project password locked but I turned it off and then closed MSAccess and restarted; did not help with the issue, but it would be good if RD could prompt for a password just like the MSFT Project does when you try to open an object From: Mathieu Guindon <notifications@github.com> Sent: Thursday, 24 May 2018 2:19 PM To: rubberduck-vba/Rubberduck <Rubberduck@noreply.github.com> Cc: LukeHSC <luke@hsconsultants.net.au>; Author <author@noreply.github.com> Subject: Re: [rubberduck-vba/Rubberduck] Code Explorer not opening any object (#4034) Definitely not what's supposed to happen. Does navigation work off the search results toolwindow (e.g. "find all references" results), and/or off the inspection results toolwindow? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4034 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AlvmwGdt_EEZREbC49F3wOi2WH_eg7yGks5t1jTNgaJpZM4ULibt> . <https://github.com/notifications/beacon/AlvmwJYNJwBW9-jN6k1k1uj4oefxY0SMks5t1jTNgaJpZM4ULibt.gif>

[LukeHSC]

on the Code Explorer issue – when I very first opened it yesterday on a medium sized project it said “Doesn’t see anything yet, refresh”, which I did. That took several mins but then worked ok-ish (per problems noted yesterday eventually worked) I closed up work last night and opened the project again and when RD fires up it says again “Doesn’t see anything yet, refresh” ? I did so and again takes a few mins (~2.5) to refresh - that will be a bit of a pain as I open and close the project (or others) a few times a day to do backups. That said, I see it sort of does it in background but it does slow my VBA response down. Does RD not keep a last-know good list? if not can that be added somehow? Regards, Luke From: Mathieu Guindon <notifications@github.com> Sent: Thursday, 24 May 2018 2:21 PM To: rubberduck-vba/Rubberduck <Rubberduck@noreply.github.com> Cc: LukeHSC <luke@hsconsultants.net.au>; Author <author@noreply.github.com> Subject: Re: [rubberduck-vba/Rubberduck] Code Explorer not opening any object (#4034) Do you have logging enabled? If not, enable it at TRACE level, it's possible a COM exception is being thrown/swallowed. Having a stack trace might help diagnose. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4034 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AlvmwHbCzhgRDEZMav5Mu8uOUok1TWKfks5t1jUZgaJpZM4ULibt> . <https://github.com/notifications/beacon/AlvmwOY9RcfSo-ZYGx_fRFoKkb7DvZYSks5t1jUZgaJpZM4ULibt.gif>

[retailcoder]

Reading the serialized declarations from disk would be even slower, unfortunately. We do have extensive caching going on, and strive to only process what needs to be processed, but once the host process triggers a shut-down of the add-in, all the cached knowledge is freed, and you get back your RAM.

"Inside Rubberduck, pt.2" explains everything there is to know about how parsing & resolving works, if you're curious about what's taking so long 😉

[comintern]

Closing this as stale, as it appears to revolve around the code that was re-written in #4661

If this persists in the current build, this can be re-opened.