Bug:ISXVG.ConnectionState

[rootkit]

Im using ISXVG.ConnectionState as abort condition in my threads. If thread A is using some ISXVGAPi members and thread B is calling ISXVG.ConnectionState, the result of ConnectionState is "NPC".

So if this is

Data.FrameHandler.Framelock();                  
                   
if ( ext.ISXVG().ConnectionState != "IN_GAME")
{
      Tools.Log(ext.ISXVG().ConnectionState);
      inThread = false;
}
Data.FrameHandler.FrameUnlock();

my ConnectionState-Check, the first call(in the if statement) to ConnectionState gives back "NPC" the second one "IN_GAME".

 

[Amadeus]

I just made a change in build 20070328.0059.

Let me know if this fixes this particular problem. If it does, it means there are a lot of other similar things I need to adjust. There are things that work very well with lavishscript that do not work as well with .NET...unfortunately.

 

[rootkit]

works now

I use this post for some more feature requests:

-make ISXVG thread safe
-change Extension into static class if possible
-a new Event on_PawnEnteredRadar(Int64 pawnid), always triggers when an already spawned pawn enters the 'visible' range of the vgclient