<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/28/2014 01:38 PM, David Haslam
wrote:<br>
</div>
<blockquote cite="mid:1414517924556-4654229.post@n4.nabble.com"
type="cite">
<pre wrap="">Obviously I had already refreshed the beta repo in order to get to that stage.</pre>
</blockquote>
<font face="FreeSerif">Well, OK,...you didn't say at what stage you
were, when you couldn't find it. I thought you meant you couldn't
find it in the set of modules offered in the repo. And there was
an old Lithuanian module in the repo already, so it would have
been seen pre-refresh.<br>
<br>
The probable explanation: Xiphos' mod.mgr runs asynchronously
(non-modally) with respect to the rest of Xiphos, so you can keep
working in the main window while the mod.mgr downloads or indexes
piles of stuff, things that may take a long time. As the mod.mgr
is closed, it re-runs the module discovery process for the rest of
the program, and if you tried <i>right at that interval</i>
between closing mod.mgr and opening the sidebar tree to find a new
module, it wouldn't appear, because the last vestige of the
mod.mgr is still busy re-discovering modules and the sidebar tree
hasn't been refilled.<br>
<br>
Technically, it's a race condition. In practice, it's so seldom a
problem that nobody has ever cared, since the mod.mgr was changed
from being modal to async in Mar'09 (-r2841).</font><br>
</body>
</html>