Scratch

Maybe it runs 1 more block before it closes like the slide animation on GitHub

grr 60 seconds rule

roijac wrote:

you can workaround it

exactly what i was thinking 
Come 2.0, you could make it so that if a person is connected, then they keep sending packets, it guess you could call them?  Then, if the packets are not being sent, then they are removed from the list.  I'd have to take some time to think of the actual code, though, because there is no server side scripting

EDIT: just came up with some experimental code:

when gf clicked
forever
if <<(☁ refresh) = [1] > and <not<[☁online v] contains (user id)>>>
add (user id) to [☁online v]//a cloud list
end
when I receive [send_packets v]
set [☁refresh v] to [0]
delete (all v) of [☁online v]
set [☁refresh v] to [1]
wait (☁refresh rate) secs //should be determined server side
broadcast [send_packets v]

The cloud list "online" would contain a list of all user id's logged on
Once a user closes scratch, it will stop sending these "packets", and it will be detected by all the other clients acting for the server
And if no one else is on, then, once someone logs on, it will be detected

also, simply broadcast send_packets to start it
I'll soon update this to include a way to switch it off, which is actually simple

Note that this wouldn't work if, for example, you wanted to show a shutdown program if a window is closed.  That would be rather hard to do, and some browsers might block it

Last edited by SJRCS_011 (2012-11-14 22:04:43)