Talk:Wait - Utility

Note about IsFurnitureInUse

The note about using this function to check when "crafting mode" was active was added to this page because Wait can be used to cause a script to wait for a menu to close before executing more code. However, even though the various "crafting modes" cause menus to display, they don't cause the game to enter "menu mode", and Wait cannot be used in this way.

The wording of the note didn't make its relevance particularly clear, though, I'll admit. Perhaps the best approach would be to leave the note where it currently is, on IsInMenuMode and add that function to the "See Also" section here. What do you think?

-- Cipscis 04:56, 15 February 2012 (EST)

Interesting, thank you! :) You're right. I was thinking "this function can't be used to detect menus at all, it explicitly ignores them... why would someone using it, care about menus?" I had not considered this use of wait to detect the *absence* of a menu. I've had a bash at a couple lines to explain this for newbies like me - whatcha think? --Catwheezle 17:31, 15 February 2012 (EST)

That looks much better, thanks :)

And while I'm thanking you, thanks for all of the great edits you've been making - you've certainly been busy here and that's excellent!

-- Cipscis 17:34, 15 February 2012 (EST)

That big list

I'm not happy with that big list of ways to wait for stuff that I made, but I'm not sure how to best address my problems with it.

My first problem is that it's a big, ugly, hard-to-digest list. Maybe a table would be a better format, with columns for "what", and "how it's used".

My second problem is findability. I've tried to link to this page from all respective pages, so that the big fat list wouldn't need to be included on every page. So it may be slightly findable from that. I've also tried to make sure that the page will appear on most searches by having all the words that people might search for: sleep, wait, pause, time, timer, etc.

But is this page the best place to have it? Should I have stuck it on Wait rather than Wait - Utility? Or somewhere else?

Should the big list actually be a disambiguation page? --Catwheezle 01:25, 16 February 2012 (EST)

Pauses the script?

As it reads now, the first sentence is: "Pauses the script for at least the specified amount of real-world time." The fact is that this just isn't exactly true. Whether intended or not, the statement implies that the function temporarily stops the script from doing anything at all. I mean, if I wrote a script like:

Event OnInit()
RegisterForSingleUpdate(10)
Utility.Wait(5)
Debug.Notification("5 seconds have passed.")
endEvent

Event OnUpdate()
Debug.Notification("10 seconds have passed.")
endEvent

after 5 seconds, I'd get the first notification, and 5 seconds later, I'd get the other notification. Perhaps, the sentence should be rewritten to this effect because it appears to me that the function seems to only stop what is going on in the event/function in which it is located. --BrotherBob (talk) 2013-11-17T12:37:04 (EST)