author | Shawn O. Pearce <spearce@spearce.org> | |
Sat, 18 Nov 2006 08:31:25 +0000 (03:31 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Sat, 18 Nov 2006 08:31:25 +0000 (03:31 -0500) | ||
commit | 53716a7bc94497cd6d2dfd53b1e4f7669d677b01 | |
tree | 548b34232b97c6981f06fa91d55ec449761d2721 | tree | snapshot |
parent | a49c67d1ff9861d80bae57642d891016ea5debd5 | commit | diff |
git-gui: Start UI with the index locked.
Because we immediately start a rescan operation, but do so slightly
delayed (by 1 ms, to let the UI show before we start forking off
git processes), we can't let the user try to activate any of the
restricted GUI commands before the 1 ms timer expires and we kick
off the rescan.
So now we lock the index before we enter the Tk event loop, ensuring
that it is impossible for the user to inject a conflicting UI event
before our rescan can begin.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Because we immediately start a rescan operation, but do so slightly
delayed (by 1 ms, to let the UI show before we start forking off
git processes), we can't let the user try to activate any of the
restricted GUI commands before the 1 ms timer expires and we kick
off the rescan.
So now we lock the index before we enter the Tk event loop, ensuring
that it is impossible for the user to inject a conflicting UI event
before our rescan can begin.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
git-gui | diff | blob | history |