-
I followed your YouTube video below and successfully setup the NextBASIC extension in Visual Studio Code.
[nextbasic vscode extension - brief intro](https://t.co/zXPMPy7ZGf)
But I also found ano…
-
I have installed the VSCode extension and set up the support programs and paths, whenever I attempt to 'run with CSpect' in VSCode it just goes to the Next main menu.
I have tried running the index…
-
Hi Remy,
I am running Cspect 2.12.36 on latest ubuntu 20.04 (fully patched) and latest vscode (1.50.1). Latest mono installed as i use it for other things. Git cloned and compiled hdfmonkey and su…
-
v1.11.7
There are a few parsing bugs that pass OK into RunInCSpect, but are picked up as errors in Export (and cause export to fail).
Examples:
%CODE:
ERROR$:
IF %SPRITE AT (j,1)>127 …
-
Repro1:
9000 DEFPROC Init(): RUN AT %3: BORDER %0: PAPER %0: BRIGHT %1: INK %7: CLS: PALETTE OVER %0: LAYER %2,%0: LAYER %0: SPRITE CLEAR: SPRITE BORDER %1
9001 PROC LoadFont(): PRINT "LOADING METEO…
-
On prior versions, launching CSpect used kill any current mono instance before launching.
On new plugin, this doens't happen and I can inadvertently get a few CSpect running in parallel, slowing each…
-
Hi Remy! How are you? I'm using your vscode extension for nextbasic and I think that I've found a little bug with @ used as label. When I use it, for example:
10 LOAD "sprites2.spr" BANK 12: SPRIT…
-
v1.11.7
BANK %27 DPOKE %y
-
v1.11.3
RunInCSpect option works fine, but Export to binary .bas macro (using the same VSCode .txt file) renumbers the output, including any references to GOTO/SUB jump destinations (which then break…
-
v1.11.4 nonsense in BASIC
%d=%d-(IN 57342 &1)+(IN 57342 &2>>1)
Also fails:
%d=%d-(IN 57342 &1)
Also fails:
%d=%(IN 57342)
Removing the brackets, or re-editing the line in the editor and …