Bug Tracking

 

SDL Component Suite - Bug Tracking - Release 10.0

In order to make the SDL Suite even better, we installed this public bug tracking page. Please report bugs in the user forum - we'll check your input and add it to this list as soon as the bug has been confirmed. See also: Release History

Date Component Short Description Details Status
Jun-14, 2011 TDendrogram.AutoRange AutoRange should include the width/height of the object captions in order to ensure better readability of the labels. user mail P.M.
2011-05-30
(1)
2011-06-18
May-4, 2011 TGeoMap.SaveLandmarks The SaveLandmarks method does not save the LM ids and the time stamps (1)
2011-05-04
May-4, 2011 Dendrogram / DataTable in contrast to ExportAsASC the method TDataTable.ExportAsCSV does not export the row attributes (which would be useful when exporting the dendrogram data) (1)
2011-09-14
Apr-16, 2011 C++Builder / Thumbnail When using the OnImageRequest event of the class TThumbnail the program cannot be compiled under C++Builder ("E2015 Ambiguity between TBitmap and Windows::TBitmap") user mail C.V.
2011-04-16

2011-04-19
see Technotes
Apr-6, 2011 NumLab Numlab displays 0°59'60.00" if the Value property is set to 0.999999.
Remark by HL: this bug is actually a bug of the function DegreeToStr in the unit SDL_Math1.
(1)
2011-04-14
Dec-03, 2010 GeoMap CalcExtentsAndResolution calculates wrong map resolution if the map spans more than 180 degrees longitude - (1)
2011-01-04
Jul-1, 2010 Installer The installer destroys an existing library path if the path is too long. This bug is very rarely experienced, it probably depends on the Windows environment settings. user mail E.L./M.W.
2010-07-01
open
Jul-1, 2010 Plot3D The component raises an exception if one of the axes is perpenticular to the viewing plane. (1)
2010-07-03
Jun-20, 2010 RChart If the property Scale1X.RangeHigh is changed during design time while the property Isometric is TRUE, the vertical axis does not adjust automatically to maintain the isometric mode. - open
Jun-19, 2010 NumIO2 Wenn ich zur Design-Zeit den Wert RangeLow auf 0 setze (Format=iFloat, RangeHigh=200), ist dieser zur Laufzeit auf -1.7E308. Setze ich den Wert zur Design-Zeit z.B. auf -1, +1 oder +1E-5 funktioniert es wie erwartet. user mail F.S.
2010-06-19
() - see 2)
2011-07-13
Jun-18, 2010 NumIO2 The property NumIO->RangeLow will not be saved to the dfm file after changing by the designer. () - see 2)
2011-07-13

 


1) The new code will be available with the next minor release of the SDL Suite
2) This is a bug of some of the older Borland/CodeGear compilers