![]() |
The quotation marks and the apostrophe - Printable Version +- QB64 Phoenix Edition (https://qb64phoenix.com/forum) +-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1) +--- Forum: Code and Stuff (https://qb64phoenix.com/forum/forumdisplay.php?fid=3) +---- Forum: Help Me! (https://qb64phoenix.com/forum/forumdisplay.php?fid=10) +---- Thread: The quotation marks and the apostrophe (/showthread.php?tid=3523) |
The quotation marks and the apostrophe - Marco Kurvers - 03-08-2025 In the editor, I can't type the quotation marks for strings and I can't type the apostrophe for comments. I must type the ascii codes 34 and 39. I can also hold the keys, but then I get more of these and I must delete this every time until I finally have one. My question is, is this problem only with me? RE: The quotation marks and the apostrophe - SMcNeill - 03-08-2025 I've never heard of the issue before. Is it a US Keyboard or one with an unusual keyboard layout perhaps? Which version of QB64PE are you using, and what OS is it for? RE: The quotation marks and the apostrophe - Marco Kurvers - 03-08-2025 I have a QB64 Phoenix Edition 3.13.1 (x64) version. My keyboard is an US Logitech and I use Windows 10 Home. I must use the shift and the apostrophe keys for the quotation marks. I can try to use a new version of QB64PE. RE: The quotation marks and the apostrophe - visionmercer - 03-10-2025 I saw the same problem a few years ago, the problem was the keyboard layout in windows was set to US International instead of just US. RE: The quotation marks and the apostrophe - mdijkens - 03-10-2025 A very common keyboard setting for dutch is to be able to type quotes and then an i or e to get the dots on the letter. Not sure if you have that turned on in windows? I've never used it, but I assume if you have that, you might also use that in the QB64pe IDE by typing ' space or " space RE: The quotation marks and the apostrophe - SMcNeill - 03-10-2025 (Today, 08:48 AM)visionmercer Wrote: I saw the same problem a few years ago, the problem was the keyboard layout in windows was set to US International instead of just US. That's why I mentioned: Quote:unusual keyboard layout perhaps? I've seen the same issue in the past with the US International layout. I'm wondering if that may be what the issue is in this case. |