Recent

Author Topic: We are planning the next release: Lazarus 2.0.12  (Read 7616 times)

Zvoni

  • Sr. Member
  • ****
  • Posts: 470
Re: We are planning the next release: Lazarus 2.0.12
« Reply #15 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
One System to rule them all, One IDE to find them,
One Code to bring them all, and to the Framework bind them,
in the Land of Redmond, where the Windows lie
---------------------------------------------------------------------
People call me crazy, because i'm jumping out of perfectly fine aircraft

dbannon

  • Hero Member
  • *****
  • Posts: 1296
    • tomboy-ng, a rewrite of the classic Tomboy
Re: We are planning the next release: Lazarus 2.0.12
« Reply #16 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
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

Bart

  • Hero Member
  • *****
  • Posts: 4186
    • Bart en Mariska's Webstek
Re: We are planning the next release: Lazarus 2.0.12
« Reply #17 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

Igor Kokarev

  • Sr. Member
  • ****
  • Posts: 316
Re: We are planning the next release: Lazarus 2.0.12
« Reply #18 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.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3977
  • I like bugs.
Re: We are planning the next release: Lazarus 2.0.12
« Reply #19 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.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

PascalDragon

  • Hero Member
  • *****
  • Posts: 2758
  • Compiler Developer
Re: We are planning the next release: Lazarus 2.0.12
« Reply #20 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.

dbannon

  • Hero Member
  • *****
  • Posts: 1296
    • tomboy-ng, a rewrite of the classic Tomboy
Re: We are planning the next release: Lazarus 2.0.12
« Reply #21 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
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

trev

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1282
  • Former Delphi 1-7, 10.2 User
Re: We are planning the next release: Lazarus 2.0.12
« Reply #22 on: February 20, 2021, 01:58:17 am »
Does Lazarus 2.0.12 use FPC 3.2.0 (not fixes tree)?

See first post.
Lazarus 2.1 r64368 FPC 3.3.1 r48100 macOS 10.14.6 Xcode 11.3.1
Lazarus 2.1 r64455 3.3.1 r48839   macOS 11.2.2 aarch64 Xcode 12.4
Lazarus 2.1 r61574 3.3.1 r42318 FreeBSD 12.1 amd64 VMware VM
Lazarus 2.1 r61574 3.0.4 Ubuntu 20.04 Parallels VM
Lazarus 2.0.10 3.2.0 Win10 Parallels VM

Igor Kokarev

  • Sr. Member
  • ****
  • Posts: 316
Re: We are planning the next release: Lazarus 2.0.12
« Reply #23 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.

kegge13

  • New Member
  • *
  • Posts: 39
Re: We are planning the next release: Lazarus 2.0.12
« Reply #24 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?
« Last Edit: February 20, 2021, 05:14:52 pm by kegge13 »

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 6906
  • Debugger - SynEdit - and more
    • wiki
Re: We are planning the next release: Lazarus 2.0.12
« Reply #25 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.


kegge13

  • New Member
  • *
  • Posts: 39
Re: We are planning the next release: Lazarus 2.0.12
« Reply #26 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.

« Last Edit: February 21, 2021, 05:54:38 pm by kegge13 »

 

TinyPortal © 2005-2018