[aRoach]

Description

• This is a little include that uses OnPlayerDialogResponse( ) to process players Dialogs.
  Each dialog has his own function like the Command Processors( ZCMD, DCMD, YCMD ), such method is much faster than the normal way.

Usage

• All you need to do is to add a public function using special pre-defined macros, like this:
  
  pawn Код:

  DIALOG:1( playerid, response, listitem, inputtext[ ] )
  {
      // Your code here, like in the Normal Dialogs with 'if else if else if else'
  
      return ( 1 ); // My style, it's not obligatory to use returns like that
  }

  or( another macro ):
  
  
  pawn Код:

  DLG:1( playerid, response, listitem, inputtext[ ] )
  {
      // Your code here, like in the Normal Dialogs with 'if else if else if else'
  
      return ( 1 );
  }

Here is all like the normal dialogs, but much faster.
That's all! Very easy, isn't it?

How to make two different dialogs doing the same thing( like in ZCMD )

• For example, you have the dialog '123' :
  
  pawn Код:

  DIALOG:123( playerid, response, listitem, inputtext[ ] )
  {
      // Your stuff here...
      return ( 1 );
  }

  And you want to create another one that does the same thing:
  
  pawn Код:

  DIALOG:456( playerid, response, listitem, inputtext[ ] )
  {
      return dlg_123( playerid, response, listitem, inputtext );
  }

Notes

• If you want to check whether inputtext string is empty( like in ZCMD with parameters ) you should not do it like:
  
  pawn Код:

  if( !strlen( inputtext ) )
  {
      // ...
  }

  or:
  
  pawn Код:

  if( !inputtext[ 0 ] )
  {
      // ...
  }

  Just use isnull( ), because its length will never be NULL:
  
  pawn Код:

  if( isnull( inputtext ) )
  {
      // ...
  }

  Actually, if you use sscanf[1] you don't need to do this as it has built-in isnull checking.

Speed Test

• I did the test between mine and FDLG( because I think is the faster ) and here's the Result:
  
  Код:

  Time taken to show 32766 RDLG dialogs: 3 ms, average call time: 3/32766 ms.
  Time taken to execute 100,000,000 RDLG OnDialogResponse calls: 8805 ms.
  
  Time taken to show 32766 FDLG dialogs: 4 ms, average call time: 4/32766 ms.
  Time taken to execute 100,000,000 FDLG OnDialogResponse calls: 8818 ms.

  Both are almost the same at timing!

Requirements

• You'll need y_hooks( OPTIONAL ).

Downloads

• SolidFiles
• Pastebin

Special thanks to

• ****** - For some Tips.
• stuntman - For some Tips.
• Gamer_Z - His Speed Test Filterscript.