2025-09-19, 04:21 PM
Don't know if this is the correct place for this post but I'm sure someone will let me know if not.
This post relates to ZX Basic Studio builds 1.0.8702.19933 2023-10-29 and 1.5.9168.37638 2025-02-06 which ,for brevity, I shall call buildA and buildB respectively.
Following the instructions for creating a project from pages 47 to 53 of the "Boriel Basic for ZX Spectrum" book I have the following observations:
(1)
With buildA the Main.bas file appears in the explorer window when it is created,as described in the book.
With buildB it does not. Closing the displayed code by clicking the X next to the "Main.bas" file name removes the code from view and there is no way of re-opening
it from the explorer window (as it isn't listed there). One way to make the file name visible in the explorer window is to close then re-open the project.
(2)
For both buildA and buildB running the book's example code (page 51) without debug results in the expected coloured block of X's.
Running the code under debug with a breakpoint set as shown on page 52, neither build produces the full block (stops after 3 and a bit rows).
Hope this information is useful.
This post relates to ZX Basic Studio builds 1.0.8702.19933 2023-10-29 and 1.5.9168.37638 2025-02-06 which ,for brevity, I shall call buildA and buildB respectively.
Following the instructions for creating a project from pages 47 to 53 of the "Boriel Basic for ZX Spectrum" book I have the following observations:
(1)
With buildA the Main.bas file appears in the explorer window when it is created,as described in the book.
With buildB it does not. Closing the displayed code by clicking the X next to the "Main.bas" file name removes the code from view and there is no way of re-opening
it from the explorer window (as it isn't listed there). One way to make the file name visible in the explorer window is to close then re-open the project.
(2)
For both buildA and buildB running the book's example code (page 51) without debug results in the expected coloured block of X's.
Running the code under debug with a breakpoint set as shown on page 52, neither build produces the full block (stops after 3 and a bit rows).
Hope this information is useful.