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.
Messages - Hayleia
Pages: 1 ... 96 97 [98] 99 100 ... 239
1456
« on: May 04, 2013, 04:21:39 am »
5086: You are at an exam here only one calc is allowed so you use Jacobly's emu on your CX CAS 5087: You whack the ON key during that exam to see better the bug then you reboot your calc to get rid of the bug. At the end of the exam, the examinator comes to you and asks you "Can you swear me that you weren't communicating with the outside ?" 5088: Both previous signs are true stories (true story lol, I had to show her the screen shifting bug  )
1457
« on: May 01, 2013, 04:01:48 pm »
If you know how to handle one object, it is easy to handle several, using a For loop.
For example, to move one pixel from left to right, you do that:
:0->A
:While 1
: Pxl-On(A,0)
: DispGraph
:End
(yeah, infinite loop, I don't care)
...
I'd go for this:
:0->A
:While 1
: Pxl-On(A,0)
: A+1->A
: DispGraph
:End
And if you use repeat getKey(15) instaed of While 1, you can quit the loop by pressing clear. But Hayleia has already said the most basic thing: If you know how to do one thing, you can easily do it multiple times by putting it in a for loop.
Lol at first I had a A++ in the EndIf, which also means that my loop was not infinite, but then I wanted to simplify and forgot to put the A++ back -.- And While 1 / EndIf getKey(15) is more optimized than Repeat getKey(15) / End  (fixed my previous post)
1458
« on: May 01, 2013, 01:01:44 pm »
If you know how to handle one object, it is easy to handle several, using a For loop. For example, to move one pixel from left to right, you do that: :-1->A :While 1 : Pxl-On(A++,0) : DispGraph :End (yeah, infinite loop, I don't care) Now, to move 10 pixels from left to right, you do that (unoptimized): :Fill(L1,10,0) :While 1 : For(r1,0,9) : Pxl-On({r1+L1}++,r1) : End : DispGraph :End Now, I let you guess what to do with your ships and your bullets
1459
« on: May 01, 2013, 07:50:38 am »
Hmm the new version you provided ( http://ubuntuone.com/4Lwc8oddR4SOcfP3L03WNX ) doesn't have any bug... because it doesn't do anything It just produces a file with a .out extension, but its size is 0KB so I don't think I actually have to send it to you to know what thre is inside (note: I tried by renaming ontest into calcemu_cx, launching with file association or launching it directly, and I also tried renaming the rom into "rom" and launching ontest, none of those did anything)
1460
« on: May 01, 2013, 07:38:55 am »
Try replacing your ClrHome with a ClrDraw.
What ClrHome does is clearing the screen, while ClrDraw clears the main buffer, where all your drawings go, and which is copied to the screen with the DispGraph. So if you don't clear it at the beginning of your program, chances are that you are drawing to a buffer that is not empty.
1461
« on: May 01, 2013, 05:23:02 am »
So, bug report, on my CX CAS, as said on IRC.
-An archived Axe source doesn't show up in the compilable progs list, and trying to unarchive it leads to ERR:Memory even before getting to the program list and even if I have 23000 bytes of RAM.
-Screen shifting bug: after quitting the emu, pressing ON makes the screen shift weirdly, but other keys work fine. See the video (sent by email because too large for attachement), where I whack the ON key so that you see what happens, and make some stupid calculatings in the scratchpad so that you see that other keys work fine
1462
« on: May 01, 2013, 03:52:54 am »
Quick question, is there a way to loop through static variables? For example, I have 19 sprites Pic00, Pic01, Pic02,...,Pic18, and I'd like to display them horizontally across the screen (until it reaches the edge and go to the next column).
I've read somewhere that you can use
For(I,0,18)
Pt-On(X,Y,Pic00+I)
End
But all I got is the first sprite pressed down and spread across the screen (think of butter or shift drag in MSPaint).
You already got the answer, but I wanted to precise some things. I think that your problem comes from the fact you said "static variables". First of all, what can a static variable be ? Is is static or variable ? But most of all, your data is not to be treated as variables, static or not, but as bytes, pointed by pointers. This is why when you have a bunch of 8x8 sprites, the first one is pointed by some pointer P, and the second one is pointed by P+8 (as Runer and StreetWalker said), because it is 8 bytes after the beginning of the first sprite in your data.
1463
« on: April 30, 2013, 11:24:26 am »
Nice.
BTW I'm feeling that the scrolling is much too slow, this eventually gets boring hence I don't play this game too much though it's awesome.
Thanks for the feedback! I'll add this to my to-do list and see what I can do 
Some stupid thing I just found out to fasten things a bit is just to add frameskipping. You don't change anything to the drawings to the buffers but you don't always copy them to the screen. That is not really a smart optimization hack but it really works for monochrome games.
1464
« on: April 30, 2013, 11:22:09 am »
Note, if you want your programs to appear in alphabetical order, you can use Jacobly's modified MEMKIT (and give him +1s )
1465
« on: April 30, 2013, 11:19:27 am »
Edit: Runer suggested that I don't post timings so as not to discourage anyone, so I'll just say that my program can get the 5953rd palprime in under an hour.
Lol, that is too late, I got discouraged when I learnt that Runer and you were participating, no need to post your timings
1466
« on: April 30, 2013, 11:11:47 am »
Kind of update:
- fixed the issue with it freezing on inputs
- fixed crashing when trying to install on the wrong OS
- fixed (probably) the C000 issue a few people had on 83+BE's
- fixed an issue involving interrupts and port (07)
Stuff I intend on fixing later:
I came across this "bug" multiple times now:
When you turn off the calculator while you're editing an archived program (the copy of one), and zStart wants to store the edited version and GarbageCollect appears, the LCD turns off and and it doesn't react on any key presses (calc behaves like turned off, but it isn't) before you can do a GarbageCollect. You need to remove the batteries and lose the current progress which is kinda annoying :/
Is there someway you can prevent the calc (or its peripherals) from turning off when the program isn't saved yet?
Can we have find|replace?
I found another bug with Axe compilation. Unlike Axe, zStart doesn't check whether a program is compilable or not, so you can accidentally compile another source file (e. g. a file with subroutines etc.) which is not meant to be compiled as the main program by Axe. It causes Axe to crash or compile another program (like the one directly above or below (?) in the program list). Of course you can avoid this by not doing the On + Sto-> in the wrong place but it happened multiple times when I didn't watch out.
If after a few days, there are no glaring mistakes in this, I'll upload it to ticalc.org finally.
Great :D I'll update as soon as I get a hand on a SilverLink (read: this weekend D:) edit yay ! I gave thepenguin77 his 770 post rating :P
1467
« on: April 29, 2013, 02:10:07 pm »
Yeah, I remember when p2 made it. I don't know why he was fond of peanuts at this time
1468
« on: April 29, 2013, 01:53:16 pm »
 +1 'Nuff said. No seriously, that is awesome. I just had a question since your screenshots don't show it: does it support clipping ?
1469
« on: April 29, 2013, 01:46:09 pm »
I use zStart and AXEPAINT.
zStart is simply the best, no missing features, no more features than you need, all in one page.
1470
« on: April 29, 2013, 01:43:59 pm »
Wait, 200 000 KB ? 200 MB ? I don't really think so But yeah, that is why I asked to describe your problem precisely. Your problem is most likely due to low batteries. I had the same (same as you, programs transferring well but not apps), the calculator never told me "low batteries", neither did the computer, but when I changed them, everything worked well. So try changing your batteries.
Pages: 1 ... 96 97 [98] 99 100 ... 239
|
Show Posts