<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<title></title>
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
</head>
<body>
<p>Hi Remi,</p>
<p>On 2018-09-26 21:22, Rémi Denis-Courmont wrote:</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> Le keskiviikkona 26. syyskuuta 2018, 21.12.44 EEST Filip Roséen a écrit :</code></pre>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> If one would like to preparse all items, but skip those that take too
long (for reasons such as being read over a "slow" network
connection), the timeout would help with making such decision. It
would then continue to populate the playlist with entities that at
least finished their job within a "reasonable"* amount of time.
* whatever timeout value would be *reasonable* in this case.</code></pre>
</blockquote>
<pre><code> Again, Reasonable is no more than ZERO.
ALL items in the hierarchy should be inserted retaining the playlist lock.
Otherwise shuffle and what-not does not work properly. That or the playlist
code must be significantly reworked. That might actually be the way to go in
4.0, but that seems impractical in 3.0.</code></pre>
</blockquote>
<p>Ok, noted and appreciated.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> That is how things worked until 2.2.x inclusive.</code></pre>
</blockquote>
<pre><code> Didn't `2.2.x` suffer from the equivalent delay in preparsing (not
"showing up directly") if it started to dive into something which
looked local, but was actually remote (like a mounted network share)?</code></pre>
</blockquote>
<pre><code> And again, in 2.2, expand meant expand in-line/immediately. Now expand means
collapse until the preparser expands.</code></pre>
</blockquote>
<p>All the best,<br />
F</p>
</body>
</html>