RBXScriptSignal:Wait() should be changed to include an argument

[buildthomas]

Use the search feature to search for similar threads:

Timeout argument for Event:Wait()

So there’s this issue I’ve ran into a few times by now; I regularly write code which waits for a ‘response’. Often times the response is given by my framework’s font- or back-end so a response it pretty much always guaranteed to be given. Sometimes however the response is given by a player. Players can be really unexpected sometimes and might not give a response at all which could complicate some stuff. Let’s say for example that I’m making a dialog system. Some parts of the dialog allow you to…

Add timeout parameter for Event:Wait()

add a time parameter for event:Wait(), a thread will only wait on that event for that many seconds before continuing. will return true or false based on whether the event was called before the waiting limit was reached local WasTouched = part.Touched:Wait(3) -- waits for .Touched up to 3 seconds if WasTouched then --part was touched before 3 seconds else --wait timed out before part was touched end

See discussion on those pages.

This suggestion won’t work generically for all events: in case an event returns no arguments there is no way to distinguish between a timeout or an event actually being fired with just this suggestion. So I wouldn’t approve of this addition simply because there’d be exceptions to the rule that aren’t properly handled.

The workaround linked by Merely above seems elegant enough, and you can modify that to properly distinguish between a timeout or actual event.

PS: this is typically a client feature, it doesn’t apply to just Studio