Space Warp INKEY$ VS Space Warp Mouse!!

[Mitth'raw'nuruodo]

Hmmm...Thats good...I was doing it the long way then...

[Rattrapmax6]

I'm glad I released Beta's,. I ran into the word "Sucks" alot, lol..

Yeah, I've heard of ON KEY keyboard scanning but wasn't going to bother with it,.. as for the Mouse, I thought myself it would suck, but I'm really liking this bit of ASM Mitth has sent me..

Course, I can run a comparo over ON KEY and Mouse, and I might make it where you can chose between the two in opptions depending on out put.

But as for me, once I ratio, well realy scalefactor the mouse X Y to SCREEN 13's X Y, I'm realy rather hooked on the Mouse,.

[Mitth'raw'nuruodo]

That's good, I like the mouse too. Just not that "stick", and the lack of Y control.

But if I make a suggestion, I don't like the ON KEY GOSUB. It's just a event clone of GOTO. But I'm not going to get into that again. (Please don't comment on that).

You can do the same thing easily with the INP(96) statement which is accually better in this case (you wouldn't want to change the coordinates while you were in the middle of drawing you ship now would ya?)

If you are going to go with the keyboard controls (still 3 to 0 vote against that in the poll) use INP(96) instead of INKEY$ (I mean EXACTLY where INKEY$ was) and check the return with keyboard Scancodes table of them in help (must convert table from Hex to Dec) because the scancodes return a DEC or just check it to &HXX(Where XX is the Hex scancode). Then just increase/decrease certain values then update the ship like you did with the mouse.

[Rattrapmax6]

LOL!!! That stick, you know how you fix it.. I did a scale factor equation on the Mouse X to the SCREEN 13's X (The Mouse Y and SCREEN 13's Y are the same, mind) and all I had to was this...

Code: Select all

sx = outregs.cx * 0.5

PS: I got the Y set up, its not so bad (the arc) on the screen as I thought it be,..

[Nodtveidt]

ON KEY is a hack. Avoid it like the plague.

[Mitth'raw'nuruodo]

Right on Nek!

[Pete]

I suggest you guys check out Milo Sedlacek's "Monospace".

It has an excellent pure-QB keyboard handler.

Here's a link to our old review:

http://www.petesqbsite.com/reviews/action/mono.html

[Rattrapmax6]

MonoSpace,. wounder if that still on me harddrive?? hmm Cool game tho no color,.. He should have made a ColorSpace for his sequal.

I'm still really liking the mouse,. More so after:

Code: Select all

sx = outregs.cx * 0.5

No sticking on the right side anymore!! Yay! < Hehe! he look rather k%l,

[Mitth'raw'nuruodo]

that's great $$$. Heh, heh, Mr. Green.

I looked at Monospace (I couldn't resist playing it either). Cool game, lacks color, overly done too (lot of redundant code).

And what he did was basicaly, when a key is pressed he put it in a bolean array with the subscripts = to the keyboard scancodes (he did this all with ASM). Then all he had to do was to see if the value of the scancodes were true (nonzero) or false (zero).

I like it but I could rigg something up simular with out using any ASM!

[Pete]

Hmmm, I guess my memory failed me. I thought Monospace was pure QB. But anyway, it's a very good key handler.

[Nodtveidt]

Monospace IS pure QB, but it uses Call Absolute.

[Mitth'raw'nuruodo]

Yes excatly, but CALL ABSOLUTE () IS calling ASM code. What I meant was to forgo this statement or SetVarSeg. Stupid terminology stuff...

[Rattrapmax6]

WOW! INP(96), I doesn't cycle!!! On wide open, off when I won't it,.. not, on - off (repeat very fast), byby INKEY$ for me(hay, that rhymes!)

Yep, I'll write a INP(96) Beta for spacewarp, maybe make it variable in options for both Mouse and KeyScan!!! HEHE!!

[Z!re]

INP(96) Is just as much QB as CALL ABSOLUTE

And you cant do the same using INKEY$ as Milos keyhandler

[Mitth'raw'nuruodo]

You go Rattra~! Have fun!