|
|
Post by IsmAvatar on Apr 14, 2004 15:14:49 GMT -5
you put it whereever you want it. Let's see, if you want to check for the joystick whenever, let's put it in the create event... **stares with mouth open**... Here's a hint, the step event looks kinda hungry.
|
|
|
|
Post by jeremylacroix on Apr 15, 2004 11:03:31 GMT -5
Would I have to do that with every object? Can I put it by keyboard_wait? I had something working in keyboard wait but it made it so that if you are using the keyboard the text scrolled WAY too slow, but if you use the joystick it scrolls it so fast you can't read it, with the touch of a single button.
|
|
|
|
Post by IsmAvatar on Apr 15, 2004 14:54:25 GMT -5
I don't know, I'm not familiar with the situation you are using it for. Try different things. Modify things, change things up, tweak, debug. If something doesn't work, try something else. If you find you have to put it in every object, then guess you have to, because you don't want to make it it's own script (which is only your own loss)
|
|
|
|
Post by jeremylacroix on Apr 15, 2004 16:22:07 GMT -5
I just don't see the point in having two scripts for one thing. Can't it be placed in the script I already have?
|
|
|
|
Post by IsmAvatar on Apr 15, 2004 21:56:56 GMT -5
yes, it can. But I find when you refer to something multiple times (more than once), to either make it a script or set it to a variable.
But it most certainly can be left alone, it just leads to bunchy and repetitive coding, which can be hard to read.
|
|
