BUG TRACKER - List of known bugs

Please report bugs

BUG TRACKER - List of known bugs

Postby berndnoetscher » Tue Mar 24, 2009 9:56 am

List of known bugs:
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V1.89f: "Open ... For Output"

Postby berndnoetscher » Fri Apr 24, 2009 9:01 am

Open "IP_Settings.inc" For Output As #fh writes to C:\, not as expected the current directory (App.Path). Even when running everything from D:\Program\KBasic\Projects\.....
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V1.89f: "Str(number As Short)"

Postby berndnoetscher » Fri Apr 24, 2009 9:01 am

Writing Str(number As Short) writes as float with 6 decimals, not as I expected as Int. Resolved by using Format(number, "#")
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

Re: BUG TRACKER - List of known bugs

Postby berndnoetscher » Fri Apr 24, 2009 9:02 am

if (1) xmax is readed and ymax readed
if (2) xmax and ymax readed

Code: Select all
Private Sub CommandButton1_OnEvent()

dim i,j as integer

dim xmax , ymax as string '(1)

'dim xmax as string (2)

'dim ymax as string (2)

dim od as opendialog

dim s as string =od.getfile("Attention","d:\Program files\kbasic\examples\npl.kbasic_project","Nombres placés (*.npl)")

me.text=s

If s Then

Open s For Input As #1

input #1,xmax

textbox1.text=xmax

input #1,ymax

textbox2.text= ymax

End If

End Sub
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V1.89g: Key event modifiers are not recognised

Postby berndnoetscher » Mon May 04, 2009 7:50 am

I ran the program events_kbasic.project from example on Vista using a dell laptop
The modifiers (alt shift and command) are not recognised are always reported as false

I tried the example events project "events_kbasic.project".

When I press command, alt and shift while pressing a key I always get a "FALSE" printout for the shift keys.

I found the same problem in a program I wrote using the trial version.

I am using vista on dell xps m1330 laptop.
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V1.89g: extra 13 space characters in print #1, "Hel

Postby berndnoetscher » Tue May 05, 2009 9:06 am

OPTION OLDBASIC
open "MYTEST.TXT" for output AS #1
print #1, "Hello"
close #1

. . . it outputs an extra 13 space characters before the Hello. This also happens if I print# a variable rather than a literal.
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V1.89g: compiler error due to optimization

Postby berndnoetscher » Mon May 11, 2009 10:07 am

Compilation error when a control is used as variable outside of a form, but only method calls (faulty instructions are created), properties are working...

It was an error in the compiler and optimization for parsing variables didn't work all the time.

Code: Select all
frm_Main.Udp1.WriteData(UDPString)
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V1.89g: CHR-> CSTRING prefering

Postby berndnoetscher » Mon May 11, 2009 10:28 am

Due to CSTRING prefering of CHR, changed to STRING prefering

s2= chr$(0)+chr$(b)+chr$(v)+chr$(r) chr$(0) is in s2
s2=chr$(b)+chr$(v)+chr$(r)+ chr$(0) chr$(0) is not in s2
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V.189(m): Form Name on the Properties Window doesn'

Postby berndnoetscher » Fri Jun 12, 2009 12:29 pm

Form Name on the Properties Window doesn't properly update the name of the form in the Project Window when it is changed.

One of the things that happens because of this incongruity is that events created after the name change are given names that match the new name instead of being given the generic Form syntax.
For example, if I change the name of frmMain to frmSub in the Property Window, instead of a

Form_OnOpen() event, it'll create a
frmSub_OnOpen() event, which will never run.
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

FIXED IN V1.89k: Remove (Dummy, 9,3)

Postby berndnoetscher » Mon Jul 06, 2009 2:30 pm

Remove and some other non-returning string procedures don't work.

Code: Select all
Dim Dummy as String
Dummy = "This is not an empty string"
Print Dummy;" ";Len(Dummy)
Remove (Dummy, 9,3)
Print Dummy;" ";Len(Dummy)


Results in both cases This is not an empty string 27
berndnoetscher
Site Admin
 
Posts: 1059
Joined: Tue Sep 25, 2007 9:37 am

Next

Return to Bug-Reports

cron