[Depresie]

In the next example function_1 will always return true, shouldn't be more logical to return false since the task already triggered the function and has no reason to exist anymore?

PHP Code:


#define TASK_1      5000

public plugin_init()
{
      set_task(30.0, "function_1", TASK_1)
}

public function_1(taskid)
{
      if(task_exists(TASK_1))
      {
          return true 
      }
      return false
} 


[klippy]

It probably gets destroyed once function_1 returns.
Is there anything wrong with that? Do you really need it to be destroyed before function_1 gets called? What are you exactly trying to do? If you provide a good enough reason for it to be changed then it may as well change.

[EFFx]

KliPPy is right, the task is destroyed after the function's return.

[Depresie]

Well, it would be more logical to be destroyed before the function returns, because from the moment the function is triggered, the respective task does not exist anymore..

One reason in particular for me, is the following case where i have a function with multiple triggers, but don't want it to be executed if there is a task set to execute it

Of course there are workarounds, there always are, but to me, it just doesn't make sense that a task which doesn't exists anymore, to be said that it still exists..

PHP Code:


#define TASK_WAITING_PLAYERS 2000
public plugin_init()
{
       set_task(45.0, "function_check_players", TASK_WAITING_PLAYERS)
}

public client_disconnect()
{
     function_check_players()
}

public client_team_changed()
{
     function_check_players()
}

public client_killed()
{ 
     function_check_players()
}

public function_check_players()
{
    if(task_exists(TASK_WAITING_PLAYERS))
         return
   
    // execute some fancy code
} 


[fysiks]

Originally Posted by Depresie Well, it would be more logical to be destroyed before the function returns, because from the moment the function is triggered, the respective task does not exist anymore..

The task exists until the task is completed. The "task" is defined as running the function (which implies completion). So, the task exists until it has completed what you told it to do which is running the function to completion.

What you are wanting is something more like "trigger function". However, in your case there are probably better ways to do it. Simply use a global variable to control the functionality of the function:

PHP Code:

public DoStuff()
{
    if( g_bAllowed )
    {
        // Main functionality here
    }
}

public TaskToDoStuff()
{
    g_bAllowed = True
    DoStuff()
} 


[klippy]

Originally Posted by fysiks The task exists until the task is completed. The "task" is defined as running the function (which implies completion). So, the task exists until it has completed what you told it to do which is running the function to completion.

I totally agree with this. I'm sure that in most languages that have a library managing timers/delays/tasks contained by an object you would find the same behavior.

[Depresie]

The task exists until the task is completed. The "task" is defined as running the function (which implies completion). So, the task exists until it has completed what you told it to do which is running the function to completion.

Makes sense, but would be welcome to have it work both ways controlled by a param, but that's up to the devs to decide if it would be worth

[klippy]

Just use Fysiks's code or something similar to it. It's a problem solvable with a few lines of code, it rarely matters and would add unnecessary complexity by adding another param.

[fysiks]

Originally Posted by Depresie Makes sense, but would be welcome to have it work both ways controlled by a param, but that's up to the devs to decide if it would be worth

Adding such a thing is completely unnecessary since the proper alternative is trivial.