Community
Participate
Working Groups
Build Workbench 040226. Content Assist on windows.h takes 16 seconds Steps: 1) Load attach project 2) Open ManyFunctions_3.cpp 3) In the last function, type DOU<ctrl-SPACE> Takes 16 seconds for Content Assist to come up. By the way the content was wrong as well.
Created attachment 8303 [details] project
Hoda, please add in the appropriate time-out. We shall look into providing you an asynchronous interface so you can get partial results in lookup().
Mathieu, James, Please re-try this with today's version (March 9th,2004) Dave has just submitted a fix for the scanner and he claims that now windows.h takes only 3 seconds :-)
Fixed in HEAD, mar. 24th, 2004 A preference has been added to the content assist page for timeout, default = 3 sec. As we can not control the size of projects and the parsing time no matter what we do, we have to provide a means by which the user is capable of cancelling content assist and returning back to editing. The user should be advised to set the timeout limit proportional to the mean size of the projects he normally works on (in the documentation, help, and/or FAQ).
We will need to document this very clearly in the online help and maybe the FAQ (Is this a good question to add, DavidD?) The problem is that a user would still want to have the content of the Windows.h even if it times out. The user would have a hard time in finding the Time out threshold preference because it is buried in the preferences dialog. Can we make this more usable. Opinions?
Update: With the timeout set at 3 seconds, Content assist times out on the first try but does not timeout on the second try. Reopening.
Mathiew Is this re-opened for documentation? or for a required better performance?
*** This bug has been marked as a duplicate of 59468 ***
I accept the duplicate. It was for performance.
