question of the source code Ineisis

Babulesnik · 10-27-2011 08:54 PM

Why are using Time.wait(1) in Server->main.es

Code:

bool Update()

{

   if(Kb.bp(KB_ESC))return false;

   Gui.update();

   Server.update();

   Time.wait(1);

   return true;

}

Babulesnik · 11-19-2011 01:37 PM

In the future there will be more comments in the source code Ineisis? I find it hard to learn it. I have to parse each line.It would be nice to see documentation that shows the detailed structure / architecture Ineisis.Also causes inconvenience to use "Code Editor". I really like working in VisualStudio.Will the project is created by VS?

**Esenthel** · 11-19-2011 01:39 PM

I can add "adding more code comments" to roadmap

Babulesnik · 11-19-2011 01:41 PM

(11-19-2011 01:39 PM)Esenthel Wrote: I can add "adding more code comments" to roadmap

Thank you very much

Babulesnik · 11-21-2011 08:22 PM

The class is only one angle, the axis of y. But I have a tank will go to the mountains and heel. I just need add to classes two interpolator for x and y axes ?

Code:

class Neighbor : BlendObject

{ 

  ...

   Interpolator3S   pos;

   InterpolatorA    angle_x;

   InterpolatorA    angle_y;

   InterpolatorA    angle_z;

}

**Esenthel** · 11-22-2011 12:11 AM

yes

Babulesnik · 11-23-2011 12:31 PM

Why when receiving data, are using the cycle REP and why 16 ?

Code:

REP(16)if(!Server.receive(0))

**Esenthel** · 11-26-2011 11:13 PM

to process 16 commands at once
you can use different number

Babulesnik · 11-27-2011 02:07 PM

Why in the container before the action is used "lockedData(i)"

Code:

NeighborClients.lockedData(i)

In the class of "Map" I have not found a detailed explanation

Code:

// access i-th   element data from container, this   can  be used   after locking and before unlocking the container

- but what do "lock" and "unlock" container ?

For a list of players I'm using container "memx" .Can there be problems with using this container for such purposes ??? Or to have to create a list of players using the Map???For example:Map<SockAddr, Player> ListPayers

**Esenthel** · 12-01-2011 12:11 PM

you're free to use any container you wish, each has different advantages
lock, unlock is to avoid mult-threading issue, you can ignore this since all player operations should be done on 1 main thread only

Babulesnik · 12-02-2011 06:46 PM

(12-01-2011 12:11 PM)Esenthel Wrote: you're free to use any container you wish, each has different advantages
lock, unlock is to avoid mult-threading issue, you can ignore this since all player operations should be done on 1 main thread only

thanks,but if I use a dedicated server i-series(i3,5,7) processors should I have to use the "lock/unlock"? What could be the problem if I ignore it?

Babulesnik · 12-03-2011 10:42 AM

(12-02-2011 08:07 PM)aceio76 Wrote:
(12-02-2011 06:46 PM)Babulesnik Wrote:
(12-01-2011 12:11 PM)Esenthel Wrote: you're free to use any container you wish, each has different advantages
lock, unlock is to avoid mult-threading issue, you can ignore this since all player operations should be done on 1 main thread only
thanks,but if I use a dedicated server i-series(i3,5,7) processors should I have to use the "lock/unlock"? What could be the problem if I ignore it?

Those aren't related with each other. The lock/unlock is strictly for multi-threading, to prevent non-thread safe access to shared data. Containers pertain to Memc, Memx, Meml, etc. To understand potential problems with not using the locks, you will need to understand how multi-threading works.

Thank you very much

question of the source code Ineisis
Author	Message