Help needed ASAP, thanks.

[CNguy]

Hello all,

So I have been making a presentation with rmxp.
But the problem is I'm stuck.
I want to get a picture scrolling up and down when we press the buttons up and down.
I have the basic codes ready already, its scrolling is working with one major error.

The key doesn't repeat itself, or, the variable inputs itself only once, therefore, we must repetitively punch the down or up key to scroll the picture up or down.

My idea was, to press the key once and the variables will continue to write itself continuesly, so that the picture will scroll if we hold down the buttons.

Any idea how to make the variable input be continues?
If so can you include a crude code to do that? thanks. (default codes)

 

[Despain]

I don't have the program with me right now so I can't really test anything, but this MIGHT work for you.

You're probably using the Key Input Processing (or whatever it's called) command that traces the key input to a variable. Instead, look into the option "If a key is being pressed" in the conditional branches. It might work better for what you're doing. I'm not 100% familiar with it because I used the first method myself, but it's worth a shot.

 

[CNguy]

Mm, thanks for the suggestion but it still has the same error. But thanks for that anyway ^^

 

[Reives]

What are your implementations in terms of scrolling pictures to begin with?

Here's what should work:
Parallel processing - Conditional branch, key input "up"; inside that make it decrease a variable Y by a small margin (decreasing Y = go up). Then have another conditional branch (outside of the last one) doing similar things for "down", only make it increase the same variable Y instead. Outside of both conditional branches, perhaps have a wait command for like 2 frames to slow down the scrolling if you want, but probably not necessary.

In another parallel processing event, do the command "move picture: (fixed x as you name it), VARIABLE Y (that you are manipulating in the other event). Don't forget to actually show the picture (but not in neither of those events!) first.


By the way, your name is EXACTLY the same as my last year's roommate's WoW character name...... Although I know that it's not him because you are typing in proper capitalization and grammar. D: But still kinda creepy.

 

[CNguy]

Mm, truly, names are deceiving. Ah, anyway, I had that code input already, so thanks for reminding. And correct spelling ftw!

Anyway, I found out the error now.

I had two events. One common, the other an on-screen type of event, both with the same input, because I was wondering if its the type of event that causes the mix-up. However, I didn't notice that when I changed the common event input (to the one Despain suggested) I had the on-screen event running instead of the common event (both had specified switches that I forgot to toggle and replace). So I continued to experience the error until I checked my activity log and notice that I had turn the common event off and left the other one on. (handy to have one to remind you of the event history [changes]) So now I changed it already and it works.

Sorry for the mix-up, guys (especially Despian^^). Cheers! Have a good night/day. And, be seeing you all around.