0 Members and 7 Guests are viewing this topic.
But in this forum I see a common problem with the answers people give....1) read the manual2) a link to something that may not even be in axe, with the promise its similar
most of the tutorials never even say that you have to use hexadecimal notation for your tilemap declaration pointer.
As I have been going throughout this forum I see a major difference between the forum for TI-BASIC & Axe. The key is in the way people have responded to the different types of programming problems. Now I'm not saying axe parser is anything like the syntax of ti-basic, its not. What happens is the forum for tibasic need only be searched to find out how to do something. But in this forum I see a common problem with the answers people give....1) read the manual2) a link to something that may not even be in axe, with the promise its similar
What I find even worse than that is when someone responds with the irc chatbox and doesn't put the solution on the topic.
Why if the syntax for a simple command such as bitmaps not even mention that you need a header... I dont think that thats good documentation for a command.
Draws a bitmap to (X,Y) on the main buffer, back buffer, or specified buffer respectively. The bitmap data should have in order: width (1 byte), then height (1 byte), then the rows of the image padded with zeros to the nearest byte. Mode 0 is "Pt-On" logic and Mode 1 is "Pt-Change" logic. Mode 0 is used if unspecified.
Now I'm certain that the command list has no single mention of what you have to do to make tilemapping work...
and on top of that most of the tutorials never even say that you have to use hexadecimal notation for your tilemap declaration pointer.
I think that when we do have such a small community of axe users we should maximize the potential for understanding how it works. As ive thought about this alot... how about a more verbose command list.
They are shrouded in a cloud of possibilities. Which are endless, but what I think is a good example is needed for each one with all possible arguments.And the arguments could be colorized to make sence of what is required for the command to work and whats not. Some commands leand themselves to this in the descriptions but some do not. One such example is pxl-on and then you have Bitmap which gives you the options but doesnt tell you how to make bmp in the option.
They are shrouded in a cloud of possibilities. Which are endless, but what I think is a good example is needed for each one with all possible arguments.
And the arguments could be colorized to make sence of what is required for the command to work and whats not.
Some commands leand themselves to this in the descriptions but some do not. One such example is pxl-on and then you have Bitmap which gives you the options but doesnt tell you how to make bmp in the option.
Before: EXP▶Hex Converts the number to hexadecimal and returns the pointer to that string.
After: EXP▶[HEX] -> PTR Converts the expression to hexadecimal and if a pointer is declared it will be available at named pointer.
Example:Code: [Select]Before: EXP▶Hex Converts the number to hexadecimal and returns the pointer to that string. Code: [Select]After: EXP▶[HEX] -> PTR Converts the expression to hexadecimal and if a pointer is declared it will be available at named pointer.The red is not needed, but if you want the pointer to go somewhere you should provide this information.