Parallel running fucntions

Anatoly · 2017-10-01 10:37:08

Basically:

Like in ShiftBot, how to isolate blocks buildings from the commands, so once you build a map, you can still use commands.

LukeM · 2017-10-01 10:45:06

Use multiple threads and locks

I usually have a Queue<object[]> where object is the b messages being sent, and Place and BlockPlaceTick functions using locks to add and remove blocks from the queue
BlockPlaceTick is usually then called by a timer, and has a while(curTick < curTime) so it can place blocks faster than the max timer speed

Edit: Locks basically make it so two threads wait for each other to finish using data before they try to access it, as if they both used it at the same time, bad things could happen

Tomahawk · 2017-10-01 11:25:51

Or, if you're not worried about potential thread issues,

new Thread(() =>
{
    //send blocks

}).Start();

LukeM

Anatoly · 2017-10-01 11:39:52

What is more suggested? That Queue stuff or Threads?

SirJosh3917

LukeM · 2017-10-01 11:44:27

AnatolyEE wrote:

What is more suggested? That Queue stuff or Threads?

Depends what youre using it for, some things wouldnt cause any threading problems, so you could just use Tomahawks, but other things might need the locks and queues to prevent errors

Vinyl Melody · 2017-10-01 12:13:54

Screams Async in the background

BuzzerBee, Latif, Zumza

den3107 · 2017-10-01 12:55:52

I personally have my main thread (duh), a thread for my message handler (so I don't have to worry about delays in messages) and a thread for my block handler. All I then just do is call a function and the block handler will do the rest.

LukeM · 2017-10-01 13:06:06

Vinyl Melody wrote:

Screams Async in the background

It really depends what youre using it for, if it was a shift like world, you should probably use async as youd want to have a callback once it had finished placing, and wouldnt need mutliple things being placed at once, but if it was something where, for example commands could place structures, that wouldnt work very well, as you could have multiple placement loops at the same time, which would lead to an inconsistant placement speed, plus iirc async is for things that would need a callback, which it wouldnt

den3107 · 2017-10-01 22:29:31

destroyer123 wrote:

you should probably use async as youd want to have a callback once it had finished placing

I personally provide an optional "onComplete" Action parameter to my block handler. Just push in a method or an () => { anonymous.Method(); } and you got your callback.

LukeM · 2017-10-01 23:31:03

den3107 wrote:

destroyer123 wrote:
you should probably use async as youd want to have a callback once it had finished placing
I personally provide an optional "onComplete" Action parameter to my block handler. Just push in a method or an () => { anonymous.Method(); } and you got your callback.

You definately can do it that way, but IMO its neater to use async / await, as then all your code is all at one 'level', and is run from top to bottom

Official Everybody Edits Forums

#1 2017-10-01 10:37:08

Parallel running fucntions

#2 2017-10-01 10:45:06, last edited by LukeM (2017-10-01 10:46:49)

Re: Parallel running fucntions

#3 2017-10-01 11:25:51

Re: Parallel running fucntions

#4 2017-10-01 11:39:52

Re: Parallel running fucntions

#5 2017-10-01 11:44:27

Re: Parallel running fucntions

#6 2017-10-01 12:13:54

Re: Parallel running fucntions

#7 2017-10-01 12:55:52

Re: Parallel running fucntions

#8 2017-10-01 13:06:06, last edited by LukeM (2017-10-01 13:06:37)

Re: Parallel running fucntions

#9 2017-10-01 22:29:31

Re: Parallel running fucntions

#10 2017-10-01 23:31:03

Re: Parallel running fucntions

Board footer