316
Axe / Re: Some questions: Toggle button, Buffers, Appvars
« on: October 30, 2011, 06:29:47 pm »
Thanks a lot, jacobly! - I think that is fast enough, and you can use arbitary buffers too.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to. 316
Axe / Re: Some questions: Toggle button, Buffers, Appvars« on: October 30, 2011, 06:29:47 pm »
Thanks a lot, jacobly! - I think that is fast enough, and you can use arbitary buffers too.
317
Axe / Re: Some questions: Toggle button, Buffers, Appvars« on: October 30, 2011, 05:43:03 pm »
Ok, but then I cannot use the other keys the same time, right?
318
Axe / Re: Some questions: Toggle button, Buffers, Appvars« on: October 30, 2011, 05:27:12 pm »
Thanks jacobly. I will try that out.
Has someone any idea to solve the other problems? 319
Axe / Re: Some questions: Toggle button, Buffers, Appvars« on: October 30, 2011, 09:07:38 am »
Thanks Xeda for your attempt solving my problem, but I think it isn't exactly that what I'm looking for.
I will explain what I need: Let's say D is our toggle variable (at the beginning 0), and Enter the key. So if I press Enter, D toggles to 1. If I hold down the button, nothing should happen. If I release the button, nothing should happen. If I press Enter again, D toggles back to 0. If I hold down the button, nothing should happen. If I release the button again, nothing should happen. Edit: This is the way I do not want it: Code: [Select] 0->D
320
Axe / Some questions: Toggle button, Buffers, Appvars« on: October 30, 2011, 07:28:39 am »
Planning my new project I'm going to make in axe, I came across some questions about how to do stuff in axe (V 1.0.5)
1. How can you make it that a variable toggles from 0 to 1 and vice versa if you press a special key, but it doesn't keep toggling when you hold it? It shouldn't influence the other getkeys for movement, etc. in the same loop. 2. Is it possible to display two buffers on top of each other (or / xor) without having greyscale? 3. Is there a short way of letting to user chose from a bunch of saved files (appvars) to reload or chose the file to save the data, without having that many If-statements? 321
The Axe Parser Project / Re: Features Wishlist« on: October 28, 2011, 12:24:48 am »
Yeah, that would make things a lot easier - same syntax like C++.
322
Axe / Re: Routines« on: October 25, 2011, 07:17:19 am »
Thanks, that's good enough for my purposes.
I found a pixel-wise xor (or / and) function for sprites, to invert a sprite if it is on dark background. Code: [Select] pt-Get(X,Y)->W
323
Axe / Re: Routines« on: October 25, 2011, 01:23:50 am »
Does someone know a short and fast routine for a broke / dotted line?
324
The Axe Parser Project / Re: Which Axe version do you use?« on: October 24, 2011, 03:32:36 pm »no, L1 is not a buffer, just a free ram area. But "L6 (main), L3 (back)" is right (or maybe it is the contrary )Thanks, but I never used such code in my programms. 325
The Axe Parser Project / Re: Which Axe version do you use?« on: October 24, 2011, 10:58:17 am »
Right, but only for specific buffers - and due to the lack of them in 0.5.3 I won't have to change anything... I think.
And how do these specific buffers work? These are L6 (main), L3 (back) and L1, right? 326
The Axe Parser Project / Re: Which Axe version do you use?« on: October 23, 2011, 02:36:59 pm »
Ok, then I change...
327
The Axe Parser Project / Re: Which Axe version do you use?« on: October 23, 2011, 04:08:16 am »
I'm panning a new (larger) project in AXE and I'm still using 0.5.3, should I chnage now? is 1.0.5b completely stable?
329
Axe / Re: Jumping« on: October 21, 2011, 12:55:23 am »
really, Quigibo? I could swear that in 0.5.3 it was signed.
330
Axe / Re: Jumping« on: October 20, 2011, 01:35:29 pm »
After skimming your code which looks OK, I found four things:
- usually, you start arrays with the value zero, change that everywhere else. - You have to use signed multiplication ( ** ) to multiply with a value less than zero. - You are storing the direction value into the x-value, that won't work, so just add 5 to the pointer. - If you use a version below 1.0.1 of axe, use the addition sign for conditions, not the 'or' keyword Code: [Select] :If ({L1+F}=1)+({L1+F}=86) To optimize a bit, use just one for loop for everything, than the speed will increase drastically. Code: [Select] :For(E,0,4) Hope that works |
|