DevLabs > DevLabs Forums > Small Basic > Small Basic 0.7 BUGs
Ask a questionAsk a question
 

StickySmall Basic 0.7 BUGs

  • Saturday, October 24, 2009 11:18 AMFEHÉR András Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The small basic version 0.7 still does not write '*' on Hungarian keyboard. Insted of changing the size of letters!
    (AltGr -)

All Replies

  • Saturday, October 24, 2009 7:28 PMVijaye RajiMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    What other characters are on the key for '*'?
  • Monday, October 26, 2009 12:13 PMFEHÉR András Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    No other button for '*'.
    keyboard layout
    On Hungarian keyboard how can change the letter size bigger? AltGr Shift Ó (+) does not change!

  • Monday, October 26, 2009 3:49 PMVijaye RajiMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hmm... the characters are all so differently placed on this keyboard.  I'll take a note to use a different mechanism than ScanCodes for the text zoom feature. 

    Have you tried AltGr Shift 7 (=) for zoom up?
  • Monday, October 26, 2009 4:16 PMFEHÉR András Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Sorry, the right combination for growing is: AltGr Shift Ó on HUNGARIAN keyboard. It is working now.

  • Sunday, November 01, 2009 2:19 AMJason Jacques Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Some times I want to be told I'm stupid and wrong - this is one of them:

        TextWindow.ForegroundColor = "red
        TextWindow.WriteLine("This program should not run.")

    Is the fact that this code actually works correctly intentional, or just an happy side effect of the way your parsing engine works?

    Maybe this is a one of those rare bugs that could legitimately be called a 'feature'!

    Best,

    Jason.
  • Monday, November 02, 2009 1:16 AMRushworksAnswererUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    It also seems you don't need commas between parameter arguments either.

    Image = ImageList.LoadImage(Program.Directory + "\AnyImage.png")
    GraphicsWindow.DrawResizedImage(Image 0 0 GraphicsWindow.Width * 0.2 GraphicsWindow.Height)
  • Monday, November 02, 2009 9:26 AMFediachov Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    GraphicsWindow.GetPixel - still does not work
  • Monday, November 02, 2009 2:31 PMwillTthrill Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Has Code
    More specifically, GetPixel does work with the shapes added via GraphicsWindow.AddShape (Ellipse, Rectangle, etc). It does not seem to work in three ways:

    • The background returns black (#000000) when nothing has been drawn on it, even though it look white.
    • When used in conjunction with Shapes.Move, the pixel colour is not returned at all
    • Some shapes seem to be shaded around the edges or something... the GetPixel method returns slightly different values from their stated colours around their edges
    Here is a sample programme that shows some of the working and broken parts (take out the background to see how #000000 is returned even with a "white" background):

    GraphicsWindow.Show()
    'background:
    GraphicsWindow.BrushColor="White"
    GraphicsWindow.FillRectangle(0,0,640,450)
    'shapes:
    GraphicsWindow.BrushColor="Blue"
    GraphicsWindow.PenColor="Blue"
    ball=Shapes.AddEllipse(20,20)
    Shapes.Move(ball,300,100)
    GraphicsWindow.BrushColor="Black"
    GraphicsWindow.FillEllipse(100,100,20,20)
    GraphicsWindow.BrushColor="Red"
    GraphicsWindow.FillEllipse(200,100,20,20)
    
    While ("True")
      x= GraphicsWindow.MouseX
      y= GraphicsWindow.MouseY
      c= GraphicsWindow.GetPixel(x,y)
      GraphicsWindow.Title = c
    EndWhile
    

    GetPixel is a really handy command for teaching programming and I hope it gets fixed. When teaching kids without a good background in geometry, commands like GetPixel make it much easier to make simple games that require collisions - you can just check the colour of the pixel around the player to see if s/he's collided with anything.
    • Edited bywillTthrill Monday, November 02, 2009 2:31 PMformatting
    •  
  • Saturday, November 07, 2009 4:38 PMFremyCompanyAnswererUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Some bugs I noticed :
    * New window still opened too far when we open many documents. The winPos param should be reset when we close a document and at least more quickly, because we then need to move our codes windows, because they dispear after the sidebar.
    * Extensions are not added as reference when exported to VB (causing 'Unknown reference' problems)

    Exporting to VB is cool ! I think it's a good way to help beginners to switch to VB smootly.
    Fremy - Developer in VB.NET, C# and JScript ... - Feel free to try my extension
  • Thursday, November 12, 2009 9:00 PMDavey-Wavey Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Has Code
    Is this a bug in the shapes object or am I misunderstanding something? 

    GraphicsWindow.Width=800
    GraphicsWindow.Height=600
    
    ' get an 800x600 image and display it
    map1 = ImageList.LoadImage(Program.Directory + "\800x600.jpg")
    GraphicsWindow.DrawImage (map1, 0,0)
    
    ' put the above image into a shape object and display it
    map2 = Shapes.AddImage(map1)
    Shapes.Move(map2,0,0)
    
    


    In the above, map1 gets drawn at the expected 800x600, but map2 only takes up a quarter of the window at 400x300. What's going on here?

    BTW, the same happens if I just directly do a map2=shapes.addimage(program.directory + "800x600.jpg")