Raised This Month: $ Target: $400
 0% 

Sharing the cellarray handler with two plugins.


Post New Thread Reply   
 
Thread Tools Display Modes
Author Message
11922911
Senior Member
Join Date: Dec 2011
Location: Yuen Long Country
Old 07-05-2014 , 02:51   Sharing the cellarray handler with two plugins.
Reply With Quote #1

Is it possible to sharing the cellarray handler with two different plugins?

For example:
Plugin A has created an cellarray handler, Plugin B wants to use the handler which Plugin A created, when Plugin B makes change to the handler (using ArraySet.., ArrayPush.., etc.) that also affect to the Plugin A.
__________________
youtube:
@holla16
11922911 is offline
Backstabnoob
BANNED
Join Date: Feb 2009
Location: Iwotadai Dorm
Old 07-05-2014 , 05:04   Re: Sharing the cellarray handler with two plugins.
Reply With Quote #2

Yes it is, you can simply return it as an integer via natives. See my database ORM, I do it all the time (all natives tagged with Array)
Backstabnoob is offline
Nextra
Veteran Member
Join Date: Apr 2008
Location: Germany
Old 07-05-2014 , 09:10   Re: Sharing the cellarray handler with two plugins.
Reply With Quote #3

Also this is possible with every handle. SQL Handles, Cellarrays, Tries, Cvars, Datapacks, HamHooks. It doesn't matter. The handle system in AMXX is very simplistic and does not restrict you in this way.
__________________
In Flames we trust!
Nextra is offline
klippy
AlliedModders Donor
Join Date: May 2013
Location: Serbia
Old 07-05-2014 , 11:20   Re: Sharing the cellarray handler with two plugins.
Reply With Quote #4

XVars may be really suitable here if he hasn't made an cellarray handler array, i.e:
PHP Code:
new Array: aArray[10]; 
klippy is offline
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 21:11.


Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
Theme made by Freecode