|
Post by visionmercer on Sept 28, 2023 19:53:26 GMT
qb64 works best with a standard us keyboard setup, I cant use ^ and ~ on my windows computer that has a danish keyboard.
|
|
|
Post by elephiant on Sept 29, 2023 17:49:45 GMT
Statesman has suggested we check your font setting, are you on default setting, not using an monospaced font of your own specification I use default and looks like this: View AttachmentIDE > Options > Display no monospaced font nor [ ] box checked I'm using the default settings
|
|
|
Post by elephiant on Sept 29, 2023 18:12:43 GMT
I've not come across this and it certainly looks like bplus has done a pretty thorough job trying to get to the bottom of it using the *standard* approaches. With that said, there is another thing that could potentially be looked at here... given that the QB64 application itself is a compiled QB64 application, one could try to reproduce what *might* be happening by writing a program that reads keyboard entry in the same manner as the QB64 ide... meaning does `Inkey$` (https://qb64.com/wiki/INKEY$), as an example, work as one would expect in your own program? You also mention that VSCode is working without issue; so I'll share that in my own personal usage of QB64 I actually utilize VSCode nearly 100% of the time using github.com/QB64Official/vscode/tree/main/releasesThe QB64 VSCode extension isn't published in the extensions *store*, but you can download the latest .vsix to install it manually. Provides for some code formatting, error checking and has full access to the help directly within VSCode - and you can press F5 to build/run. Additionally, can jump to method as well as a host of other *free* features that come along with being in VSCode. I recognize that this doesn't solve the problem you are having within the QB64 IDE, but it might be a way to have what could potentially be a *better* experience given that you already have experience using VSCode (as mentioned above). Thanks for your comment. When I try to read input with INKEY$ I see the same problem. The same characters don't appear on the screen. I tried the VSCode extension which seems to install fine, but when I press F5 it says "You don't have an extension for debugging QB64. Should we find a qb64 extension in the Marketplace?". I restarted vscode after adding the extension and the extension is listed in vscode as installed.
|
|
|
Post by elephiant on Sept 30, 2023 14:34:30 GMT
dualbrain visionmercer bplus I only tried "United States International" keyboard, not "United States", but did try it just now and with the "United States" keyboard it seems to work fine. Should have tried that earlier . Thanks very much for all your help.
|
|
|
Post by bplus on Sept 30, 2023 17:31:43 GMT
dualbrain visionmercer bplus I only tried "United States International" keyboard, not "United States", but did try it just now and with the "United States" keyboard it seems to work fine. Should have tried that earlier . Thanks very much for all your help. OMG! I didn't know there were two different US settings. I'm sorry Fellippe mentioned something like that at Discord (and visionmercer here?) but I thought that was something we had checked already. Dang! Thank all that's good you found this! I will hopefully remember this for future. Not "US International", straight "US" Man thanks for hanging in there and persisting and reporting back! Honestly I had given up. The littlest things can really hang things up! Persistence pays!
|
|
|
Post by Steve on Oct 26, 2023 12:59:24 GMT
You may also need _CONTROLCHR OFF if you're trying to print the lower value ASCII codes.
|
|