-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance QuickEdit performance #12874
Comments
Yes, we'd like to improve the performance of Quick Edit searches. Be sure to read the Large Projects in Brackets wiki page. |
|
One other question -- is it only slow the first time you invoke Quick Edit, or is it equally slow every time? |
I guess Brackets not caching search results or parsed files, so it's slow for every time. I just ended up using Quick Edit directly in my project folder. I'll try the work around that |
I made the same observations and it's equally slow every time. |
I am recently experiencing delay when using quick edit and also when switching between files. At times the delay is greater than 1.5 seconds rendering the application super slow and almost unusable. I've not noticed this delay in previous versions (<0.44) of brackets - which have performed perfectly when editing even larger projects. This project I have open consists of 119 files - total of ~3MB. Switching between files in "working files" pane or by using ctrl + tab is equally as slow. Brackets Build: 0.44.0-14876 |
I have same issue here. It's quite annoying because the quick edit is too slow. I tried "Reload Without Extensions" and it doesn't help at all. Any ideas to fix it? |
|
Monday Oct 13, 2014 at 15:36 GMT
Originally opened as adobe/brackets#9541
Hi,
When using Quick Edit in a large project which including many css files, it's taking a lot of time to show the related css. I haven't looked into the implement of this feature so I can't say more. However, IMO a cache file, or if we can add one file to declare which files/folders to be searched when editing should provide a huge improvement (just something like .git_ignore, or bowerrc.json etc).
Does anyone have the same problem, and any suggestion how to setup a large project to improve performance of this feature?
Thanks.
The text was updated successfully, but these errors were encountered: