|
Mark Busch
DarkLife Developer
Join date: 8 Apr 2003
Posts: 442
|
11-05-2004 06:34
Hey for bigger script project I notice how slow scripting is  it's difficult to actually give suggestions on how to do this because I don't know the server-side code... but one thing I was thinking about was how much events are triggered in my scripts that should nog have to be triggered... so solution would be sending link_messages to certain scripts only (not too all), so that script that won't use the link message don't run the event
|
|
Hank Ramos
Lifetime Scripter
Join date: 15 Nov 2003
Posts: 2,328
|
11-05-2004 06:39
From: Mark Busch Hey for bigger script project I notice how slow scripting is  it's difficult to actually give suggestions on how to do this because I don't know the server-side code... but one thing I was thinking about was how much events are triggered in my scripts that should nog have to be triggered... so solution would be sending link_messages to certain scripts only (not too all), so that script that won't use the link message don't run the event Using the Link Number or the LINK_ALL_OTHERS, LINK_ALL_CHILDREN, etc helps a lot with large multi-prim objects.
|
|
Mark Busch
DarkLife Developer
Join date: 8 Apr 2003
Posts: 442
|
11-05-2004 06:54
yeah good idea, but I have 20 scripts on 1 object...
|
|
Mark Busch
DarkLife Developer
Join date: 8 Apr 2003
Posts: 442
|
11-05-2004 07:02
hmm maybe altering the functioncall llMessageLinked is not a good idea. but what about making the link_message event the same as listen? so you can specify which link messages should generate an event for this script and which not?
|
|
Apotheus Silverman
I write code.
Join date: 17 Nov 2003
Posts: 416
|
11-05-2004 09:19
From: Mark Busch yeah good idea, but I have 20 scripts on 1 object... The best way I have found to handle this is to use a standardized tagging system for linkmessages. Use the key or int field as your tag, then each script can process messages or not depending on that. The systems I've created use tagging to define the purpose of a message but it should be no more difficult for tags to define which script the message is meant for.
|
|
Carnildo Greenacre
Flight Engineer
Join date: 15 Nov 2003
Posts: 1,044
|
11-05-2004 22:50
My link message system uses the "int" field for message IDs, and the "string" and "key" fields for message data. Ints are fairly quick to process, and small enough that I can usually use defined "constants" to make the meaning of each numeric value clear.
_____________________
perl -le '$_ = 1; (1 x $_) !~ /^(11+)\1+$/ && print while $_++;'
|
|
Mark Busch
DarkLife Developer
Join date: 8 Apr 2003
Posts: 442
|
11-06-2004 13:21
yes my scripts also use the number for identifying the message.. but still you have to check for it with LSL... which is much slower then if it were checked before any LSL was excuted.. that's why I say yes to a mixture of link_messages and listen-function that you can use to tell which link-messages will and which will not be executed for a script.
|