Small Basic Prime 1.1.5

A Small Basic development environment (IDE) with debugger.

SB-Prime.zip
 
 
 
 
 
5 Star
(5)
965 times
Add to favorites
Applications
9/20/2018
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Debugging
    2 Posts | Last post January 01, 2018
    • Once again a superior piece of work.
      Thanks for responding so timely. I knew how to use breakpoints etc and do appreciate the PDF explanation. I should have been more clear. I wanted to be able to have the new ide and the program windows up at same time. When I click resizing on top menu, my IDE window went to a 2 inch ribbon with just upper left showing. So I was flipping back and forth between IDE and my program graphics window. When I manually resize from the tiny ribbon on the IDE I was able to see both IDE and Application window at same time and interact accordingly. Works GREAT!
      I have also found what I believe to be the main forum thread on the IDE and will ask any further questions there.
      Once again thanks for the response and the new IDE. 
    • Ah I see.
      I also get the 'small window thing' sometimes which I just drag to the left to go 'half screen' in Windows 10, but usually I run the IDE at about 60% my display width with full height (not full screen and intellisense minimised).
      When debuggging, I put a pause after the GW is created and then position it somewhere not overlapping IDE or at least partly visible.  I experimented a bit using transparency on the IDE, but other issues with that cause more confusion than it solves.
  • Debug
    3 Posts | Last post December 11, 2017
    • This IDE looks great!
      When debugging I cannot interact with the visuals of the program. In other words, if debugging Tic Tac Toe, I cannot enter an "X" or an "O" to see how the program reacts. Is it not able to do that or have I missed something.
    • Hi,
      
      Debugging allows the program to pause to see values and the path the program takes etc, so when it is paused you cannot interact with it (it is paused).
      
      When it is not paused (running) you can interact as normal with it.
      
      You can put break points so when the code reaches a break point it pauses.
      
      When the program is paused you can resume running (Run), or step to the next statement (Step), with step vairiants to to step out or over subroutines.
      
      When the program is paused a yellow background highlights the line it is paused at.  When it is not paused (running) there is no yellow highlight line.
      
      One last point, make sure you have the recent version, although debugging has worked like described from the start.
      
    • To help I wrote a short document describing how to debug.  The following is a link to it.  The link may disappear in the future if I do something more formal with help.
      
      [http://litdev.co.uk/forum/HowToDebug.pdf]