Recent

Author Topic: Lazarus Release Candidate 2 of 2.2.0  (Read 18373 times)

mattias

  • Administrator
  • Full Member
  • *
  • Posts: 176
    • http://www.lazarus.freepascal.org
Lazarus Release Candidate 2 of 2.2.0
« on: November 04, 2021, 07:27:47 pm »
The Lazarus team is glad to announce the second release candidate of Lazarus 2.2.

This release was built with FPC 3.2.2.

Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_2.2.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.2.2

Here is the list of fixes for Lazarus 2.2.x:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_2_2

The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 2.2RC2" directory.

Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#2_2_0RC2

Minimum requirements:

Windows:
   2k, XP, Vista, 7, 8, 8.1 and 10, 32 or 64bit.

FreeBSD/Linux:
   gtk 2.8 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.

Mac OS X:
   Cocoa (64bit) 10.12 to 11.4, Carbon (32bit) 10.5 to 10.14, qt and
   qt5 (32 or 64bit).

The gitlab page:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/lazarus_2_2_0_RC2

Last trunk svn revision was r65398.

For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:ftp://ftp.freepascal.org/pub/lazarus/releases/

== Why should everybody (including you) test the release candidate? ==

In the past weeks the Lazarus team has stabilized the 2.2 fixes branch. The resulting 2.2RC2 is now stable enough to be used by anyone for test purposes.

However many of the fixes and new features that were committed since the release of 2.0 required changes to the code of existing features too. While we have tested those ourselves, there may still be problems that only occur with very specific configurations or one project in a million.

Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we cannot fix it.

Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 2.2.x releases. So it may be, that we cannot merge the fix you require. And then you will miss out on all the new features.

== How to test ==

Download and install the 2.2 RC2.
- On Windows you can install as a 2ndary install, that will not affect your current install:
http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus
- On other platforms, if you install to a new location you need to use --primary-config-path

In either case you should make backups. (including your primary config)

Open your project in the current Lazarus (2.0.x), and use "Publish Project" from the project menu. This creates a clean copy of your project.

You can then open that copy in the RC2. Please test:
- If you can edit forms in the designer
   - rename components / change properties in Object inspector / Add new events
   - Add components to form / Move components on form
   - Frames, if you use them
- If you can navigate the source code (e.g. jump to implementation)
- Auto completion in source code
- Compile, debug and run
- Anything else you use in your daily work

BSaidus

  • Sr. Member
  • ****
  • Posts: 396
  • lazarus 1.8.4 Win8.1 / cross FreeBSD
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #1 on: November 07, 2021, 08:06:46 am »
Hello.
I recompiled Lazarus with anchodocking support, then go to codeexplorer and try to jump to different places, units ( clicked on go to unit emplacement ) but it do not do that.
  There is many things not working ( jumping) from code explorer to editor.


Thanks
lazarus 1.8.4 Win8.1 / cross FreeBSD
dhukmucmur vernadh!

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3996
  • I like bugs.
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #2 on: November 07, 2021, 10:15:50 am »
I recompiled Lazarus with anchodocking support, then go to codeexplorer and try to jump to different places, units ( clicked on go to unit emplacement ) but it do not do that.
  There is many things not working ( jumping) from code explorer to editor.
It works here.
It must depend on the code. Something confuses the parser. Do Codetools work otherwise with the unit you tested?
Anchodocking should have no effect on CodeExplorer synchronization. Can you please test without it.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

BSaidus

  • Sr. Member
  • ****
  • Posts: 396
  • lazarus 1.8.4 Win8.1 / cross FreeBSD
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #3 on: November 07, 2021, 01:21:54 pm »
It works here.
It must depend on the code. Something confuses the parser. Do Codetools work otherwise with the unit you tested?
Anchodocking should have no effect on CodeExplorer synchronization. Can you please test without it.
Frankly,I tested a new non saved project.
I'll test later and give more infos.


[Edited to fix quote tags]
« Last Edit: November 07, 2021, 11:29:57 pm by trev »
lazarus 1.8.4 Win8.1 / cross FreeBSD
dhukmucmur vernadh!

BSaidus

  • Sr. Member
  • ****
  • Posts: 396
  • lazarus 1.8.4 Win8.1 / cross FreeBSD
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #4 on: November 08, 2021, 10:44:45 am »
It works well, the code explorer synchronize well with the code.
Tested on saved project.
PS: I used fpcupdeluxe to compile the fixes branche of Lazarus with fpc 3.2.2.
lazarus 1.8.4 Win8.1 / cross FreeBSD
dhukmucmur vernadh!

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3996
  • I like bugs.
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #5 on: November 08, 2021, 01:48:50 pm »
It works well, the code explorer synchronize well with the code.
Tested on saved project.
I guess it should work on non-saved project, too. It may not be important because any code where you want to use CodeExplorer is part of some project or package.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

dbannon

  • Hero Member
  • *****
  • Posts: 1674
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #6 on: November 09, 2021, 03:33:43 am »
The current rc2 (and trunk) again have some misspelling of the word "occurred".  All in string literals so, no big deal to fix.

Code: [Select]
grep -rw occured lazarus-lazarus_2_2_0_RC2 [enter]
I reported a number of these some time ago and they were fixed so have to assume they have crept back in again over time.  Last time, my patch was not very well received so will just report for someone else to make a better patch.

I report it because occured is on Debian's hit list and it gets reported by lintian (in pedantic mode).

EDIT : I should have mentioned than most of the "occured" occur in msgid of po files.

Davo
« Last Edit: November 09, 2021, 06:47:55 am by dbannon »
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

dsiders

  • Hero Member
  • *****
  • Posts: 534
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #7 on: November 09, 2021, 09:00:05 pm »
The current rc2 (and trunk) again have some misspelling of the word "occurred".  All in string literals so, no big deal to fix.

Code: [Select]
grep -rw occured lazarus-lazarus_2_2_0_RC2 [enter]
I reported a number of these some time ago and they were fixed so have to assume they have crept back in again over time.  Last time, my patch was not very well received so will just report for someone else to make a better patch.

I report it because occured is on Debian's hit list and it gets reported by lintian (in pedantic mode).

EDIT : I should have mentioned than most of the "occured" occur in msgid of po files.

Davo

In Lazarus: If you look at the matches, you'll see that they are commented entries in the .po files with the following line being the correction.

In FPC: There are source comments with the spelling error too. They need to be reported to the FPC issues tracker.

Lazarus 2.0.12, 2.2.0-RC2, 2.3.0 (Git) / FPC 3.2.0, 3.2.2 / x86-win64 / Windows 8.1

dbannon

  • Hero Member
  • *****
  • Posts: 1674
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #8 on: November 10, 2021, 12:22:55 am »
re: "occured"

In Lazarus: If you look at the matches, you'll see that they are commented entries in the .po files with the following line being the correction.
It does not matter to Debian lintian why they are there or why they are there. It just spits them out if it finds them anywhere.

In FPC: There are source comments with the spelling error too. They need to be reported to the FPC issues tracker.

As mentioned, my previous bug report including a patch was unacceptable. Cannot see how i can do any better this time.

Davo

edit: sorry, that sounded very penchant. Having a bad time at home at present, will try harder.
« Last Edit: November 10, 2021, 12:36:04 am by dbannon »
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

dsiders

  • Hero Member
  • *****
  • Posts: 534
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #9 on: November 10, 2021, 07:13:48 am »
re: "occured"

In Lazarus: If you look at the matches, you'll see that they are commented entries in the .po files with the following line being the correction.
It does not matter to Debian lintian why they are there or why they are there. It just spits them out if it finds them anywhere.

In FPC: There are source comments with the spelling error too. They need to be reported to the FPC issues tracker.

As mentioned, my previous bug report including a patch was unacceptable. Cannot see how i can do any better this time.

Davo

edit: sorry, that sounded very penchant. Having a bad time at home at present, will try harder.

 I looked for a previous issue to see its disposition. I could not find one. Issue with patch: https://gitlab.com/freepascal.org/fpc/source/-/issues/39434.
Lazarus 2.0.12, 2.2.0-RC2, 2.3.0 (Git) / FPC 3.2.0, 3.2.2 / x86-win64 / Windows 8.1

dbannon

  • Hero Member
  • *****
  • Posts: 1674
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #10 on: November 10, 2021, 08:11:18 am »
Thanks Don. 

Similar Previous Lazarus Issues -

https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/38977

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

dsiders

  • Hero Member
  • *****
  • Posts: 534
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #11 on: November 10, 2021, 09:13:06 am »
re: "occured"

In Lazarus: If you look at the matches, you'll see that they are commented entries in the .po files with the following line being the correction.
It does not matter to Debian lintian why they are there or why they are there. It just spits them out if it finds them anywhere.

In FPC: There are source comments with the spelling error too. They need to be reported to the FPC issues tracker.

As mentioned, my previous bug report including a patch was unacceptable. Cannot see how i can do any better this time.

Davo

edit: sorry, that sounded very penchant. Having a bad time at home at present, will try harder.

 I looked for a previous issue to see its disposition. I could not find one. Issue with patch: https://gitlab.com/freepascal.org/fpc/source/-/issues/39434.

And removes the commented lines from the .po files. Issue: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39460
Lazarus 2.0.12, 2.2.0-RC2, 2.3.0 (Git) / FPC 3.2.0, 3.2.2 / x86-win64 / Windows 8.1

Ñuño_Martínez

  • Hero Member
  • *****
  • Posts: 1141
    • Burdjia
Re: Lazarus Release Candidate 2 of 2.2.0
« Reply #12 on: November 10, 2021, 12:56:36 pm »
Just found an issue with version 2.0.12 that is related with this issue.

The thing is if I try to "Open with Lazarus" from a file explorer (i.e. double click either on Windows' Explorer or Xubuntu's Thunar) it just opens Lazarus IDE with an empty project (or the previous project, it depends on Lazarus documentation).

The link I've post before fixes it using lazarus-ide instead of lazarus, and that works also in the explorer, but installation configures the file explorer to use lazarus so it seems as it's broken.

I've look in the fixes list but I can't see any mention to this.  Does this version changed something about this?
Are you interested in game programming? Join the Pascal Game Development community!
Also visit the Game Development Portal

robert rozee

  • New Member
  • *
  • Posts: 42
height of Courier New 12pt font not right (windows, Lazarus 2.2.0 RC2)
« Reply #13 on: November 11, 2021, 02:37:58 pm »
would someone running windows (i tested with windows XP VM) please compile and run the attached test with Lazarus 2.2.0 RC2. if everything is correct, then BOTH lines of text should be underlined, and when Button1 is clicked all 4 numbers displayed should be 19.

in XP at least, if underline is set in the font style of a TLabel whose font is 12pt Courier New, then the label autosizes wrongly, 1 pixel short. worse still, this error is reflected in the value returned by TLabel.Canvas.TextHeight().

now it could be that fault lies in the font itself - whereby the underline is defined as sitting outside the character cell, but i'm not sure how to check this. the problem doesn't appear to manifest on sizes other than 12pt. i have only checked with Courier New, and only the version supplied with XP.

when i transplanted the offending font file (cour.ttf) onto a linux machine (lazarus 2.0.12), the odd behaviour partially followed - autosize was wrong, but by 2 pixels this time (expected behaviour with 2.0.12), but the TextHeight() values were correct (at 19).


cheers,
rob   :-)

wp

  • Hero Member
  • *****
  • Posts: 9008
Re: height of Courier New 12pt font not right (windows, Lazarus 2.2.0 RC2)
« Reply #14 on: November 11, 2021, 05:00:02 pm »
I checked your demo and confirm the issue with Win 11 (Laz main).

The issue is not related to the font file since when I paint the underlined text onto a Paintbox without clipping the underline is always there. Moreover, TStaticText does not show the issue (it is painted by the widgetset, though).

There are some other font sizes at which the underline disappears in the AutoSize=true case. Of course it disappears in the AutoSize=false case when the text height is larger than the control height.
Mainly Lazarus trunk / fpc 3.2.0 / all 32-bit on Win-10, but many more...

 

TinyPortal © 2005-2018