 |
chris-74269
Magician
Joined: 23 Nov 2004
Posts: 364
|
 Posted: Sun Jun 18, 2006 4:55 pm
priority in triggers
|
in the trigger options, what is up with the values in the priority window?
|
|
|
|
|
edb6377
Magician
Joined: 29 Nov 2005
Posts: 482
|
Posted: Sun Jun 18, 2006 8:10 pm
|
decides where in line it falls. although i admit the 2650 numbers etc are a bit confusing i guess it gives us lots of room :P
|
|
_________________
Confucious say "Bugs in Programs need Hammer" |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Jul 05, 2006 7:09 pm
|
It was done for performance reasons. As edb mentioned, it gives room for inserting/changing priorities. Currently, CMUD makes the priority 10 times the "index" number, which is the order in which settings are created. This gives room for inserting other items without having to renumber every setting.
Remember that CMUD is using a database. The priority is a field stored in the database for each trigger. If you dragged/dropped a trigger into a new priority order, then normally CMUD would need to update every database record after that to add one to all of the priorities. By leaving some space between priorities, it significantly reduces the number of database records that need to be updated when you change priority orders.
So yes, the large numbers might be a bit confusing to new people, but I think the big performance boost is worth it. |
|
|
|
|
|
|
|
