QP suggestion: GetIt cache

[Lars Fosdal 1734]

https://quality.embarcadero.com/browse/RSP-26999

 

 

 

 

1

Quote

When you open GetIt, there is a long wait with a frozen UI before you can look at the list. Not only does this happen initially, but also every time you change the filter. 

GetIt should store the component list in a local cache, f.x. as Json or XML, which can be used to bring up the GetIt UI immediately. The cache can be updated by a non-UI blocking background thread, preferably just after you start the IDE, or by selecting a Refresh request from the UI. Filtering should be done locally in the UI. We are not talking about thousands of components here, so the impact of local filtering would be minuscule.

Follow link and vote if interested.

[Vandrovnik 202]

Voted and commented 🙂

[Fr0sT.Brutal 897]

Freezing UI in a software that costs ~$1k *facepalm*