.Net Bug with threads ?

I finally managed to reproduce this bug that gave me much trouble !

It seems it only appears using threads, that's why this script might seem mad (I have MMF launch a Main function which launches a new thread which launches another one regularly). The problem happens when I try to retrieve a parameter from an immediate condition : from times to times, it doesn't return the specified param.

Launch the app, press space and watch the result, most of the lines are correctly written ("Condition Parameter : my parameter"), others might show the bug("à§îCondition Parameter : my parameter" or such). If this doesn't show up the first time, press space again, it happens from time to time.

Is there a way to prevent this from happening (I really need multi-threading) ? Is it because of .Net extension, or should I use Mutex or something ?

Thanks for the help, and fast answer.

I wasn't able to fix the problem, but i've never used locks before, maybe I did something wrong. Should this be ok ?

Quote

string[] param=new string[1]{"my parameter"};
lock (param){
MMFInterface.Conditions.CallImmediateCondition("Condition",param);
}

It doesn't seem to work.

I never had a crash here...

Using the list object makes things better, but it's not perfect yet, sometimes a line is not added (this only happened to me once, with more than 4000 immediate conditions, so this might be hard to reproduce).

Do you still think this issue could be fixed in a future version ?

I hope this gets fixed some way, I'd love to see a C# multithreaded server available for MMF, and it will need to be reliable.

For now I'll stick to the List object to retrieve my parameters. By the way, it would be handy to have a "Last triggered ImmediateCondition Name" expression : this way you could create a "ParamParser" Loop which could retrieve the parameters of any ImmediateCondition (I know it's easy to have a string keep this information, but it would be easier).

After working a bit on this problem, i found a workaround :

The problem is that you can only use CallImmediateCondition() from MMF thread, so I stored every event that should trigger such a callback in a container, and asked MMF to Always CallFunction("TriggerConditions",""). This way, all the ImmediateConditions will be called from inside MMF thread. Here is a simple example :

static class Global {


   //ATTRIBUTES
   private static Mutex MutexMMF=new Mutex();
   private static ArrayList Conditions=new ArrayList();


public static void AddCondition(string nom, string[] param) {
   MutexMMF.WaitOne();
   Conditions.Add(new MMFCondition(nom, param));
   MutexMMF.ReleaseMutex();
}//Adds a MMFCondition inside Conditions


public static void TriggerConditions() {
   MutexMMF.WaitOne();
   foreach(MMFCondition c in Conditions) {
      MMFInterface.Conditions.CallImmediateCondition(c.nom, c.param);
      //Console.WriteLine(c.nom+" : "+c.param[0]+"||"+c.param[1]);
   }
   Conditions.Clear();
   MutexMMF.ReleaseMutex();
   }//Triggers all the MMFImmediateConditions Stored in Conditions


}


class MMFCondition {
   //attributes
   private string _nom;
   private string[] _param;


   //properties
   public string nom {
      get { return _nom; }
   }//public, read only
   public string[] param {
      get { return _param; }
   }//public, read only


   //constructor
   public MMFCondition(string nom, string[] param) {
      _param=new string[param.Length];
      _nom=nom;
      param.CopyTo(_param, 0);
   }


}//Our condition class to trigger an MMFInterface.CallImmediateCondition

This seems to work perfectly here, without any list object to retrieve the params