Author Topic: Features Wishlist (Read 691307 times)

Freyaday · « **Reply #2895 on:** December 23, 2011, 07:01:37 pm »

A version of ClrDraw that fills the screen with black instead of white. For making White-on-black games.

saintrunner · « **Reply #2896 on:** December 23, 2011, 07:03:02 pm »

oooh, I like that! That would have helped with Pogo Dark/Light....then again, I just used drawinv..

epic7 · « **Reply #2897 on:** December 23, 2011, 07:09:25 pm »

Yeah, you could just make the game in black on white, and then used a DrawInv

Runer112 · « **Reply #2898 on:** December 23, 2011, 07:33:56 pm »

Quote from: Freyaday on December 23, 2011, 07:01:37 pm

A version of ClrDraw that fills the screen with black instead of white. For making White-on-black games.

This can be done quite easily already with Fill(L₆,768,ᴇFF), which fills 768 bytes (size of graph buffer) of data starting at L₆ (the graph buffer) with ᴇFF (all bits 1 = black). An optimized form of this is Fill(L₆,768,-1).

A large reason ClrDraw exists is because there is a bcall that does just that. However, there is no bcall that clears the buffer to black, so it wouldn't really make sense to have an Axe command just for it, especially since a built-in routine would do pretty much the same exact thing as the code I wrote above.

parserp · « **Reply #2899 on:** December 23, 2011, 08:45:26 pm »

Quote from: Freyaday on December 23, 2011, 07:01:37 pm

A version of ClrDraw that fills the screen with black instead of white. For making White-on-black games.

hmmm? I thought that is possible with: Rect(0,0,96,64) ?

Builderboy · « **Reply #2900 on:** December 23, 2011, 09:04:55 pm »

There are indeed many routines to quickly fill the screen with black. Runer's is possibly the fastest and most optimized as well

thydowulays · « **Reply #2901 on:** December 23, 2011, 11:31:37 pm »

I really think you should make a Switch command. Like the switch command in C++ you know? You could replace SetUpEditor, since we are using lists for buffer pointers. It would really be nice

EDIT:OMGOMGOMGOMGOMG I LEVELED UP!!!!! I can use omnomirc now

Builderboy · « **Reply #2902 on:** December 23, 2011, 11:34:11 pm »

You should check out the new features on the newest version, there is already a switch command

thydowulays · « **Reply #2903 on:** December 23, 2011, 11:34:53 pm »

:O, are you serious?! *orgasm* Lemme find it

EDIT: Wait, do you know how to use it? I need it for my SPTEXT thing in the GUI library, so I can switch the getkeys that people press

Builderboy · « **Reply #2904 on:** December 23, 2011, 11:45:07 pm »

You can read Quigibo's detailed description in his post here

thydowulays · « **Reply #2905 on:** December 23, 2011, 11:54:20 pm »

Thanks!

Runer112 · « **Reply #2906 on:** December 27, 2011, 12:46:13 pm »

The addition of preprocessor conditionals was awesome, and I will find it very useful. But could there also be something similar to #ifdef? It would be useful for Axe libraries that allow the user to customize them by including defines in their own source code, and the library can fill in any defines with default values if the user didn't define them. The obvious solution would be a new command that determines whether or not the constant is defined. If you don't want to add a new command, you could also try something like the standard preprocessor conditional, but with the constant being used in a trivial comparison, like this:

...!If °Size≥0 8→°Size ...

Yeong · « **Reply #2907 on:** December 29, 2011, 07:12:46 pm »

Able to draw polygonal shapes?
Like Poly(5,10 coordinates draws filled polygon and stuff?

TIfanx1999 · « **Reply #2908 on:** December 30, 2011, 06:25:09 am »

^Would probably be a good Axiom.

Hayleia · « **Reply #2909 on:** December 31, 2011, 07:27:01 am »

Quote from: calc84maniac on December 23, 2011, 11:38:48 am

I think the most effective way to accomplish this would be to have a different static pointer syntax (with a prefix or something) for data on other app pages. That way, the user will be able to control what data is accessed more slowly and what data is accessed more quickly, and Axe will easily know whether to generate a normal memory access or an off-page memory access. If you use a 16-bit pointer for off-page accesses, that's a maximum of 4 pages of data available, and data will be able to cross page boundaries.

Edit: Also, I suppose that when compiling a RAM program, these special pointers could be treated like normal data, as much as RAM allows.

Edit2: Actually, come to think of it, this wouldn't work for specifying anonymous data on other pages. But I guess [HEX]^r and Data()^r aren't taken, right?

Edit3lol: In fact, if the syntax for archived data is Data()→prefixStr1, the syntax for anonymous data could be Data()→prefix

So, with that, would multipage apps with only data on secondary pages be possible ?

Author Topic: Features Wishlist (Read 691307 times)

Freyaday

Re: Features Wishlist

saintrunner

Re: Features Wishlist

epic7

Re: Features Wishlist

Runer112

Re: Features Wishlist

parserp

Re: Features Wishlist

Builderboy

Re: Features Wishlist

thydowulays

Re: Features Wishlist

Builderboy

Re: Features Wishlist

thydowulays

Re: Features Wishlist

Builderboy

Re: Features Wishlist

thydowulays

Re: Features Wishlist

Runer112

Re: Features Wishlist

Yeong

Re: Features Wishlist

TIfanx1999

Re: Features Wishlist

Hayleia

Re: Features Wishlist