From: Maxwell, A. R <ada...@pn...> - 2005-07-13 16:50:57
|
On Jul 13, 2005, at 09:41, Alex Montgomery wrote: > > On Jul 13, 2005, at 12:29 PM, Maxwell, Adam R wrote: > > >> >> On Jul 13, 2005, at 09:10, Alex Montgomery wrote: >> >> >> >>> >>> On Jul 13, 2005, at 11:27 AM, Maxwell, Adam R wrote: >>> >>> In 1.1.2, it's only updated once you switch to another field, >>> cutting CPU usage. >>> >>> >> >> This is not correct. It is updated as you type in 1.1.2, but it >> should be much faster than in previous versions; unfortunately, I >> just noticed that this causes problems with undo. >> > > Hmm, really? The table looks the same as I'm editing a field, and > only changes once I hit tab... This is correct if you're editing a "regular" field in the editor. The OP mentioned the abstract field, though, which is in a separate tab of the editor (as is annote); those are updated as you type. > >>> As an aside, I might mention that I get high CPU usage in the >>> table view when switching between entries (say, if I hold down >>> the down key), probably due to the constant updating of annote >>> pane, even if it's mostly hidden. >>> >> >> Do you have TeX previewing enabled? This is the biggest CPU hog; >> displaying the preview pane has negligible overhead in most >> cases. Also, what are you displaying in the preview pane? Annote >> only? >> > > Nope, the TeX preview is off. Annote only. Do you get a beachball? Please try this: in Terminal, `sample BibDesk 10`, hit return, and then start switching entries as you mention above. When sample finishes, send me the output file (in Terminal, `open /tmp`, then grab the file). Adam |