Author Topic: Features Wishlist (Read 705273 times)

SirCmpwn · « **Reply #270 on:** March 16, 2010, 04:46:32 pm »

I made a little program that will convert the graph screen into hex so you can paste it into Axe source. Thought it might be useful. What you need to do is run the program with your picture on the graph screen, wait about 5 or 6 minutes, and when it is done it will paste the hex into Ans.

ztrumpet · « **Reply #271 on:** March 16, 2010, 05:03:51 pm »

Looks nice Sircmpwn.

Personally, I like lists as they are. I think once you figure them out, they will be no trouble, and they're vary nice as is. I'd rather have better access to the hardware with {X*3+8+L1} than L1(X*3+7). (Remember these are my views, and no one's views are wrong because of them.

)

SirCmpwn · « **Reply #272 on:** March 16, 2010, 05:10:51 pm »

Quote from: ztrumpet on March 16, 2010, 05:03:51 pm

Looks nice Sircmpwn.

Personally, I like lists as they are. I think once you figure them out, they will be no trouble, and they're vary nice as is. I'd rather have better access to the hardware with {X*3+8+L1} than L1(X*3+7). (Remember these are my views, and no one's views are wrong because of them. )

A) Thank you
B) Agreed, it should stay that way.

DJ Omnimaga · « **Reply #273 on:** March 16, 2010, 11:06:44 pm »

Nice program,. it might be useful for those who dont want to use the computer (BMP to z80 for instance) to convert pics.

@ztrumpet, yeah I guess it might be better this way, as long as we don't have to define lists with hex data. I would rather be able to define them like in basic or close. Having to convert everything to hex before storing it to list would suck imho

calc84maniac · « **Reply #274 on:** March 16, 2010, 11:55:36 pm »

I think getKey(0) should tell whether any keys at all are pressed. Here is an example of how you could do it (feel free to write your own though):
xor a out (1),a ld h,a ld l,a in a,(1) inc a ret nz inc l ret

Edit: I modified it so the output would make more sense considering how the rest of the getKey() operations work. Now it returns 1 if no keys are pressed, 0 if keys are pressed.

DJ Omnimaga · « **Reply #275 on:** March 17, 2010, 01:46:15 am »

That reminds me, how many keypresses at once can we use in an Axe game? I noticed some games detects like 3 at once, like the shooter example. I could move diagonally and shoot at the sane time. In BASIC only one is possible at once and in xLIB two (only arrows, others = 1 keypress) and Celtic III a bit more than arrows

calc84maniac · « **Reply #276 on:** March 17, 2010, 07:36:46 am »

Quote from: DJ Omnimaga on March 17, 2010, 01:46:15 am

That reminds me, how many keypresses at once can we use in an Axe game? I noticed some games detects like 3 at once, like the shooter example. I could move diagonally and shoot at the sane time. In BASIC only one is possible at once and in xLIB two (only arrows, others = 1 keypress) and Celtic III a bit more than arrows

The limit is the same as in ASM, which is the limit of the keyboard itself. Just remember that if you press 3 keys that are the corners of a rectangle, the 4th corner of the rectangle will be detected pressed as well.

Quigibo · « **Reply #277 on:** March 17, 2010, 01:36:06 pm »

I'm almost positive that you can detect as many keys at one as you need. I don't think there are actually any limits by the nature of the commands.

What is the effect of this though?
xor a
out (1),a
I've never seen this used. I thought it only works when a in binary is a combination of all ones and a single zero.

getkey(0) is a good idea, but isn't getkey=/=0 basically the same thing? I was actually planning on making getkey(0) detect the [on] button.

EDIT: wait nevermind, you were requesting an indefinite return. Regular getkey only is true once and then gets reset back to zero. I'll have to add that command.

DJ Omnimaga · « **Reply #278 on:** March 17, 2010, 01:42:45 pm »

Mhmm interesting

Also can both getkey commands detect multiple keypresses? And when multiple ones are pressed, what does one getkey command returns as number?

Quigibo · « **Reply #279 on:** March 17, 2010, 01:49:35 pm »

No, "getkey" tells you the last key pressed once and then gets reset back to zero. Its essentially identical to the basic getkey but with different numbers.

"getkey(KEY)" tells you if that particular key is held down right now. So you can chain these together like "getkey(1) and getkey(2)" notice I don't need the parenthesis on the and operation since they're boolean.

DJ Omnimaga · « **Reply #280 on:** March 17, 2010, 01:52:05 pm »

ooh ok I thought one single getkey command checked for all keypresses. In BASIC, if you do

If getkey=25
A-1->A
If getkey=24
B-1->B

good luck moving diagonally.

At least that's a good plus that Axe allows multiple keypresses ^^

ztrumpet · « **Reply #281 on:** March 17, 2010, 04:34:52 pm »

Quote from: Quigibo on March 17, 2010, 01:36:06 pm

I was actually planning on making getkey(0) detect the [on] button.

Could you make the On button have a number? That would be useful at times!

I don't know what number to use, but there are plenty to choose from.

calc84maniac · « **Reply #282 on:** March 17, 2010, 09:38:49 pm »

Quote from: Quigibo on March 17, 2010, 01:36:06 pm

I'm almost positive that you can detect as many keys at one as you need. I don't think there are actually any limits by the nature of the commands.

What is the effect of this though?
xor a
out (1),a
I've never seen this used. I thought it only works when a in binary is a combination of all ones and a single zero.

getkey(0) is a good idea, but isn't getkey=/=0 basically the same thing? I was actually planning on making getkey(0) detect the [on] button.

EDIT: wait nevermind, you were requesting an indefinite return. Regular getkey only is true once and then gets reset back to zero. I'll have to add that command.

If you set more than one bit to 0, you can select more than one key group. All the pressed keys in the groups are ANDed together. Thus, you can test for the "any key" quite easily this way.

Builderboy · « **Reply #283 on:** March 21, 2010, 11:43:01 am »

Mmmm i think i'd like support to compile the program with ON breaking enabled for debugging (since you said it takes up a +300 bytes to handle the interrupts) but it would be a huge plus for those not working with interrupts and not wanting to deal with them, especially for those who don't understand them. It can be a huge lifesaver during debugging though.

DJ Omnimaga · « **Reply #284 on:** March 21, 2010, 01:39:04 pm »

personally I like the idea of letting the user choose when compiling. Example:

Choose if you want ON to be enabled
CHoose if you want error checking ON
Choose for what shell to compile for
Choose to store the compiled program in RAM or Archive

I don't know if I forgot any

EDIT:

The ability to draw the back-buffer directly to the LCD
The ability to store the LCD content straight to the back-buffer

Author Topic: Features Wishlist (Read 705273 times)

SirCmpwn

Re: Features Wishlist

ztrumpet

Re: Features Wishlist

SirCmpwn

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

calc84maniac

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

calc84maniac

Re: Features Wishlist

Quigibo

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Quigibo

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

ztrumpet

Re: Features Wishlist

calc84maniac

Re: Features Wishlist

Builderboy

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist