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 - Builderboy
Pages: 1 ... 319 320 [321] 322 323 ... 375
4801
« on: February 07, 2010, 12:23:06 pm »
Alright thanks ^^ I also have some bugs (well not quite bugs) with the output function. When displaying a character/number on the bottom row, the rest of the screen is shifted up. This would be nice if it could be turned off for output, as the scrolling migt disrupt other graphics. My second gripe is that when displaying a single digit number at a certain location, the number doesn't actualy appear where the coordinates you specify are. For this reason I don't think it's possible to display numbers in the left few colloms? Just two things with output that I think might need to be changed 
4802
« on: February 07, 2010, 02:33:12 am »
Good idea * Builderboy rushes off to clear Ram and save lives * And here is that program, I don't think i was doing anything wrong  :DiagnosticOff
:
:0→A
:0→B
:0→K
:
:While K≠15
:getKey→K
:
:Output(A,B,"
:If (K=3) and (A≠15
:A+1→A
:End
:If (K=2) and (A≠0
:A-1→A
:End
:If (K=1) and (B≠8
:B+1→B
:End
:If (K=4) and (B≠0
:B-1→B
:End
:Output(A,B,"O
:
:End
:
:ReturnAnd the 8xp file in a zip for ya
4803
« on: February 07, 2010, 02:11:59 am »
Ok i found another weird bug. When compiling one of my programs, the compiler stops while compiling and a blinking cursor appears beneath the Compiling message. No matter what button i press, the cursor just keeps blinking. So i am forced to pull my batteries, but although i quit back to homescreen, there is no RAM clear I'll try to get the program uploaded in a sec...
4804
« on: February 06, 2010, 10:59:25 pm »
So these are the currently wanted formats to store the source data in if i cam correct:
Pics: Easy to edit and easy to view/preview sprites. Take up a lot of space however and source will not be in one file. Pics may or may not be archived to save memory, and storage is efficient with 8 pixels per byte)
Binary: Just 1s and 0s in the program, easy to type and edit, and easy to preview, however this is VERY memory inefficient, at 1 byte per pixel. Cannot be archived either, as it resides in the source program.
Hex: Similar to Binary but every 4 bytes is represented as a char from 0-F. More memory efficient but harder to see what the sprite is supposed to look like, and harder to edit. Cannot be archives. 4 pixels per Byte.
Tokenised: Taking Hex a step further, each 2 hex codes is tokenized by a program or the OS and recalled into the program. Twice as efficient, but even harder to edit/preview. Cannot be archived. 8 pixels per byte. Same storage capacity as a pic, but can change size according to how many sprites you need.
Appvar: Data is stored in an appvar by some sort of sprite editing program and can be archived for memory uses. This is memory efficient but makes for difficult previewing and multiple files for the source. 8 pixels per byte.
I personally am for Pics and Binary, if only because Hex/Tokens/Appvars are difficult to edit quickly and preview without external programs. Also for making large amounts of sprites, like for huge tilemaps, it would be nice not to have a bunch of hex/tokens in your program, and be able to view the whole sprite map in one pic. It also helps for sprites that are greater than 8x8, as they will have to combine multiple 8x8 sprites, which might be difficult to do/visualize with hex/tokens.
4805
« on: February 06, 2010, 02:24:29 pm »
Hmmm, id rather not have tokenised hex, as then you would have to rely on other assembly programs besides Axe, and i think that would kind of defeat the purpose a little. I personally would like either Pics or Pure Binary as the picture format storage, as they are the easiest to view and edit, a must while working on games. Pics would be used when you have large ammounts of sprite data, and could be archived if needed. And Binary would be used when you have a small amount of sprites or just want to play around a but. And then when compiling the program, the pics/binary would be stored into the program itself so that there is no need for any pics/appvars to run your program.
4806
« on: February 06, 2010, 01:58:00 pm »
I just have a program called XtraVars  Not only does it have all the tokens, but also all the pics/strings/matrixes that you would ever need! ^^
4807
« on: February 06, 2010, 02:23:50 am »
true true, its cool that you don't need the assembly programs after you recall it though, so it technicaly could be considered pure basic, just not pure basic while programing But i know what you mean
4808
« on: February 06, 2010, 02:17:44 am »
You could always use an Assembly program to get the actual % token and just display that instead
4809
« on: February 06, 2010, 01:58:01 am »
:O I got an error on Easy speed Fast For(Q,15,N-3,-1 [A](2,Q->U <- right here For(L,3,6 Q was zero, and this is what the board looked like  I got quite a bit of gameplay in before it broke though ^^
4810
« on: February 05, 2010, 08:28:58 pm »
Ah i see. Thanks for the info
4811
« on: February 05, 2010, 07:04:33 pm »
Yay! I like it ^^ I can see how you were inspired a bit, but it actually is quite a bit different from Factory, definitely original. Good job!
4812
« on: February 05, 2010, 07:02:51 pm »
It seems that OR does not work  I have this program 0->A
1->B
If A=0 or B=0
Output(0,0,"HI
EndAnd when i compile and run, nothing is displayed.
4813
« on: February 05, 2010, 02:57:06 am »
Yeah I think it can, imma have to see I can find that.
4814
« on: February 05, 2010, 02:55:11 am »
Yeah I do, Its a Habbit I picked up from an old board. I just find Anything more than a little bit of yet distracting.
4815
« on: February 04, 2010, 07:42:47 pm »
Its an imprecise technology >.>
Mostly the error was due to attempting to interface with such a device such as the iTouch using remotely controlled gerbils.
Pages: 1 ... 319 320 [321] 322 323 ... 375
|
Show Posts