0 Members and 7 Guests are viewing this topic.
Actually, storing to a variable might be valid syntax in the next version, that is "Hello"->P will be parsed the same as ("Hello")->P
Something like this would be great.
I think he meant built-in icon support, like you can define a description.It's been requested before, I believe.
Matching icons to each program would be too complicated.
.Program [hex for icon image]
Quote from: Deep Thought on November 18, 2010, 07:39:30 pmMatching icons to each program would be too complicated. In what way; I don't quite get what you mean. I think he's just looking for a way to just define the 16x16 icon in the header or something in a similar way that Sir's program gives you hex to paste into the first line of the program, but instead of using Sir's program, it would just be Code: (for example) [Select].Program [hex for icon image] or something similar
[19:19:29] <nemo> anyone know how to add a DCS description in an Axe program?
Quote[19:19:29] <nemo> anyone know how to add a DCS description in an Axe program?Is that possible in Axe? If not, maybe as new feature in one of the upcoming versions?
Allowing For( to take any mem location as a variable. For example, For({L1},0,255) would be really useful.
Nope, no pi. I think Quigibo was thinking of adding it for a different purpose, though (quickly saving as temporary mem).
3.14159265358979323846264338327950288419716939937510->P