Lazarus Release Candidate 1 of 2.2.0

[dbannon]

Yes, I can confirm that Fixes_2_2 does the same thing, my sort of same thing, not prof7bit's.

So, the question is, is it because I am missing something in my install ......

OK, my previous post was misleading, the issue I spotted has nothing to do with the one from prof7bit.

I just built a new U2004 Mate VM and I installed FPC322 (from Deb) and trunk (sorry, Main), Fixes_2_2 and Lazarus_2_0_12, (no cross compilers) all from source and all exhibit the same problem, as shown in the screen dump further up this thread.

So, mine is an 'install issue', and does not belong in this thread. It seems (?) Ubuntu 2004 now arrives with some dodgy font information that can be corrected by refreshing the font cache. (clean out local cache first) -

Code: Bash  [Select][+][-]

1. rm -rf ~/.cache/fontconfig
2. sudo fc-cache -r -v

I have no idea why this was necessary but its repeatable using U2004 Mate in a VM ......

Davo

[mrmaxmusterman]

In the past we were aiming at 4 to 6 weeks.
At the moment we got lots of other stuff going on. So no idea.

Are there any updates as far as the release date of Lazarus 2.2 goes?

[prof7bit]

In the past we were aiming at 4 to 6 weeks.
At the moment we got lots of other stuff going on. So no idea.

Are there any updates as far as the release date of Lazarus 2.2 goes?

In the Milestones view on Gitlab it lists 366 Bugs to be fixed before 2.2. Yesterday it was 365.

[mrmaxmusterman]

In the Milestones view on Gitlab it lists 366 Bugs to be fixed before 2.2. Yesterday it was 365.

But it also says that there are only 19 issues open and 347 are already closed and that the Milestone is 94% complete.

[Martin_fr]

As indicated earlier the issues are added as they are suggested here on the forum.
So they should at least be noted by the maintainer of the affected code.

They may still be moved to the next release.

[chikega]

Thank you for all the hard work for this release 

[PeterBB]

... issues are added as they are suggested here on the forum. ...

I would like to suggest https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39354
be added to issues now that the bug been recovered from its loss during the move to git.

I gather that https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/35478 is included,
but without 39354, the widgetset will still not compile on Linux.

It broke with FPC 3.2.0, but can only be fixed in Lazarus.

The bug report includes a trivial patch to fix.

Cheers,
Peter

[PeterBB]

I have built RC1 on Arch Linux OK by modifying the existing PKGBUILD.

Attaching here.


Cheers,
Peter

P.S.  Had to add .txt extension to upload. Rename before trying to use!

[Milsa]

I have this title in main IDE window in Lazarus:

Lazarus IDE v2.0.10 r63526

Please add to title these information:
- processor version: 32/64 bit
- project compilation setting: i386-win32, x86_64-win64, etc
Changed title by this comment:

Lazarus IDE v2.0.10 r63526, 32 bit, i386-win32

Please add this to final Lazarus release.

[Martin_fr]

I have this title in main IDE window in Lazarus:

Lazarus IDE v2.0.10 r63526

Please add to title these information:
- processor version: 32/64 bit
- project compilation setting: i386-win32, x86_64-win64, etc
Changed title by this comment:

Lazarus IDE v2.0.10 r63526, 32 bit, i386-win32

Please add this to final Lazarus release.

I don't think this will make it. (for starters its a new feature, not a bug fix)

It's not (no longer) an option of adding just a (few) checkbox(es).
There are to many bits of info that could be toggled, and then there is the question of ordering....

So what we need is an option to specify the title using the IDE variables that are also used in path info.
like: $(TargetCPU)

[Milsa]

Ok, please add it in future.

[Martin_fr]

Check, and if there is no feature request yet (bugtracker) then add one.

Then if anyone has time and is interested in it.....
Or contribute to it.

[prof7bit]

Is it only me or is the dialog for configuring the syntax colors broken (fixes and main)?

* Select a theme you usually don't use (for example Twilight to not break anything)
* change one of the colors
* click ok

-> color has changed, this is OK so far.

* Open the dialog again, click on "Reset all" (top button panel)

-> strange things happen, color is not reset to scheme default, instead colors in the left sidebar are jumping around and it loses the ability to click into the example synedit to select a syntax element.

I tried the same with main, symptoms are similar, and even got it to segfault.

I have anchordocking installed, and also using the Desktops feature for having a separate window layout during debug, if that makes any difference (it does affect storage of some settings), did not yet test without it.

Am I using it wrong? The "reset all" button should reset all colors to the ones defined in the selected scheme xml, shouldn't it? Or did I just find a nasty bug? I'm going to test more and maybe file an issue tomorrow if nobody else did it yet.

[Martin_fr]

It happens without anchordocking too.

Please create a bug report.

Do you by chance know when (approx) it last worked?

[prof7bit]

Do you by chance know when (approx) it last worked?

No, unfortunately not. I have not played around with color themes for at least a year, only recently felt the need to get some fresh colors and noticed this effect only by accident (always avoided the reset button when making new themes).