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 - macweirdo
1
« on: February 06, 2012, 08:06:21 pm »
Also, a protip:
GitHub (and by extension, Git) is the best way to code a project IMHO.
Sadly, GitHub doesn't support Axe source.
2
« on: February 05, 2012, 10:00:59 pm »
I'll help! This sounds great!
Also, just my two cents:
We should have the ability to have multiple files open (in a screen-split like interface, like G-T mode except without the Graph or Table)
Copy and Paste is much needed
Semi-Parsing of certain types of "project" (like, if this is an Axe Source, do something fancy)
Text highlighting
Sharing files by linking
Saving as either an AppVar or Program or whatever
Editing in either AxeProgram mode, TI-Basic mode, Plain Text, or Hex (list just for starters, don't think I forgot Grammer or anyone else)
In-built compiling for Axe (it's Axe within Axe!)
Gray-scale (with the option to turn it off)
and if we really are aiming for the moon:
windowing.
3
« on: December 12, 2011, 06:54:19 pm »
Does Dispgraph^rr or whichever one makes 4scale change either of the two buffers?
4
« on: December 11, 2011, 08:59:44 pm »
Thanks guys!
Also, if you're really looking to get the exponent of a number, and you're really just doing 2^$something,
just bitshift 1 $something times.
I just don't like looping :(
EDIT: or wait, no
0010 is 2
0100 is 4
nvm, don't even need loops for that
5
« on: November 27, 2011, 01:08:51 pm »
Alright, so I want to read, for example, a single bit of data from a byte.
I tried (L3+offset) and 2 to the power of bit_I_want where L3+offset is my byte of choice and "and" is logical and
but I can't figure out how to get # to the power of other# because ^ is now modulus.
So tl;dr how do you read a bit from a byte and how do you multiply a number by itself many times without using For(?
Thanks in advance :D
6
« on: November 21, 2011, 07:56:29 pm »
EDIT: why do I have -3 karma?
Because three people disliked this post and downvoted it.
Deleted it because I recently lost respect even though that post is ancient. Thanks for taking the time to find that post  EDIT To prevent a double post: Just an FYI, if you absolutely needed more free ram and all the buffers are taken, you could create an appvar and use that:
getCalc("appvMYAPPV", 766)->A
3->{A+766}
DispGraph(L3,A)^^r
You could also do something like
Buff(766,0)->A
3->{A+766}
DispGraph(L3,A)^^r
...although you'd be adding the buffer directly to the program itself (inflating its size by 766 bytes) + I don't think you can modify buffers you have inside the program if you turn your program into an app.
I'm trying to keep it as fast as I can, but I'm never making it an App, this program might be less than 1500 bytes. Can't wait to release my first Axe game
7
« on: November 20, 2011, 07:48:36 pm »
use L6, which is the main buffer
You're serious? Waht? Doesn't that corrupt buffer drawing or something? (btw, I don't understand that statement)
The main buffer is what gets displayed with a DispGraph. If there's something else there, that will be drawn instead.
For instance, try this code and see if you can figure out what is happening:
:ClrDraw
:255->{L6}
:rand->{L6+766}r // This is the superscript r
:DispGraph
:Repeat getKey(15)
:End
So storing data there is just like doing a Pxl-On( to that buffer?
Kind of. It's just another way of drawing stuff.
Remember that the data on the buffer is stored in binary, and because of this 255 = FFh = 11111111b makes 8 pixels in a row black.
Yeah, don't worry, I have prior programming experience. EDIT: why do I have -3 karma?
8
« on: November 20, 2011, 05:12:20 pm »
use L6, which is the main buffer
You're serious? Waht? Doesn't that corrupt buffer drawing or something? (btw, I don't understand that statement)
The main buffer is what gets displayed with a DispGraph. If there's something else there, that will be drawn instead.
For instance, try this code and see if you can figure out what is happening:
:ClrDraw
:255->{L6}
:rand->{L6+766}r // This is the superscript r
:DispGraph
:Repeat getKey(15)
:End
So storing data there is just like doing a Pxl-On( to that buffer?
9
« on: November 20, 2011, 05:01:41 pm »
use L6, which is the main buffer You're serious? Waht? Doesn't that corrupt buffer drawing or something? (btw, I don't understand that statement) Good luck. 
Looks like I'll need it. Thanks
10
« on: November 20, 2011, 04:42:46 pm »
Why is this not stickied anymore?
I have no clue, but it became unstickied recently (like as of today or yesterday.)
11
« on: November 20, 2011, 04:39:34 pm »
So let's say I wanted to have a way to store two bits per pixel on the screen (768 bytes of data, * 2.) into RAM so I could manipulate it. How would I go about doing this, and which safeRam areas should I use (if I use L6, I'll just end up drawing directly to the screen, but I want 4scale as well, and I know it's possible.)
The first one, I'm guessing might be L3, and everytime I want to access data, I'll just do
for bit one:
{L3}+(number of pixel)
and bit two:
{other safeRam}+(number of pixel)
so to draw the screen, I just have to do a
DispGraph(L3,other safeRam)^r
So tl;dr, which safeRam besides L3 should I use for holding the entire screen?
Thanks in advance!
12
« on: November 20, 2011, 03:15:04 pm »
So, say a certain person tried to make a program on their calculator in Axe, but when they made the main loop, they failed at the GetKey= statement and can't quit their program. Make sure your getKey values are Axe keycodes, not BASIC keycodes: http://www.omnimaga.org/index.php?action=ezportal;sa=page;p=21
Yeah, I used the Getkey^r keycodes, because I made a GETKEY program that way, and didn't notice that the Getkey^r keys are different from the GetCSC keycodes. Whoops :p EDIT: fail quotes, that's what I get for not using Preview.
13
« on: November 20, 2011, 10:21:49 am »
But... RAM clear?  I guess that's ok except for the fact that it's effin' impossible to get anything onto a TI-Nspire via Win7 and I'll have to wait another 82 trillion years to put Axe back on. EDIT: HAHANO, Axe is in archive 'cause it's an app! [/noob]
14
« on: November 20, 2011, 09:42:08 am »
So, say a certain person tried to make a program on their calculator in Axe, but when they made the main loop, they failed at the GetKey= statement and can't quit their program.
What should I, I mean they, do?
15
« on: November 12, 2011, 04:06:21 pm »
TYVM
|
Show Posts