o_o I think I will participate, but if I make it to the finals, I won't be able to participate unless I get a Skype thing (I have no camera or mic).

Still, just in case I do get those in time, I should enter o.o

EDIT: I entered in TI-BASIC, z80 Assembly, and 68k BASIC. Also, because I plan to change my name in the future and I have started to use the name IRL, I am using that name instead of my legal name. This way if I do well I can put it on a CV ^-^

Thanks! In code, I currently have this but I want to change it:
MainMenu:
     Menu("Command Index",cmdindex)
     Menu("Math Tutorials",mathtutorials)
     Menu("Programming Tutorials",programming)
     .db 0
programming:
     Item("Hello World",ex_helloworld,0)
cmdindex:
mathtutorials:
     .db 0
Anything labeled as a Menu() will open a new menu when it is selected and anything labeled as Item() well set it as the tutorial to use. I think I will make it a simple list that the user can scroll through and I think that I will change the format, too. This way the menu or item name is part of the data and there can be several organisation options. For example, a command that falls under several categories might be like this:
MainMenu:
     Menu(cmdindex)
     Menu(mathtutorials)
     Menu(probstattutorials)
     .db 0
cmdindex:
     .db "Command Index",0
     Item(cmd_nCr)
     .db 0

mathtutorials:
     .db "Math",0
     Item(cmd_nCr)
     .db 0

probstatstutorials:
     .db "Probability/Statistics",0
     Item(cmd_nCr)
     .db 0
cmd_nCr:
     .db "nCr",0
     .db tut_nCr
And now each menu is just an LUT of 3-byte elements. 1 byte is for the Menu/Item and 2 bytes for the pointer to the item data.

Could someone check the list of bugs on the 1st post and post whatever is missing that was discovered in recent years? It would definitively be nice to complete that list, especially with the MP OSes. Please, only OS bugs, not bugs caused by ASM programs and stuff.

Okay, I updated it

Also who thinks that most OS 2.43 and 2.55 MP bugs will still be present in OS 4.0 for the Color 84+?

The game.

You probably don't even need to file it down. I can use the 2.5mm headphones just fine to listen to music on the calc. I should look into a better method for making a cable, though. I have a 3.5mm to 3.5mm cable with two adapters for 2.5mm→3.5mm, but the connection gets kind of iffy and it needs to be just right for both lines to connect.

I need to adjust the program a bit because I realised that I made a silly mistake. (Warning: This is complicated ASMy stuff): Since the keyhook automatically deletes the first element from the string once it is read, I ran into a problem when I made a key sequence to create and edit a program or equation. I realised this last night which is why I tested it and it is because the edit buffer is still open. I think that what I will do is if the edit buffer is open, I will just fill the bytes with 00 and treat those as null bytes, then when the edit buffer is closed, I will delete all the appropriate stuff.

Now, stuff I have been thinking of adding:

• *<<number>> to execute a key press a number of times. This shouldn't be difficult to add.
• For(number)<<key sequence>>End to execute a keysequence a number of times. This might be difficult to do since I will need to somehow keep track of which key to execute next.

EDIT: To give an idea of the syntax for *, I am thinking something like 3*7 will simulate pressing right 7 times. I already have the code planned for this, so if I have time today, I will try to have it implemented

EDIT:22 April 2013
This topic is now renamed Tutor App as the project has evolved. An updated version can be found at this post later in the topic.

---

(original post)

On TI-BD, there was an idea for simulating keypresses, so I offered my assembly program to simulate a keypress. But then they wanted to simulate a list of keypresses, so I finally started working on that. Currently, whenever the OS looks for keypresses (not while programs are executing), the hook looks for the hacked string 17 (AA11h) and if it contains data, it will read the numbers one at a time, executing the keypresses.

The keypresses are not getKey values. If you have used assembly keycodes (where Enter=9, for example), that is the set you will want to use. To simulate pressing [2nd]+[nobbc], add 56, to simulate [ALPHA]+[nobbc], add 112. So for example, [Graph]=49, [PRGM]=31, [MATH]=47. To open the graph screen, then press [2nd][prgm] and then select 1:ClrDraw, use:
"49,87,9
To do that, then select the A:Pen from the draw menu, add an additional 87,159 (159=112+47). Finally, the arrows are 1=down,2=left,3=right,4=up. Combining all this:
"49,87,9,87,159,9,2,2,2,2,1,1,1,1,3,3,3,3,4,4,4,4
That will select ClrDraw, then Pen, then it will draw you a box

I worked on Grammer a little bit yesterday and at some points I  had precisely 0 bytes of coding space. However, I removed two undocumented experimental routines for sending/receiving bytes over the I/O port and now there are 69 bytes of coding space available!

As to the updates, I may have broken some things because I made a few more complicated modifications. I am pretty sure that I checked everything that could be affected, but I may have missed something.

• Else is finally added as a command. In a very basic way, Else works like you would expect:
  
  Code: [Select]
  If A=B
Then
<<do stuff>>
Else
<<do stuff>>
End

• Else has some complicated things that it can do. The way I implemented Else, it can stand alone as its own command. If you do this, it will seek an appropriate End token. For example:
  
  Code: [Select]
  While A>3
A-1→A
If A=5
Else        ;This will skip over everything until it finds the correct End
If A=4
Then
<<do stuff>>
End         ;not the correct End!
End         ;The correct End!
If you don't uderstand that, don't worry. As well, you can do something like this:
  
  Code: [Select]
  While A
A-1→A
Text(0,A,"O
Else
DispGraph
End
That is actually a neat trick to help you understand how Else works, but it isn't optimised That basically does this:
  
  Code: [Select]
  While A
A-1→A
Text(0,A,"O
End
DispGraph
Personally, I would just stick with the first use. The other methods will just complicate your code and probably cause confusion when parts of code don't work.
  
• Typewriter Text has been fixed! Now you don't need a DispGraph after using /Text( to see the last character.
• The degree token now acts as a command on its own, too. This can be used to temporarily change the draw buffer for the Text( command. Any command that has an optional buffer argument will revert the draw buffer back to normal. So for example, if Z points to the back buffer:

oZ           ;o is supposed to be the degree token
Text(0,0,"HI!
Text(6,0,"This is on another buffer.
Pxl-On(3,3
Text(0,0,"HI!     ;This is now drawn on the main buffer since the Pxl-On( command resets the temporary draw buffer
It also happens that this works for the particle commands as well, so now you can draw particles on back buffers without using complicated techniques.