rtext_key can still get triggered
- Create a message box
- Click the message box in edit mode and start typing in it
<ctrl-click>an empty part of the canvas
- Keep typing stuff in the message box
Bug: the GUI is no longer in "text" mode even though Pd still treats the message box as being "e_textedfor" (see g_canvas.h). So the GUI forwards each keystroke to Pd as if the GUI were in runmode, and Pd forwards the received keystrokes to the message box's rtext because we are still in editmode.
So, two items:
- the GUI "text" mode should probably filter out
<ctrl-or-cmd>clicks to deal with these cases correctly.
- we should probably figure out if rtext_key is even used anymore. If not, remove it. The problem is that it expects the GUI to be sending it single key codes the whole time, and the new GUI-only editing behavior doesn't do that. Mixing the two can cause one to write data that is different that what the other expects. This apparently can crash rtext_key as it indexes into the char array past the last char.