locked
Help us prioritize your Small Basic 1.1 Known Issues (Bugs) and Feature Ideas!!! RRS feed

  • Question

  • Thank you everyone for your feedback about Small Basic!

    First, you can check out the Microsoft Small Basic 1.1 Release Notes to see what's new in Small Basic!

    We've been gathering known issues and feature ideas from you here: Microsoft Small Basic v1.0: Known Issues.

       

    And now we want your help prioritizing some of these Known Issues and Feature Ideas!

    Please take this survey:

    http://aka.ms/smallbasic1-1feedback

    In the survey, the first page lays out all the Known Issues that we haven't fixed yet. You get to vote for your top 5. This helps us understand what has the biggest impact on what you do!

    In the second page, you can vote for your top 5 feature ideas.

    And if you have another bug or idea that's not on the list, then you can write it in!

    Thank you in advance for your help!

    Small and Basically yours,


    Ed Price, Azure & Power BI Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Tuesday, April 28, 2015 11:49 PM

Answers

  • I did this survey.  Thanks.

    Nonki Takahashi

    Monday, May 11, 2015 7:29 AM
  • Survey taken. Basically asked for:-

    - Local subroutine parameters/variables.

    - More powerful video commands/control.

    - Sound commands.

    Being able to have local parameters/variables would make subroutines far more powerful/neater IMHO. Being able to return a variable to make a subroutine into a function would also be nice.

    To allow developers to work with (non-displayed) virtual screens, and to then copy screen regions around (virtual or displayed). This would allow screen regions to be scrolled, and indeed large (virtual) screens to be created and just a region of them to be displayed on the visible screen. Extremely useful for create large work spaces/game spaces and simply scrolling them around on the visible window.

    Generally more powerful/faster graphics commands.

    Also a simple set of sound commands to create basic synthesized sounds like most basic languages do, so programmers can create simple sound effects rather than relying on WAVs.





    Monday, May 11, 2015 8:48 AM

All replies

  • I did this survey.  Thanks.

    Nonki Takahashi

    Monday, May 11, 2015 7:29 AM
  • Survey taken. Basically asked for:-

    - Local subroutine parameters/variables.

    - More powerful video commands/control.

    - Sound commands.

    Being able to have local parameters/variables would make subroutines far more powerful/neater IMHO. Being able to return a variable to make a subroutine into a function would also be nice.

    To allow developers to work with (non-displayed) virtual screens, and to then copy screen regions around (virtual or displayed). This would allow screen regions to be scrolled, and indeed large (virtual) screens to be created and just a region of them to be displayed on the visible screen. Extremely useful for create large work spaces/game spaces and simply scrolling them around on the visible window.

    Generally more powerful/faster graphics commands.

    Also a simple set of sound commands to create basic synthesized sounds like most basic languages do, so programmers can create simple sound effects rather than relying on WAVs.





    Monday, May 11, 2015 8:48 AM
  • Survey taken. Basically asked for:-

    - Local subroutine parameters/variables.

    - More power video.

    - Sound commands.

    Being able to have local parameters/variables would make subroutines far more powerful/neater IMHO. Being able to return a variable to make a subroutine into a function would also be nice.

    To allow developers to work with (non-displayed) virtual screens, and to then copy screen regions around (virtual or displayed). This would allow screen regions to be scrolled, and indeed large (virtual) screens to be created and just a region of them to be displayed on the visible screen. Extremely useful for create large work spaces/game spaces and simply scrolling them around on the visible window.

    Generally more powerful/faster graphics commands.

    Also a simple set of sound commands to create basic synthesized sounds like most basic languages do, so programmers can create simple sound effects rather than relying on WAVs.




    Thanks again for submitting this!

    Ed Price, Azure & Power BI Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Friday, June 5, 2015 2:42 AM
  • Suggestion: A SandBox File Object

    Description:

    The Sandbox object would be a set of file commands that allow the saving and reading from a file in much the same way that the File object works. The big difference is the sandbox file itself. The Sandbox would only save to a single file. The sandbox file name would match the name of the executable: ProgramName.sbox. The location of the sandbox file would always be in the same folder as the executable (Program.Directory). The sandbox file would be size limited to something small, like 50k. The other file operations would pretend that the sandbox file didn't exist, preventing rename and other operations from turning the sandbox file into something dangerous. Because of its predictable size and location, the sandbox file would be available to the online interpreter.

    Secure, flexible and filling the needs of 99% of file operations that Small Basic is called to perform. Most importantly it would completely and perfectly fulfill the "Seamless Sharing" concept that is such an important part of what makes Small Basic great.

    With the associated discussion

    Tuesday, June 9, 2015 6:08 PM
    Answerer