VSCode = Visual Studio Code (Editor ++) with QB64 extension - Printable Version +- QB64 Phoenix Edition (https://staging.qb64phoenix.com) +-- Forum: Chatting and Socializing (https://staging.qb64phoenix.com/forumdisplay.php?fid=11) +--- Forum: General Discussion (https://staging.qb64phoenix.com/forumdisplay.php?fid=2) +--- Thread: VSCode = Visual Studio Code (Editor ++) with QB64 extension (/showthread.php?tid=1639) Pages:
1
2
|
RE: VSCode = Visual Studio Code (Editor ++) with QB64 extension - SMcNeill - 04-25-2023 (04-25-2023, 03:24 AM)bplus Wrote: @grymmjack thanks for soul bearing reply. Doing those vid's for yourself firstly sure explains allot. My dad passed from Alzhiemers/Parkensons 2014 and going through same now with mom at 92, she does crossword puzzles to help keep mind fit but nothing sticks in short term memory, hard to get use to...
RE: VSCode = Visual Studio Code (Editor ++) with QB64 extension - bplus - 04-25-2023 OK it's in. Funny I tried that very file before and no luck, Now I have to tell it where QB64 is, where? Update: found it RE: VSCode = Visual Studio Code (Editor ++) with QB64 extension - bplus - 04-25-2023 Under Extensions here But I had to copy QB64pe.exe rename it QB64.exe in another Folder and then paste that exe back into QB64pe Folder and I could finally run some code. BTW Thankyou Steve, your Quick Guide had me trying again. Oh yeah, I also had to fill a space in Folder name with a - hyphen. RE: VSCode = Visual Studio Code (Editor ++) with QB64 extension - SMcNeill - 04-25-2023 I think you can put it in single quotes or quotes if it has a space, a lot like SHELL commands. RE: VSCode = Visual Studio Code (Editor ++) with QB64 extension - grymmjack - 04-25-2023 (04-25-2023, 03:24 AM)bplus Wrote: @grymmjack thanks for soul bearing reply. Doing those vid's for yourself firstly sure explains allot. My dad passed from Alzhiemers/Parkensons 2014 and going through same now with mom at 92, she does crossword puzzles to help keep mind fit but nothing sticks in short term memory, hard to get use to... Hey @bplus you are welcome. Lint and Linting is simply the process of checking syntax for validity. This happens every line in QB64 IDE. You get the errors at the bottom when linting fails. The "linting" is the common term that other languages use too. Check this link on Wikipedia for more information. OK got you, I will help you with that, video will come in a bit! Glad to help! RE: VSCode = Visual Studio Code (Editor ++) with QB64 extension - grymmjack - 04-25-2023 @smcneill Exactly! You guys got it. Yep, you have to copy the qb64pe.exe to qb64.exe right now - but @durus is working on a change that let's us specify the actual compiler file itself in the latest development branch for qb64 vscode extension - but yeah, recommend you just stick with this latest one you installed, and you can freely change the \ back slashes to forward slashes / and powershell might be ok for you. Otherwise, set your default terminal to CMD. CTRL+SHIFT+P, type "terminal default", choose CMD.exe from the list, with arrow keys, then hit ENTER. Hope that helps! RE: VSCode = Visual Studio Code (Editor ++) with QB64 extension - mnrvovrfc - 05-12-2023 Somebody is complaining about the question mark automagically not becoming "PRINT" (facepalm) Also remember that BASIC, like Pascal, is a programming language that disregards letter case. Not like Python where "Number" and "number" could be two different variables. Might need an option apart from "How keywords are formatted" related to names of variables and subprograms. There are other subtleties such as single-line "IF... THEN" against "IF... THEN... ELSEIF... ELSE... ENDIF", this could be hard to get right. For example, Kate always boldfaces the two letters that come right after "THEN" if anything follows "THEN". It's a strange quirk. Good work on the VSCode template but that program is something I'm not interested in. (thumbs up) |