Lazarus

Announcements => Lazarus => Topic started by: Martin_fr on February 11, 2021, 05:42:48 pm

Title: We are planning the next release: Lazarus 2.0.12
Post by: Martin_fr on February 11, 2021, 05:42:48 pm
The Lazarus team has scheduled

      Lazarus 2.0.12
      for February 2021 (estimated 22nd to 25th)

      This release will be built with FPC 3.2.0.

Here is the list of fixes for Lazarus 2.0.12 (since 2.0.0):
http://wiki.freepascal.org/Lazarus_2.0_fixes_branch


We would invite everyone to provide their feedback to help us improve
this upcoming release. Please let us know in particular:
- Any bug-fixes already made to trunk, that you believe should still be
  merged to the fixes branch (fixes that are not listed on the above wiki page)
- Any regressions that happened in fixes branch since the release of 2.0
- Other urgent (e.g. crashes/data-loss/...) matters, you believe we should know before the release.

Please attempt to provide your feedback by: 16th February 2021


More info on our release process can be found at (work in progress):
http://wiki.lazarus.freepascal.org/Lazarus_release_engineering

Information about the previous release:
http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.0.4
http://wiki.lazarus.freepascal.org/User_Changes_3.2.0

The intended minimum requirements for the release will be:

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.

macOS:
   10.5 to 10.12; Carbon (32bit), Cocoa (64bit, beta), qt and qt5
   (32 or 64bit).


(*) requires install from sources

Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: tetrastes on February 11, 2021, 08:22:41 pm
The issue https://forum.lazarus.freepascal.org/index.php?topic=52808 remains in fixes.
Compile the project for LCLwin32 widgetset, launch and click ToggleBox - ComboBox "flickers" (white box appears in the ComboBox for a time of Sleep(), approximately the size of the focus rectangle, but in other my programs it can be the size of the whole ComboBox).
This is regression since Lazarus 2.0.8.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Alextp on February 11, 2021, 08:39:44 pm
>macOS:    10.5 to 10.12; Carbon (32bit), Cocoa (64bit, beta),

Cocoa is not beta now (IDE has dropped this mark).
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Martin_fr on February 11, 2021, 08:52:39 pm
The issue https://forum.lazarus.freepascal.org/index.php?topic=52808 remains in fixes.
Compile the project for LCLwin32 widgetset, launch and click ToggleBox - ComboBox "flickers" (white box appears in the ComboBox for a time of Sleep(), approximately the size of the focus rectangle, but in other my programs it can be the size of the whole ComboBox).
This is regression since Lazarus 2.0.8.
Unfortunately there is no mention when it was fixed in trunk. So no info where to look what to backport (nor if it even could be backported).
If indeed it is fixed in trunk, then that means the fix will be in Lazarus 2.2
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: del on February 12, 2021, 05:33:43 am
Keep up the great work !!!  :) :) :)
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Al-Eid on February 16, 2021, 09:40:17 am
Thank you and good luck
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: ASerge on February 16, 2021, 04:08:47 pm
- Any bug-fixes already made to trunk, that you believe should still be
  merged to the fixes branch (fixes that are not listed on the above wiki page)
- Any regressions that happened in fixes branch since the release of 2.0
- Other urgent (e.g. crashes/data-loss/...) matters, you believe we should know before the release.
In my opinion, everything that has already been fixed (even the little things) should be included. There will be no other time for this anyway.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Martin_fr on February 16, 2021, 04:43:18 pm
- Any bug-fixes already made to trunk, that you believe should still be
  merged to the fixes branch (fixes that are not listed on the above wiki page)
- Any regressions that happened in fixes branch since the release of 2.0
- Other urgent (e.g. crashes/data-loss/...) matters, you believe we should know before the release.
In my opinion, everything that has already been fixed (even the little things) should be included. There will be no other time for this anyway.

In principal yes. Practical there are limits. Some fixes make massive changes and/or may relay on code of new features. Merging it may carry a high risk of breaking code, rewriting it may be a lot of work. Also some fixes may carry a risk of breaking other stuff, then they may not be merged, or only be merged if they had been tested long enough.

The "that you believe" is not about whether a fix should be merged, but rather whether anyone believes a fix has not yet been merged. (Of course that includes, any fix of which someone knows for sure that it wasn't yet merged).
In that sense, any un-merged bug-fix can be brought forward. It will then - time allowing - be evaluated for merging. (Time allowing: That is the committer for each revision needs to be looked up, contacted, and they needs to decide).

Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: ASerge on February 16, 2021, 05:04:10 pm
But then the work of the team members is wasted.
The bug or feature is patched and marked as fixed. In this case, some time was spent on its preparation and verification.
But it never gets released! It doesn't really encourage others to write any patches.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: JuhaManninen on February 16, 2021, 05:15:24 pm
But then the work of the team members is wasted.
The bug or feature is patched and marked as fixed. In this case, some time was spent on its preparation and verification.
But it never gets released! It doesn't really encourage others to write any patches.
Of  course it will be released in the next major version 2.2.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Roelof on February 17, 2021, 10:04:13 am
Very nice indeed!
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Sieben on February 18, 2021, 07:48:11 pm
Quote
We would invite everyone to provide their feedback to help us improve this upcoming release.

Sorry for missing this thread 'til now, but it might still be the right place to leave a note that TSynEdit does not publish OnContextPopup and OnResize yet, and same for T/DB/DateTimePicker with OnShowHint - cf here (https://bugs.freepascal.org/view.php?id=38453) as well. If not for this then maybe for the next release.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Martin_fr on February 18, 2021, 08:46:30 pm
Sorry for missing this thread 'til now, but it might still be the right place to leave a note that TSynEdit does not publish OnContextPopup and OnResize yet, and same for T/DB/DateTimePicker with OnShowHint - cf here (https://bugs.freepascal.org/view.php?id=38453) as well. If not for this then maybe for the next release.

I made a note, probably will still get it in.

Not sure that patch fixes the issue for SynEdit?
If not, then make a new bug report for SynEdit, please. (no patch required, just need a reminder)
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Sieben on February 18, 2021, 10:08:35 pm
Quote
Not sure that patch fixes the issue for SynEdit?

I did not include it in my patch - which was not applied, however - and afaik wp did not include it either. Anyway, events still missing in current rev 64617.

Reminder created as issue 38511 (https://bugs.freepascal.org/view.php?id=38511).
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Martin_fr on February 19, 2021, 03:23:02 am
Reminder created as issue 38511 (https://bugs.freepascal.org/view.php?id=38511).

Fixed and merged. Merged the commit for the other components too.

Even though it was just half a day. Busy day, ant at the end of the day one last look at the bugtracker....
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Zvoni on February 19, 2021, 07:58:47 am
Any plans on including MySQL80-Bindings?
I'm aware, that this is more an FPC-Thing than Lazarus, but i noticed the patch for MySQL80 being submitted this week
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: dbannon on February 19, 2021, 09:22:15 am
I, personally, would like to see https://bugs.freepascal.org/view.php?id=38454 fixed.  Its about entering extended characters in GTK2 using the now reasonably standardized "compose key" mode.  You press the defined compose key, such as shift-leftWin, then two characters that represent the desired utf8 character, for example, for 'a' with a umlaut, you would press 'a' then a double inverted comma. 

https://help.ubuntu.com/community/ComposeKey

While the bug report initially associated the bug with KMemo, it also applies, for example with a TMemo.  I have posted a simple demo using TMemo, no kmemo required, I promise !

I did have a go at tracking it down myself but the key handling in GTK2 is way beyond me !   And it is a purely GTK2 issue ...

Davo
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Bart on February 19, 2021, 12:27:48 pm
How does that (compose key) work?
I have a Linux Mint 18 in a VM with Dutch locale.
I "compose" my diacritics via "dead keys": I press " and then A and I get Ä for example.
IIRC then this works OK in GTK2.
I have a standard US-intl keyboard (laptop though).
Any idea which key I should use to compose a key in the way you do it?

Bart
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Igor Kokarev on February 19, 2021, 02:57:03 pm
Thanks for your great work!

Do you plan to release a compiled build for Apple Silicon? Or will it possible to compile Lazarus 2.0.12 (not trunk) on Apple Silicon?

Does Lazarus 2.0.12 use FPC 3.2.0 (not fixes tree)?
For compilation target darwin/aarch64 fpc 3.2.0 fixes tree is required.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: JuhaManninen on February 19, 2021, 03:10:17 pm
I, personally, would like to see https://bugs.freepascal.org/view.php?id=38454 fixed.
The question with this dot release 2.0.12 is which already existing revisions from trunk should be merged. Let's keep this thread about it.
I hope your issue and all others will be solved some day in trunk. I also don't know how to fix key handling in GTK2.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: PascalDragon on February 19, 2021, 03:56:29 pm
Any plans on including MySQL80-Bindings?
I'm aware, that this is more an FPC-Thing than Lazarus, but i noticed the patch for MySQL80 being submitted this week

This requires 3.2.2 to be released first.

Does Lazarus 2.0.12 use FPC 3.2.0 (not fixes tree)?
For compilation target darwin/aarch64 fpc 3.2.0 fixes tree is required.

As mentioned in the first post it uses 3.2.0.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: dbannon on February 20, 2021, 12:52:41 am
How does that (compose key) work?
......
Bart

Bart, taking on board Juha's comment about this discussion being about things already fixed, I'll open a new thread under Programming->WidgetSets. 

Davo
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: trev on February 20, 2021, 01:58:17 am
Does Lazarus 2.0.12 use FPC 3.2.0 (not fixes tree)?

See first post.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Igor Kokarev on February 20, 2021, 06:59:42 am
Thanks,

We'll wait patiently for Lazarus 2.2 with FPC 3.2.2. It will be a golden age for macOS development.
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: kegge13 on February 20, 2021, 04:44:33 pm
Thank you for the good work.
With some startup challenges I created a secondary installation by pulling the svn.
Did a make with the make.exe from the primary v2.0.10 installation.
When I made (windows platform) a shortcut to the startlazarus.exe with

D:\temp\rc_lclwc\startlazarus.exe --pcp=D:\temp\rc_lclwc\configs
it still wanted to do something with my standard configuration in c:\users\...

D:\temp\rc_lclwc\lazarus.exe --pcp=D:\temp\rc_lclwc\configs
worked fine.

Is it correct that I need to set fcp.exe and gdb.exe paths to the v2.0.10 installation? Did not find any in the 2.0.12  installation.

The new version came with one extra hint for my project about maskedit not being used. v2.0.10 did not make this remark. Indeed it can be missed when building in both versions.

Any hints for further testing?
Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: Martin_fr on February 20, 2021, 05:39:17 pm
On Windows:
Create the file
D:\temp\rc_lclwc\lazarus.cfg

In it put the single line
--primary-config-path=D:\temp\rc_lclwc\configs

Then you do not need it on the command-line.




Did you copy your old config?
Some config files contain full path.

And if you copied, then it will warn you that the file was last used from .....

If you start with an empty config folder, the IDE creates all config for you.

You can copy the file EditorOptions.xml. Other files, you need to check for full paths first.


If you got a new config, Lazarus will ask where fpc and gdb are. (it may find your primary install, and suggest them)
You can also start
  lazarus.exe --setup
(and --pcp unless you have the lazarus.cfg)

It is ok, to point your 2ndary Lazarus to use Fpc and gdb from your primary install.

Gdb you can just copy to your 2ndary install.

If you copy/move fpc, you need to find the file fpc.cfg and edit it. It contains absolute path to some of the files/folders.

Title: Re: We are planning the next release: Lazarus 2.0.12
Post by: kegge13 on February 21, 2021, 12:37:30 pm
When compiling in 2.0.12

I got a lot of warnings for deprecated symbols. Here are some of them:

Code: Text  [Select][+][-]
  1. tachartaxis.pas(441,41) Warning: Symbol "OnMarkToText" is deprecated: "Use "OnGetMarkText"
  2. tagraph.pas(635,84) Warning: Symbol "OnBeforeDrawBackground" is deprecated: "Use OnBeforeCustomDrawBackground instead"
  3. taseries.pas(63,42) Warning: Symbol "TBeforeDrawBarEvent" is deprecated
  4. tatools.pas(2135,21) Warning: Symbol "OnDraw" is deprecated: "Use OnCustomDraw"
  5. wellform.pas(2014,32) Warning: Symbol "OnMarkToText" is deprecated: "Use "OnGetMarkText"
  6.  
I tried to resolve the last one for my own project, by replacing an OnMarkToText event with a OnGetMarkText event. This works fine but is not backwards compatible with v.2.0.10. A workaround is to set this event at runtime instead of at design time and have one of both events exist depending on the lcl version.

How can I implement such a test in the code?
I tried this to include immediately after the uses statement of the interface of (my project) unit wellform:
Code: Text  [Select][+][-]
  1. //Work-around for backward compatibility for LCL v2.0.10 and below.
  2. //It seems that both the TChartAxis.OnMarkToText event and TChartAxis.OnGetMarkText exist in v2.0.10 and v2.0.12
  3. //but the object inspector v2.0.10 offers only OnMarkToText and v2.0.12 only OnGetMarkText.
  4. //Therefore setting this at design time is has become problematic. Instead this event now is set at runtime in FormCreate.
  5. {$if declared(TChartGetAxisMarkTextEvent)}
  6.  {$DEFINE LCL_2-0-12_Up}
  7. {$endif}
  8.  

This defines  LCL_2-0-12_Up also for v2.0.10 but in the object inspector the OnMarkToText event is shown but the OnGetMarkText event not. A bit strange.

TinyPortal © 2005-2018