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 - parserp
Pages: 1 ... 79 80 [81] 82 83 ... 113
1201
« on: October 29, 2011, 12:52:44 pm »
Another good Idea... So all you people: for the things like speed up/speed downs (just added) and other non-moving objects should I use a method such as actual X,Y coordinates for collisions, or something else? and for moving objects? (enemies) 
1202
« on: October 29, 2011, 12:11:48 am »
1203
« on: October 29, 2011, 12:06:27 am »
If u want to earn post ratings... ...then post legitimate content.
It's a surprisingly effective method 
lol it seems to work out very well that way
1204
« on: October 29, 2011, 12:02:00 am »
Whoo the term just ended and I barely passed with a 4.0. hooray for me! (although choir was a HUGE pain in the a**)
1205
« on: October 28, 2011, 11:57:12 pm »
2325: You understood the name parserpadwan the first time you heard the name
2328: you knew what it meant before it was even written (or typed). EDIT: 2329: Ruler changed his avatar while you were posting on this topic.
1206
« on: October 28, 2011, 11:52:37 pm »
You could always store it to L3 (back buffer) and then do recall pic.
1207
« on: October 28, 2011, 08:46:46 pm »
oh yeah duh I am stupid. doing the pic recall erases it. (the buffer) do it at the beginning and do storepic, or whatever 
1208
« on: October 28, 2011, 08:41:08 pm »
of course you don't have to use an appvar.
arrow sprite: Pt-On(X,Y,Pic1)
is that what you need?
EDIT: try doing Fix 5 at the beginning of the program. It might help.
1209
« on: October 28, 2011, 08:37:48 pm »
pic into appvar: (quote from yeongJIN_COOL  ) To Store Pic in appvar: (just create a temp program to do this) GetCalc("appvBLAH",768)→A //appvBLAH created and stored into pointer A [Pic1]→B //Pic1 in OS Stored into pointer B Copy(B,A,768) //Copies Pic1 into appvBLAH put an arrow on the screen? can you elaborate on that? (now I sound like eliza lol )
1210
« on: October 28, 2011, 08:32:41 pm »
don't get it?
1211
« on: October 28, 2011, 08:30:13 pm »
ooh that is WAY more optimized
1212
« on: October 28, 2011, 08:28:22 pm »
lol you posted right after I edited
1213
« on: October 28, 2011, 08:18:24 pm »
one sec... I gotta get code... ok got it... just make a simple drawing program in which you draw the pic desired... (I can help with that too ) and then do this: :If getKey(42) //press store
:ClrHome //duh
:Disp "Saving...",i //imaginary i
:GetCalc("appvPIC",768)->A //appvar PIC created (768 bytes, for a picture) and stored in pointer A
:Copy(L6,A,768) //copies L6 (buffer) into appvar (pointer A)
:Archive "appvPIC" //this is optional, won't delete in ram clears
:End
and to recall it... :ClrDraw
:GetCalc("appvPIC",Y0) //recalls pic from archive and stored in Y0
:For(r1,0,767) //loops through all bytes in pic
:{Y0+r1}->{L6+r1} //copies byte into L6 (buffer)
:End
:DispGraph
Optimized way: :ClrDraw
:GetCalc("appvPIC",Y0) //recalls pic from archive and stored in Y0
:Copy(Y0,L6,768) //copies it into L6 (buffer)
:DispGraph
1214
« on: October 28, 2011, 08:17:16 pm »
hmmm...
my expirience with pics is: DON'T!
I always use appvars, easier to store, recall, and doesn't take up precious pic space.
whenever I use a OS pic, it puts the pixels wherever it wants.
1215
« on: October 28, 2011, 08:13:37 pm »
no as in Pic0 and Pic9.
EDIt: does it compile?
Pages: 1 ... 79 80 [81] 82 83 ... 113
|
Show Posts