I have a keyboard in which I have to press altgr + q in order to type in the / character.

That's not working on 0.1.0c picotron, it seems it doesn't detect the altgr key at all. On the previous version, it worked fine.

Yes, ALTGR stopped working on Picotron 0.1.0c.

In some keyboards characters like "/" , "#" , "{" , "}" , "[" or "]" needs that key to work.

Hope that get fixed soon

I'm certain it will. Until then, I'll keep using the previous version, it works fine there.

I have the same problem. On German Keyboard layout, I need to press AltGr to type "{ }" and "[ ]" which is kinda annoying, because it does not work.
"{" i.e. is "Alt Gr"+7 and if I press them, Picotron captures a label. :/
Edit: Unfortunately I cannot go back on an older version, since I purchased it just today.

That sucks :( but I imagine we'll get a fix in the next few days. It shouldn't take long.

I've done some research, and after creating a small script in Picotron that displays the last keyboard keys pressed, I can see that ALTGR is indeed detected... or something like that. In version 0.1.0b and earlier, it's detected as a combination of CTRL and ALT (As it should be), and then when pressing the key of the alternative character we want to "print", it prints. In version 0.1.0c, ALTGR is still detected as CTRL+ALT, but for some reason, the alternate character key it's not detected. I directly tried using CTRL+ALT instead of ALTGR in both versions (0.1.0b and 0.1.0c), and it works as intended in version 0.1.0b but not in 0.1.0c. The keypress is detected in both versions because it returns the press on both keys (CTRL and ALT) when pressing only a key (ALTGR), but it doesn't detect the functionality of CTRL+ALT to draw the alternate characters in 0.1.0c

If you are interested, this is the simple key testing script

function _draw()
    cls(1)
    print("Press a key:")
    for kp = 0, 255 do 
        if key(kp) then 
           print("Pressed key("..kp..")") 
        end
    end
end

That's very useful! Thanks for sharing!

Problem persists in ver 0.1.0d, seems like calls to readtext() and peektext() don't get characters typed through altgr either.

After reading the post of RazielFireeye, I also did some testing and it seems like when pressing Ctrl and Alt key, Alt gets not recognized, since the shortcut for capturing a label appears to be Ctrl+7 and when I press Alt Gr+7 or Ctrl+Alt+7 it captures a label.
I just installed 0.1.0d.

Same here. Can't use 0.1b because Ctrl+A exit Picotron on a french keyboard and can't use 0.1c or d because AltGr is not recognized. I will wait for a fix.

Same here for me, My laptop use QWERTY french Canadian keyboard set. ALtCar is used to get these usefull []{} in code editor. For now we have to type these caracters as usual in another place on your host OS (like in a worldpad or text entrysomewhere) to copy and past these caracters into code editor, and also do some copy pastes as needed.

Guess I am not the only one having to work around by copying brackets from a different text editor.

It's good to see I'm not the only one with this problem. Was getting a bit worried that I had messed something up on my end.

(Windows x64 - 0.1.0d) I'd like to chime in with the same issue. Turkish-Q and cannot type hash (#) -requires AltGr-, though I can type all the other symbols mentioned here (~, [], {}, / etc.).

Hello everyone. Zep is aware of this bug and is working on it.
https://www.lexaloffle.com/bbs/?pid=144737#p
But we still need a little patience. He also described a possible workaround in the linked post.

v0.1.0e is out and the AltGr is working again. Thank you Zep for your work.

AltGr only seems to work in the code.p64 and notebook.p64 for some reason, seems like it's because they both use the gui_ed library for text input. Terminal still doesn't recognize the characters input through AltGr.

That's strange. The AltGr key on my keyboard works, even in the terminal. Maybe it depends on the host? I use a Linux host computer. Edit: For me it is the delete key that doesn't work in the terminal.

For me it's working even on the terminal

It works and it is fixed in 0.1.0e