Lazarus Release Candidate 2 of 4.0

[JimKueneman]

Tried the arm version for MacOS and it just crashes on start.  The dialog came up to make sure the compiler/linker/debugger/windowing type but once it wanted to start it just crashes.  Tried RC1 and it worked as expected.

Jim

[Martin_fr]

Tried the arm version for MacOS and it just crashes on start.  The dialog came up to make sure the compiler/linker/debugger/windowing type but once it wanted to start it just crashes.  Tried RC1 and it worked as expected.

Not sure, who of the team is monitoring here - and how frequently. If you don't get a reply, then please report on the bug tracker.

[hukka]

Code: Pascal  [Select][+][-]

1.   FontData^.NeedETO := False;

And rebuild the IDE.
See if that makes any difference. (This is not a fix, this may have side effects, leading to small paint errors / but I want to check if the issue is related to this).

No discernable difference. Log attached.
I'm opening an issue now with some more details so this thread won't get bogged down. Thanks.

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

[tbebekis]

I cannot find the "Document Outline" in this new version, the one above the Object Inspector showing the component tree of a form.

[Martin_fr]

I cannot find the "Document Outline" in this new version, the one above the Object Inspector showing the component tree of a form.

Right click anywhere in the Object inspector. Is "Show Component tree" checked?

- If not select it.
- If yes, check if there is a slider/resizer at the top of the OI?

It should be on by default.
If the above fixed it, then for the question why it was missing, it would be needed to know if you had any old config. And what was in that old config?
OS? Anchor-docked? Docked form edit?

[dsiders]

I cannot find the "Document Outline" in this new version, the one above the Object Inspector showing the component tree of a form.

Right click on the Object Inspector, and check the "Show Component Tree" option.

[n7800]

I cannot find the "Document Outline" in this new version, the one above the Object Inspector showing the component tree of a form.

Frankly, I had this problem a couple of times (long ago). But I couldn't reproduce it, so I didn't report it. It seems I was using a undocked IDE, installed the docking package, and for some reason the checkbox "Show Component Tree" was unchecked in the Object Inspector...

[Martin_fr]

installed the docking package, and for some reason the checkbox "Show Component Tree" was unchecked in the Object Inspector...

It may be that this setting is part of the "Desktop" => as in the desktop layouts you can have for Edit vs Debug, in the desktop drop down button.

When docked windows have obviously other coordinates than when no docking is used. So Docking has it's own set of desktops, and when you toggle docking on/off (or install it for the first time), then you switch between those different sets of desktops.

In the past, when docking created it's own desktops (on first run), it left lots of values unset.


I just tested that, if I start an IDE the very first time (with empty config folder) and use docking, then this panel is hidden.

Please report that as a bug on the tracker, so it wont get forgotten.

[TRon]

I just tested that, if I start an IDE the very first time (with empty config folder) and use docking, then this panel is hidden.

Confirmed, I noticed this as well (before RC2 it was always visible by default for me).

[TraumTaenzerDieter]

Ein kleiner Bug?
Das HintWindow übernimmt NICHT mehr die angegebene Hintergrundfarbe.
ScreenShot der Ausgaben von Lazarus 3.6 und 4.0 RC2
und Testprogramm in Anhang.
Bitte einmal prüfen.

[Martin_fr]

Pascal Syntax Highlight Changes

The following has been fixed after 4.0RC2.

The IDE (and SynEdit) now differentiate between Keywords and Modifiers. (e.g.: stdcall, overload, virtual, deprecated, ...)
https://wiki.freepascal.org/Lazarus_4.0_release_notes#Editor_Settings
https://wiki.freepascal.org/Lazarus_4.0_release_notes#SynEdit_(in_user_apps)

However the build-in color schemes had not been updated for that (affecting especially the dark schemes). So if you were using one of them, then those modifiers would have been bold. But they would no longer have the same color as keywords.

The build-in schemes have been update in the main branch and fixes branch (after RC2). Modifier now have the same defaults as Keywords.


If you are using your own scheme, or if you downloaded a 3rd party scheme, then you may need to update this yourself.

Maintainers of 3rd party schemes should update their published xml downloads accordingly.

[n7800]

Managed to reproduce. You need to run the IDE (already built with the docking manager) with an empty configuration directory. Then there will be no Component Tree when running.

[TRon]

Managed to reproduce. You need to run the IDE (already built with the docking manager) with an empty configuration directory. Then there will be no Component Tree when running.

Sorry that you needed to verify that (I should of mentioned the conditions). Indeed an empty config directory, fresh build and docked enabled on first startup. Though I haven't verified with other conditions. Checmarking the option was enough for me to 'fix' the issue.

[BlueIcaro]

Hello, I downloaded the Release Candidate 2.0 for Windows and now problem. Now I want download the same release for debian 12, I going to here https://sourceforge.net/projects/lazarus/files/Lazarus%20Linux%20amd64%20DEB/Lazarus%204.0RC2/ but the files inside are:

• lazarus-project_4.0.0-0_amd64.deb
• fpc-src_3.2.2-210709_amd64.deb
• fpc-laz_3.2.2-210709_amd64.deb[/Ii]
  

This files are Release candidate 2.0?

/BlueIcaro

[n7800]

The "TDesktopOIOptions.Create" constructor is missing the initialization of "FShowComponentTree" (which is set to "true" in the constructor of "TObjectInspectorDlg.Create" itself):

Code: Diff  [Select][+][-]

1. diff --git a/ide/envguioptions.pas b/ide/envguioptions.pas
2. index 987e8faa3b..d8105a4e7f 100644
3. --- a/ide/envguioptions.pas
4. +++ b/ide/envguioptions.pas
5. @@ -458,6 +458,7 @@ var
6.    I: TObjectInspectorPage;
7.  begin
8.    FComponentTreeHeight := -1;
9. +  FShowComponentTree := True;
10.    FInfoBoxHeight := -1;
11.    FShowInfoBox := True;
12.    for I in TObjectInspectorPage do
13.