| commit | c134baf64aea3b7b4484a6350615f0607be176a1 | |
| author | Michael Keppler <Michael.Keppler@gmx.de> | |
| Thu, 5 Apr 2018 08:49:49 +0000 (5 10:49 +0200) | ||
| committer | Thomas Wolf <thomas.wolf@paranor.ch> | |
| Wed, 25 Apr 2018 10:17:38 +0000 (25 06:17 -0400) | ||
| tree | d1bf63bd9689806c9e7d739ca207eb12b16ee928 | treesnapshot (tar.gz zip) |
| parent | 455a6c3648c9dbc04fe7c82b2bb8d3ef91797825 | commitdiff |
Repositories view blocks Eclipse on startup
When asking the "Tags" node whether it has children or not, answer true,
as long as the ref database has not been read, and start reading the
database in a job.
This avoids blocking the Eclipse UI for reading the ref database very
early when creating the nodes in the repository tree view. Of course the
blocking still happens if the user tries to expand the tags node
immediately after that node became visible.
Change-Id: I553db27d2bdd2571c6a713dabd6e68065873b98b
Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de>
Bug: 533230
When asking the "Tags" node whether it has children or not, answer true,
as long as the ref database has not been read, and start reading the
database in a job.
This avoids blocking the Eclipse UI for reading the ref database very
early when creating the nodes in the repository tree view. Of course the
blocking still happens if the user tries to expand the tags node
immediately after that node became visible.
Change-Id: I553db27d2bdd2571c6a713dabd6e68065873b98b
Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de>
Bug: 533230