A single keystroke in the editor panel may trigger up to 5. (But that's 95% because Sublime Text-my other most-used app-behaves so badly when the system is under heavy load that I have no option but to limit programs like ffmpeg or HandBrake to ~600% CPU. The Markdown preview needs a lot of resources to keep rendering on-the-fly after each keystroke. I'd also like to emphasise that it's not actually an issue for me. Typing lag is definitely more of an issue in Alfred than most other apps I use. I'm not sure Alfred is any slower to activate than any other application, however. What always catches me out is Alfred's window not appearing quickly enough after I hit its hotkey, so I end up typing in the wrong application. Most of my workflows do this, and the workflow library I wrote is designed around the idea of showing the old data till you've grabbed the new data. It's very common for slow-running workflows to deliberately show you old data until they've had time to update in the background. That's already a common situation with Alfred, most noticeably for workflows that take a good fraction of a second to run. I'm guessing the biggest issue would be that you could then have "out of date" results for your onscreen text. I don't know if this would create more problems, but what about a scenario where text input refresh is somehow disconnected from the search results? i'm totally cool with waiting a bit longer for results if i'm doing heavy lifting elsewhere, it just hurts my brain a bit when i type and there's a momentary delay before the characters appear on screen! *Pets MacBook above screen, don't worry, this won't last long.* I'm going to raise an internal ticket to see if there is something I can do to improve this situation. Having said that, I suspect that the lag will have something to do with OS X's metadata querying which is allegedly asynchronous, but I've definitely seen the setup calls being held / blocked which adversely affects Alfred. This is something I could likely improve but it would have compromises such as going in the opposite direction and allowing a processor intensive workflow to slow your Mac down.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |