Lazarus 1.6.0 release notes

From Lazarus wiki
Revision as of 01:13, 1 April 2015 by Martin (talk | contribs) (Components)

Template:Lazarus 1.6.0 release notes

Lazarus 1.6.0 is not yet released. This page is under construction!

Statistics:

  1. commits: xxx
  2. log: svn log -r xxxx:xxxx
  3. resolved bug tracker issues: xxx

LCL Interfaces Changes

LCL Changes

IDE Interfaces Changes

  • Quick fix for fpc message Local variable "i" does not seem to be initialized inserts an assignment.

IDE Changes

  • Editor
    • Basic multi-caret mode
    • Option for multi-line notebook-tabs
    • line-number part of gutter now allows to select the current line, or several lines.
  • Project
    • Additions and Overrides are now added as last. Formerly they were added after the inherited and before the custom compiler options.
  • Messages Window
    • The IDE now warns when there are duplicate units or include files in packages.

Components

SynMemo is now Deprecated

  • SynMemo was deprecated.
Any code referring to SynMemo will now give a warning about this.
  • SynMemo was also removed from the component palette.
However SynMemo is still a registered component, and if you open any project already containing a SynMemo it will load correctly.
If you must have an IDE with SynMemo on the component palette, you can compile the IDE with WithSynMemo defined. This is temporary, and will be removed at some point after the release.

SynMemo was nearly identical to SynEdit (except it did publish less properties).

It only featured 2 extra method:

   function CharIndexToRowCol(Index: integer): TPoint;   
   function RowColToCharIndex(RowCol: TPoint): integer;  

Those are now available in SynEdit. However with a strong warning

   experimental; deprecated 'SynMemo compatibility - very slow / SynEdit operates on x/y';

It is highly recommended not to use them. The calculation in those methods was always done without taking in account trailing spaces (if trim trailing spaces was active). This may have lead to wrong results.

A common use case for those methods was apparently:

- Get the caret position as CharIndex.
- Insert some text
- Add the text length to the CharIndex
- Set the caret position from the CharIndex

If setting the text changed trailing spaces (e.g. text was appended at the end of line, behind some trailing spaces, which then would not be trailing any more) then the calculation would not be correct.

Yet if the 2 methods would include trailing spaces, it could equally go wrong. If between getting the caret position, and restoring it any trailing spaces where trimmed, then the restore is wrong.

For this reason, and for the fact that they are extremely inefficient (slow) their use is not recommended.


To archive caret adjustment in SynEdit, use InsertTextAtCaret, TextBetweenPointsEx or SetTextBetweenPoints, which all have the option of adjusting the caret.

Changes affecting compatibility

LCL incompatibilities

IDE incompatibilities

Previous release notes