beenull/SparkleShare
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

fix startup threading issue when Repositories is not null

Browse source
This commit is contained in:
wimh 2011-10-02 03:15:11 +02:00
parent 86c84e4120
commit dbc0fddf10
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
SparkleShare/SparkleControllerBase.cs
View file

@ -36,7 +36,7 @@ namespace SparkleShare {
public abstract class SparkleControllerBase {
public List <SparkleRepoBase> Repositories;
public List<SparkleRepoBase> Repositories = new List<SparkleRepoBase> ();
public string FolderSize;
public readonly string SparklePath = SparkleConfig.DefaultConfig.FoldersPath;
@ -155,6 +155,9 @@ namespace SparkleShare {
}
};
// FIXME: this should probably not called in a thread, because
// Repositories will not be valid until PopulateRepositories
// has been finished, but other functions use Repositories
new Thread (new ThreadStart (PopulateRepositories)).Start ();
}
@ -643,7 +646,7 @@ namespace SparkleShare {
// folders in the SparkleShare folder
private void PopulateRepositories ()
{
Repositories = new List<SparkleRepoBase> ();
List<SparkleRepoBase> TempRepositories = new List<SparkleRepoBase> ();
foreach (string folder_name in SparkleConfig.DefaultConfig.Folders) {
string folder_path = new SparkleFolder (folder_name).FullPath;
@ -654,6 +657,8 @@ namespace SparkleShare {
SparkleConfig.DefaultConfig.RemoveFolder (folder_name);
}
Repositories = TempRepositories;
if (FolderListChanged != null)
FolderListChanged ();