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 - Quigibo
Pages: 1 ... 87 88 [89] 90 91 ... 135
1321
« on: June 13, 2010, 12:03:38 am »
0.3.0 will be a gamma version. Its basically the same thing as a beta version, but with a cooler name. Stability is relative. Since this problem only affects compiling from archive, you could argue that the version when you couldn't do that was more stable. But really, you can do the same thing now, its just that with the addition of new features, its usually the new stuff that can get unstable.
1322
« on: June 12, 2010, 10:48:51 pm »
Thanks, so that should finally stabilize it. I'm adding page swapping now, it's fairly simple. I just have to make sure that only my main routines are called when reading bytes and that I'm not using any exploits in the code anywhere. 0.3.0 will come in less than a week, but I won't have app compiling working yet unfortunately. But there is another cool new feature that will come in handy 
1323
« on: June 12, 2010, 10:12:41 pm »
I THINK I MIGHT HAVE FOUND IT!
I need some asm expert to answer this question:
The user ram is 24-ish KB right? So it is possible to make a program over 16KB right? You can archive this program right? Wouldn't that imply that you can have a single program take up 2 pages of rom? Does that also mean that a program less than 16kb can also take up 2 pages since none of the rom is actually wasted? Because that would mean I have to switch pages at some point during compile time, something I'm currently not doing when reading from archive. Of course if any of these assumptions are wrong, then it must be something else...
1324
« on: June 12, 2010, 09:55:50 pm »
Wait, is this replicate-able? Can you post the source that does this?
1325
« on: June 12, 2010, 09:49:05 pm »
I don't understand how that's possible. I'm only using OS bcalls when writing to rom and as Deep Thought stated, its not an issue with any part of the RAM since it continues after a ram clear it has to be somewhere in rom.
@Runner12
You're getting errors with the source or previous executable in archive? What errors and where would it scroll?
1326
« on: June 12, 2010, 09:36:19 pm »
Okay, I think I might know what the problem is. Can those who had problems confirm this:
Were your executables archived prior to compiling a new build of the program? I think becasue the app has to delete the archived programs so often it causes the OS to mess up the rom somehow which causes other problems. I might have to have Axe automatically garbage collect or something to solve this. That would also explain why most people who are getting this error are using shells, becasue you can run the programs when they're archived.
1327
« on: June 12, 2010, 07:57:39 pm »
Very cool and very innovative! I actually made a little thing like that myself to try it 
1328
« on: June 12, 2010, 05:47:13 pm »
I occasionally use it. Sometimes, its for speed considerations, sometimes for size, other times for simplicity. Its not too difficult to copy small code segments from apps into ram and then execute them there so compatibility is usually not an issue. One smc I really like to use is modifying (ix+0) and change the 0 to other values to really quickly read and write to the nth element of a list without using any extra registers. I did this in Pyoro for the "closest block" algorithm.
1329
« on: June 12, 2010, 05:16:12 pm »
Reading the link port in assembly is simply this:
in a,(0)
and 3
Result 0-3 is in A. The rest of the hex is just to put it into HL for axe input.
1330
« on: June 12, 2010, 02:42:26 pm »
You could have the logo be grayscale. Then all you have to do is draw the logo to the back buffer and never worry about it again. Just update the screen with DispGraphrr.
Another, more annoying way to do it is to split the logo into a bunch of 8x8 sprites and then use Pt-Change() to add and remove it every frame.
1331
« on: June 12, 2010, 02:36:56 pm »
Just play around with touching different wires together and see how it affects this code:
Repeat getkey(15)
ClrHome
Disp Asm(DB00E6036F2600)>Dec
Pause 100
End
1332
« on: June 12, 2010, 02:29:39 pm »
There are 3 pins (wires) to the cable. One is ground. The other 2 are input. If the input cables are not connected to anything, just dangling wires, then they are "high". But if they touch the ground wire, they become "low".
1333
« on: June 12, 2010, 02:22:21 pm »
In Axe, you can use this code:
Asm(DB00E6036F2600)
It returns a number 0-3. I don't remember the codes, but the possibilities are left high right high, left low right high, left high right low, and left low right low.
1334
« on: June 12, 2010, 12:41:46 am »
Finally, a 3rd party tutorial! Looking forward to it
Pages: 1 ... 87 88 [89] 90 91 ... 135
|
Show Posts