0 Members and 2 Guests are viewing this topic.
Quote from: calcdude84se on March 16, 2011, 10:59:57 pmQuote from: Happybobjr on March 16, 2011, 10:43:54 pmSuch as having "appvarScreen" be able to be displayed on the screen (without messing with L3 or L6)We have "BUFFER->DispGraph" No greyscale, though, for that.isn't that the same as Buffer->(l3 or L6 not sure) then display graph?
Quote from: Happybobjr on March 16, 2011, 10:43:54 pmSuch as having "appvarScreen" be able to be displayed on the screen (without messing with L3 or L6)We have "BUFFER->DispGraph" No greyscale, though, for that.
Such as having "appvarScreen" be able to be displayed on the screen (without messing with L3 or L6)
In other news, Frey continues kicking unprecedented levels of ass.
My calculator, and one of my friend's calc (ti-84+ and 84+SE) still cant handle 4 lvl grayscale (and 3 has problems too) So maybe this could allow all users to have better displaying and slow it down enough to work on some calcs (Types L and M that I have seen)Thank you for your time.As a side note, the calc's that I have seen fail with the Gray, also have problems linking together (probably coincidence)
I'm not sure if this is done yet, but it would be nice if axioms who take control of unused system tokens can change their names in the editor, kinda like how Axe changes tokens like Plot1( to Pt-Mask(.
Quote from: Ashbad on March 17, 2011, 01:27:16 pmI'm not sure if this is done yet, but it would be nice if axioms who take control of unused system tokens can change their names in the editor, kinda like how Axe changes tokens like Plot1( to Pt-Mask(.It's been suggested before. I think people said that would slow down the editor too much (it's already scrolling much slower than usual).
No, BUFFER->DispGraph doesn't work anymore. Speaking of which:BUFFER->DispGraph
Such as having "appvarScreen" be able to be displayed on the screen (without messing with L3 or L6)Have monochrome display where both buffers are drawn. (allows masking and other things)Possible more lvl's of gray where you could use Dispgraph( A , L3, L6 ) where A is pointing to something in the ram.
A way to merge multiple buffers into one and two-bit color sprites: black,grey,white,transparent or black, dark grey,light grey,white. I don't know if this has been asked before, custom size sprites?
ClrDrawrr to clear both buffers.
In connection with this, I've always thought it would be nice if the inData() routine returned 0 instead of the position of the terminator when the byte to search for is 0.
Nested libraries would be nice.
An GetCalc() that returns a pointer to the VAT entry of it.
thepenguin77's perfect grayscale tutorial brings up a good request: changing the display routines to advance in rows instead of in columns.
Normally Axe will save changes, but if you get a compile error and scroll to with prgm, it won't save any setting changes.
run indicator going while it's in the process of "Writing APP..."Also, lowercase letters usable in static pointers GDB, Str, and Pic would really help
It would also be nice to be able to back up programs even if they are archived
What I think should be added is the ability to *set* bits through a method other than ORing or ANDing bit masks, of which not everyone is familiar with
or Fix 068 could work.
Could you give axioms the ability to define their own Fix statements? As far as I can tell, the parser handles Fix statements as special cases anyways, merging two one-byte tokens into one command.
Quigibo: if possible can axe eventually have a Select/Switch case structure? Y'know like in C/C++/Java/all that good stuffzMaybe like:Code: (POSSIBLE AXE SWITCH FORMAT) [Select]Switch(X)Case 11->YCase 23->ZCase 5X-Z->YCase ElseSin(Cos(Sin(Cos(X))))->YEnd
Switch(X)Case 11->YCase 23->ZCase 5X-Z->YCase ElseSin(Cos(Sin(Cos(X))))->YEnd
the ability to retrieve the address of our labels.How about using the L token? Like LLB?A to store the address of label LB to A.
How about a command like TI Basic's Stop. More info here: http://ourl.ca/8403/169341An "Exit" command.
When we go in compilation menu, it could be nice to put the last source compiled at the beginning of the list. What do you think ?
2. Did anyone ever request a Axe( command?3. Are there special getkeys for stuff like 2ND+MODE, or do we have to set a variable when 2ND is pressed?.
A switch statement for generating optimized assembly using vector tables would be very used, indeed.
Trinary operators! It would work great in Axe since it relies so heavily on HL. Not sure if it's too late to suggest something so big, though.
alternate steps for For() loops, the same way it is in BASIC?
Can the instant goto be made compatible with CalcUtil's "save screen" option?The save screen is when you quit out of the program editor it asks if you want to save changes or not, very useful but it causes crashes with axe
Quigibo, if you are implementing Switch statements, can you include support for Strings?
While we're at it.. I also suggest adding optimized string comparison functions
An option to disable the token swaps when editing source.
a Symbol Table. In other words, I want to define memory locations other than L1-L6 as alpha-numeric symbols. For example, this:Code: [Select]GetCalc(Str1, 768) -> {L1+700}r...code...Pt-Off(2,5,Pic1)->{L1+700}rCopy(L6, {L1+700}r, 768becomes this:Code: [Select]#Define(BUF,L1+700GetCalc(Str1, 768) -> BUF...code...Pt-Off(2,5,Pic1)->BUFCopy(L6,BUF,768)ASM programmers can do this, so why can't we?
GetCalc(Str1, 768) -> {L1+700}r...code...Pt-Off(2,5,Pic1)->{L1+700}rCopy(L6, {L1+700}r, 768
#Define(BUF,L1+700GetCalc(Str1, 768) -> BUF...code...Pt-Off(2,5,Pic1)->BUFCopy(L6,BUF,768)
First that the Axe-specific entries in the catalog are implemented in the alphabetical order, so that tey're more easy to find.And second a option to compile a progam directly using a menu entry for example in the program menu.
maybe a possible Lite-Axe program that compiles very simple programs on the fly O.o
I think it would be cool if someone made an app kind of like TI 83 Plus Catalog Help, except with Axe commands instead of TI-Basic.
4*4 sprites. Instead of it always having to be 8*8 and doing, say, [F09090F000000000], something like [F99F] would be just a square, and only a square.
I still want 8*y sprites that can be any height sometime. For instance, 8*4...
Changing some of the drawing commands so that they work with the back-buffer/arbitrary buffers, like Text() and Circle().
some sort of sign function that would return the sign (65535, 0, or 1) of a number? Too bad sign{} is already in use though...
maybe a Vertical +2 using a number to tell the parser how many pixels to shift?
Drawing to an arbitrary buffer would be really useful IMO.
Pixel testing an arbitrary buffer would also be fantastic.
A Bitmap( command that draws to the buffer, and a Pt-Mask command with custom height and width, for example Pt-Mask(xpos,ypos,hex,height, width)(cursive is optional argument)
I would also like to be able to read/write to bits instead of just bytes and nibbles.