|
Huns Valen
Don't PM me here.
Join date: 3 May 2003
Posts: 2,749
|
11-10-2004 10:45
Keep llGetNextEmail(), of course, but let us have a way to automatically have the email() event raised when new mail comes in. It seems wasteful to have to poll for it constantly.
|
|
Evil Fool
"==" != "="
Join date: 30 Jul 2004
Posts: 110
|
11-10-2004 12:29
that would be nice, and also it would fix their problem with polling, which may have messed up some of my updating scripts, as well as thousands of other creations
|
|
Moleculor Satyr
Fireflies!
Join date: 5 Jan 2004
Posts: 2,650
|
11-10-2004 13:32
ONLY AS AN ALTERNATIVE OPTION, PLEASE!
Sometimes I LIKE the fact that I have to poll for my next email. Lets not break things more than they already are.
_____________________
</sarcasm>
|
|
Oz Spade
ReadsNoPostLongerThanHand
Join date: 23 Sep 2003
Posts: 2,708
|
11-14-2004 08:04
This would be nice, but I agree with Moleculor, this should be an option. Any suggestion on how to make it optionable?
Maybe llSetAutoEmailRetrieve(boolean)? Automaticly the script would be set to boolean = FALSE, in order to have it auto retrieve you'd have to set it to TRUE. I.e.:
state_entry()
{
llSetTimerEvent(1);
}
timer()
{
llGetNextEmail();
}
Would NOT auto get email, but:
state_entry()
{
llSetAutoEmailRetrieve(TRUE);
}
WOULD.
Removing that function would return the script to defualt/normal behavior.
_____________________
"Don't anticipate outcome," the man said. "Await the unfolding of events. Remain in the moment." - Konrad
|