[205] Goto Type shortcut not working in empty environment

The way I usually work is I open up a project and immediately hit ctrl-N
to surf to the right type to start working. Unfortunately, it seems that
ctrl-N no longer works unless you are already in an editor editing a
file? Not a big deal, but probably something that needs fixing.

No exceptions so far! :)

-Greg

3 comments
Comment actions Permalink

Hello Greg,

most likely this is a consequence of the new asynchronous processing introduced
in 214/215. The caches
that Ctrl-N uses to find the type have simply not been built yet just after
opening a project, you have
to wait for some time. Of course, there should be a visual indication of
how caches construction proceeds,
we'll add it in the nearest builds.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

The way I usually work is I open up a project and immediately hit
ctrl-N to surf to the right type to start working. Unfortunately, it
seems that ctrl-N no longer works unless you are already in an editor
editing a file? Not a big deal, but probably something that needs
fixing.

No exceptions so far! :)

-Greg



0
Comment actions Permalink

Hmm, I'm fairly certain this is not the case. I can be in an environment
an hour after I've started working, close all the open file editors, and
Ctrl-N fails to respond.

Dmitry Shaporenkov (JetBrains) wrote:

Hello Greg,

most likely this is a consequence of the new asynchronous processing
introduced in 214/215. The caches
that Ctrl-N uses to find the type have simply not been built yet just
after opening a project, you have
to wait for some time. Of course, there should be a visual indication of
how caches construction proceeds,
we'll add it in the nearest builds.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> The way I usually work is I open up a project and immediately hit
>> ctrl-N to surf to the right type to start working. Unfortunately, it
>> seems that ctrl-N no longer works unless you are already in an editor
>> editing a file? Not a big deal, but probably something that needs
>> fixing.
>>
>> No exceptions so far! :)
>>
>> -Greg
>>


0
Comment actions Permalink

http://www.intellij.net/tracker/resharper/viewSCR;JSESSIONID=48301038761138272845635?publicId=16120

"Greg Fodor" <greg@parature.com> wrote in message
news:dr8p98$egj$1@is.intellij.net...

Hmm, I'm fairly certain this is not the case. I can be in an environment
an hour after I've started working, close all the open file editors, and
Ctrl-N fails to respond.

>

Dmitry Shaporenkov (JetBrains) wrote:

>> Hello Greg,
>>
>> most likely this is a consequence of the new asynchronous processing
>> introduced in 214/215. The caches
>> that Ctrl-N uses to find the type have simply not been built yet just
>> after opening a project, you have
>> to wait for some time. Of course, there should be a visual indication of
>> how caches construction proceeds,
>> we'll add it in the nearest builds.
>>
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>
>>> The way I usually work is I open up a project and immediately hit
>>> ctrl-N to surf to the right type to start working. Unfortunately, it
>>> seems that ctrl-N no longer works unless you are already in an editor
>>> editing a file? Not a big deal, but probably something that needs
>>> fixing.
>>>
>>> No exceptions so far! :)
>>>
>>> -Greg
>>>
>>

0

Please sign in to leave a comment.