Lazarus

Announcements => Lazarus => Topic started by: Martin_fr on October 13, 2019, 02:47:07 pm

Title: We are planning the next release: Lazarus 2.0.6
Post by: Martin_fr on October 13, 2019, 02:47:07 pm
The Lazarus team is glad to announce:

      The upcoming release of Lazarus 2.0.6

which has been scheduled for the

      last week of October 2019

This release will be built with FPC 3.0.4.
The previous release Lazarus 2.0.4 was built with FPC 3.0.4 as well.

Here is the list of fixes for Lazarus 2.0.4 (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 as 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 matters, you believe we should know before the release.

Please attempt to provide your feedback by: 23rd October 2019

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

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).

Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Martin_fr on October 13, 2019, 02:49:26 pm
Please note, due to me being offline during some time of the run up, this thread will have reduced monitoring (as many team members are only on the mailing list).

Should you not get a reply by a team member to any post you make here, then kindly repeat it on the mail list.

Thank you.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ravkepar on October 13, 2019, 07:49:54 pm
I hope the installer works on OSX 10.15. Lazarus 2.0.4 won't work on OSX 10.15.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ASBzone on October 13, 2019, 09:35:18 pm
Please note, due to me being offline during some time of the run up, this thread will have reduced monitoring (as many team members are only on the mailing list).

Should you not get a reply by a team member to any post you make here, then kindly repeat it on the mail list.

Thank you.


Thanks, Martin

It would be nice to see the following fixed for this release:   https://bugs.freepascal.org/view.php?id=35572 (https://bugs.freepascal.org/view.php?id=35572)

Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: willbprog9933 on October 13, 2019, 11:23:55 pm
I hope the installer works on OSX 10.15. Lazarus 2.0.4 won't work on OSX 10.15.

Yes, please let the new version work on macOS Catalina.  I had to restore my Mac back to Mojave because Lazarus and FPC weren't working (as well as some other non-Lazarus stuff). :-)
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Martin_fr on October 13, 2019, 11:26:46 pm
I believe a cocoa installer is planned, but I have to get confirmation on this.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: loaded on October 14, 2019, 07:16:08 am
We are looking forward.
In fact, LAMW android plugin, it will be very nice if you add :)
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Valderrama on October 14, 2019, 12:11:01 pm
Would be great if you could have the new installer work on MacOS 10.15 Catalina. Same experience as previous mentions: 2.0.4 no longer works on Catalina. Please also refer to this thread: https://forum.lazarus.freepascal.org/index.php/topic,47011.0.html
Many thanks for your efforts!
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: dbannon on October 14, 2019, 01:03:52 pm

Right now, the System TrayIcon  (Lazarus Additional Component toolbar) does not work as it should on many, maybe even most, Linux systems.

r62020 (listed as "Submitted by developer / committer, tested, waiting to be merged") goes a long way towards getting some functionality to most Linux desktops. Its not great but heaps better than current situation.

I'd like to add at least one entry to its look up table, Enlightenment, see -
https://forum.lazarus.freepascal.org/index.php/topic,46912.msg336373.html#msg336373

(I'd go further and put some ugly stuff in there that allows run time change of behavior using an environment variable but I suspect thats a bridge too far away right now).

Davo
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: mischi on October 14, 2019, 01:39:34 pm
Re macOS, in particular Catalina. I am working on the port description of Lazarus-Cocoa 2.0.4 / fpc 3.0.4 for MacPorts, but still have some issues to resolve (You can follow the pull request here: https://github.com/macports/macports-ports/pull/5439). Once finished, updating to 2.0.6 should not be a problem.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: JuhaManninen on October 14, 2019, 03:33:27 pm
I'd like to add at least one entry to its look up table, Enlightenment, see -
https://forum.lazarus.freepascal.org/index.php/topic,46912.msg336373.html#msg336373

(I'd go further and put some ugly stuff in there that allows run time change of behavior using an environment variable but I suspect thats a bridge too far away right now).
It is not a bridge too far away if you have the code already done and tested. Just create a patch and I will apply it and then it will be merged to fixes_2_0 before the release.
If you don't have such code yet then it is best left for trunk / next major release.

One thing bothers me: In the forum topic "Problem with TrayIcon: mantis 35723" I get the impression you don't understand the fundamental development process even after providing many patches.
I mean you fail to understand that all development happens in the trunk branch. Every single change goes there initially.
Simultaneously another regular contributor has the same problem:
 https://bugs.freepascal.org/view.php?id=36167
How is this possible? Maybe Lazarus project should explain its development process better. Where exactly should it be explained?
This is strange because a development branch in a revision control system is a common practice in every open source project. It may be called "trunk" or something else but the idea is the same. The details of the merging process may vary but the idea remains.
What should we do to improve the situation?
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Martin_fr on October 14, 2019, 04:24:41 pm
What should we do to improve the situation?
We already have some pages in the wiki, but they are vastly outdated, or lacking info...

https://wiki.lazarus.freepascal.org/Lazarus_Development_Process

https://wiki.lazarus.freepascal.org/Creating_A_Patch  This one actually says: "you need trunk"....

Anyway, that said, a patch towards fixes branch should 99% be acceptable, providing that:
=> It was somehow confirmed the issue itself exists in trunk. (The fixes patch is likely to be apply-able to trunk)
Anyway before sending a fixes based branch, it is best to check with the developer who is assigned to the issue.

If the issue is already fixed in trunk, then a separate patch for the fixes branch can not be accepted. The fixes branch then must be fixed by merging trunk. That is, if the fix is deemed merge-able.

Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Soner on October 14, 2019, 04:56:46 pm
EDIT: solved with:
1) make bigide
2) rebuild from inside lazarus (menu > tools > build lazarus ...)
---------------------
Original Message:


I updated my 2.0.fixes branch now i I get "internall error"
Code: Text  [Select]
  1. Compile checks, Hints: 6
  2. Note: package LCLBase 2.0.5: passing compiler option -O twice with different values
  3. Note: package LCLBase 2.0.5: passing compiler option -g twice with different values
  4. Note: package LCLBase 2.0.5: passing compiler option -gl twice with different values
  5. Note: package LCL 2.0.5: passing compiler option -O twice with different values
  6. Note: package LCL 2.0.5: passing compiler option -g twice with different values
  7. Note: package LCL 2.0.5: passing compiler option -gl twice with different values
  8. Free Pascal Compiler version 3.0.4 [2018/10/27] for x86_64
  9. Copyright (c) 1993-2017 by Florian Klaempfl and others
  10. (1002) Target OS: Win64 for x64
  11. (3104) Compiling alllclunits.pp
  12. (3104) Compiling imglist.pp
  13. D:\laz20\lcl\controls.pp(473,1) Fatal: Internal error 200611031
  14. Fatal: (1018) Compilation aborted
  15. Error: D:\laz20\fpc\3.0.4\bin\x86_64-win64\ppcx64.exe returned an error exitcode
  16.  
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Martin_fr on October 14, 2019, 05:01:14 pm
That would be a bug in fpc. https://bugs.freepascal.org/view.php?id=32352

Have you tried a clean build?
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Soner on October 14, 2019, 05:04:26 pm
I solved the problem with first "make bigide", then rebuilding from inside lazarus.
My configuration must have failure.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: jamie on October 14, 2019, 05:52:07 pm
I looked at the current list of fixes, I don't see my changes I requested in there unless it was a midnight silent run?

 1. On two of my systems the Html Help example can't locate the default browser, I showed the
defective code and what to do to fix it.
 
 2. The ShellTreeView is basically useless by itself unless it has a OnEntryEvent to select weather we can reject the entry or even alter its name or place a Filter property in it that can do the same, but the Event would be better, more flexible.
 
  With the ShellTreeView its only logical use is with the ShellListView, the two should have been married together as one component. But currently they are not and it just sits there on the component bard wasting space by them selves in my view. The two of them should be flexible to be used stand alone in any manner as we please.

 Thanks for listening to my whining.

Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Martin_fr on October 14, 2019, 09:50:52 pm
Do you have the link to the bug in mantis?

Or -assuming it is fixed in trunk - do you know who fixed it when (revision number)?
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Bart on October 14, 2019, 10:04:18 pm
2. The ShellTreeView is basically useless by itself unless it has a OnEntryEvent to select weather we can reject the entry or even alter its name or place a Filter property in it that can do the same, but the Event would be better, more flexible.

It has OnAddItem event in trunk.
I implemented that, based on your complaints in another forum thread.
See Lazarus 2.2.0 release notes (https://wiki.lazarus.freepascal.org/Lazarus_2.2.0_release_notes#TShellTreeView).
Mutatis mutandis for TShellTreeView, which in trunk now also supports case-insensitive masks on *nix.

It's not a bugfix but an added functionality, it's not Delhi compatible.
Therefore it was not put on the merge list for the 2.0 fixes branch.

Bart

Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: jamie on October 15, 2019, 02:07:27 am
Thank you very much, you are a gentleman and a scholar.

 Now we need to address the issue of the HTMLHELP example failing with those that have Microsoft Edge in their PC's

 I have two PC's with Win10 that has Edge in it, the code to fine the default browser fails.

 If I disable this code frag that looks for Edge specifically then the system follows through and loads Edge anyways if that Is the default browser.

 If this hasn't been fixed I can point you to the source of the hardship.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Thaddy on October 15, 2019, 08:35:26 am
Now we need to address the issue of the HTMLHELP example failing with those that have Microsoft Edge in their PC's
AFAIK OpenUrl works? Can you show the issue?
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ptvs on October 15, 2019, 11:44:32 am
We would invite everyone to provide their feedback to help us improve this upcoming release. Please let as know in particular:
- Any bug-fixes already made to trunk, that you believe should still be merged to the fixes branch
0035043: Add checkbox to show/hide property filter in object inspector (https://bugs.freepascal.org/view.php?id=35043)
0035044: Hide toolbar buttons's captions in Call Stack window (https://bugs.freepascal.org/view.php?id=35044)
0035270: Handling mouse events through shaped TWinControl (https://bugs.freepascal.org/view.php?id=35270)
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Thaddy on October 15, 2019, 12:01:57 pm
None of those are showstoppers. Bugs are, feature requests not. Focus plz.

For noobs and ill-informed:
A release candidate  is feature complete, new features will NOT be added.
You should focus on bugs. Nothing more. Maybe Martin should add a sticky?

As you can see and read for yourself, some of your issues are solved in higher - not release - versions.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ptvs on October 15, 2019, 02:30:44 pm
A release candidate  is feature complete, new features will NOT be added.
You should focus on bugs. Nothing more. Maybe Martin should add a sticky?
Ok, I can agree that 35043 and 35044 are features, though they only fix some minor UI inconsistency.
But 35270 is clearly a bug fix.

Quote
As you can see and read for yourself, some of your issues are solved in higher - not release - versions.
That's only one issue, others have empty TargetVersion.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Thaddy on October 15, 2019, 03:21:34 pm
So in that case focus on the bug...? That's all, and good testing. Devels want to know about real bugs.
Since it is already fixed there is a slight chance of making it into the release. (border case in my view).

OTOH if it is not a clear feature and the feature set was already frozen, you will have to wait for the release after the current proposed one.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: JuhaManninen on October 15, 2019, 03:33:16 pm
But 35270 is clearly a bug fix.
Yes. I now added it to the list of revisions to be merged.
I anticipated some regressions. The original code had comments and all to describe its behavior. It was there for some reason at least in the past.
Now half a year has passed without complaints, I guess it is safe to merge it.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Thaddy on October 15, 2019, 03:53:25 pm
Thanks for explaining and we hope for a nice release. (Which it usually is)

I am sure ptvs is now satisfied too?
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Akira1364 on October 15, 2019, 04:41:14 pm
The presence of an official, normally-downloadable 64-bit Cocoa installer is by far the most urgent thing for this release, I'd say.

AFAIK the Carbon-based IDE simply doesn't work on the latest OSX release, and cannot be made to work.

Otherwise, for example, when someone inevitably posts the announcement on Reddit, the thread will just devolve into a bunch of people commenting about how Lazarus "isn't really as cross-platform as it claims" or similar sentiments, which is hardly good PR.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Thaddy on October 15, 2019, 05:49:21 pm
The presence of an official, normally-downloadable 64-bit Cocoa installer is by far the most urgent thing for this release, I'd say.
And the last one to be finished... (by logic)
Quote
Otherwise, for example, when someone inevitably posts the announcement on Reddit, the thread will just devolve into a bunch of people commenting about how Lazarus "isn't really as cross-platform as it claims" or similar sentiments, which is hardly good PR.
You are perfectly capable to compile from source. Not everyone is.
This is something that hunts all open source projects: expectations because in the future there are more options.
Better to educate our users in what to expect. ( and I am just a simple user).
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Akira1364 on October 15, 2019, 06:10:03 pm
You are perfectly capable to compile from source. Not everyone is.

Right, that's the point. Many people won't bother with Lazarus at all if they can't just download a working version directly, regardless of the various ways it's technically capable of being compiled.

At the very least, if it's really the case that a normal installer can't be put together for OSX in time, it would likely be a good idea to include a mention of FPCUpDeluxe in the announcement so that people are aware they have other easy options.

Moreover, FPCUpDeluxe is useful enough and widely used enough that permanently mentioning it on the actual websites for FPC and Lazarus would probably be a good idea too...

Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: dbannon on October 16, 2019, 12:50:34 am
Now, please forgive my ignorance but isn't the cocoa issue 'just' one of packaging ?

If the install chooses to put fpc and its libraries in user space, $HOME/somwhere/, in the same way many of us (in particular) Linux user put our svn built Lazarus, that would no longer offend Apple and with appropriate PATH and LDPATH all would work ?

Maybe we could argue that the installer is not actually part of 2.0.6 or any other Lazarus version ?

I agree its important, any claim to being cross platform depends on Mac.  Carbon no longer convinces anyone. But the installer could happen quite independently of 2.0.6

Davo
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: willbprog9933 on October 16, 2019, 12:54:13 am
Now, please forgive my ignorance but isn't the cocoa issue 'just' one of packaging ?

When I tried to install 2.0.4 from the main website (then through Source Forge) on macOS Catalina, it complained that it (or some part of it) was 32-bit.  I did not see a 64-bit installer available.  I guess that would fall outside the 'just packaging' realm.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: jamie on October 16, 2019, 12:55:12 am
@Thaddy, As I explained before, if you try out the HTMLHelp example that comes with Lazarus and have Microsoft Edge Installed and set as your default browser on Windows 10, it will display the nice error.
 
 OpenUrl works fine on other OSes and older windows because Edge isn't installed but the code clearly goes out of its way looking for Edge and if it finds it, executes it incorrectly, in fact the code actually makes no sense at all since it's executing a key not an actual file or path to one.

 The fix for this is to nullify the actual function that is doing this and have it return as a failed attempt, but if Edge is your default browser after that, Edge will be loaded..

 I edited the file because it fails on every PC that has edge installed and being the default browser at this point.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: dbannon on October 16, 2019, 03:49:08 am
When I tried to install 2.0.4 from the main website (then through Source Forge) on macOS Catalina, it complained that it (or some part of it) was 32-bit.  I did not see a 64-bit installer available.  I guess that would fall outside the 'just packaging' realm.

No, I disagree. You downloaded the 32bit Carbon package because thats all that is there right now. But a 64bit Cocoa could be packaged up and made available right now or way after the release of 2.0.6. The version of Lazarus and its release has little to do with decisions made during packaging (apart from every later version is better at Cocoa).

So, your issue is getting a Cocoa package made that puts files in some place acceptable to Apple. Its an important issue but not one related to what is in 2.0.6.

I could easily build you a Cocoa Lazarus on my aging Sierra Powerbook, I don't know how I'd build you a FPC but I bet plenty of people do know. FPC would be 3.0.4 (a?) but Lazarus could be 2.0.4, Fixes or 2.0.6 in a week or so time.

I reckon a thread in the OS -> Mac section of the Forum might be a good idea.   

Davo
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: willbprog9933 on October 16, 2019, 04:01:32 am
I disagree. You downloaded the 32bit Carbon package because thats all that is there right now. But a 64bit Cocoa could be packaged up and made available right now or way after the release of 2.0.6. The version of Lazarus and its release has little to do with decisions made during packaging (apart from every later version is better at Cocoa).

This wouldn't be real life if someone didn't disagree with me!  :P

This whole issue is not a big deal to me, but I'm sure it impacts others more severely.  I rolled back to Mojave and will upgrade to Catalina when it's had more time to 'bake'.  My main dev environment right now is on Debian Linux and everything works just fine there.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ps on October 17, 2019, 06:17:24 pm
BorderSpacing for 4+ controls is broken and unusable.

https://bugs.freepascal.org/view.php?id=36186
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Dan3468298 on October 17, 2019, 09:17:02 pm
I believe a cocoa installer is planned, but I have to get confirmation on this.

The opening post stated Mac Cocoa Beta so I take that to mean a Beta Installer.   Which I will wait for.   
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Akira1364 on October 17, 2019, 09:27:28 pm
Now, please forgive my ignorance but isn't the cocoa issue 'just' one of packaging ?

When I tried to install 2.0.4 from the main website (then through Source Forge) on macOS Catalina, it complained that it (or some part of it) was 32-bit.  I did not see a 64-bit installer available.  I guess that would fall outside the 'just packaging' realm.

The 2.0.4 release contained a build of the 32-bit Carbon-based IDE. So yes, it was in fact entirely 32-bit, and therefore not compatible with Catalina.

What we're talking about is the IDE built as a 64-bit application, against the Cocoa widgetset instead of Carbon. This is something that already works and has worked for quite a while, regardless of whether or not the Cocoa backend is 100% complete in all regards.

The bottom line is that the Carbon IDE now officially does not work at all with the latest release of OS X, meaning there basically needs to be a Cocoa release ASAP.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: VTwin on October 18, 2019, 02:47:24 am
I appreciate the progress in Lazarus, especially the Cocoa widgetset. I am pleased with the progress in the 2.0 Cocoa fixes branch, but agree with the comments that getting a stable Cocoa installation is a priority. Carbon is no longer viable.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ChrisR on October 18, 2019, 02:24:45 pm
Many of the comments seem to regard installing Lazarus on MacOS Catalina. Thanks to Dmitry, the Cocoa widgets and 64-bit apps is in pretty good shape. The challenge is that when users download the disk image from the main Lazarus page they get a 32-bit version that is not MacOS compliant. A second problem is that it is hard to install the gdb on modern MacOS, and it is not intuitive to new users how to set Lazarus to use LLDB. An improved Disk Image installer would be great, or a streamlined Mac Ports package.

However, one solution not mentioned on this thread is Anthony Walter's clever shell script for guiding Catalina users through an install:
  https://lists.lazarus-ide.org/pipermail/lazarus/2019-October/237082.html
The author clearly asks for testers to give feedback, so perhaps community members who want to see improved Catalina support can provide him with suggestions. From my perspective, it seems like an elegant script that is very close to a one-stop shop for ensuring all the components are installed and in the modern directories.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Dan3468298 on October 18, 2019, 08:34:33 pm
Many of the comments seem to regard installing Lazarus on MacOS Catalina. Thanks to Dmitry, the Cocoa widgets and 64-bit apps is in pretty good shape. The challenge is that when users download the disk image from the main Lazarus page they get a 32-bit version that is not MacOS compliant. A second problem is that it is hard to install the gdb on modern MacOS, and it is not intuitive to new users how to set Lazarus to use LLDB. An improved Disk Image installer would be great, or a streamlined Mac Ports package.

However, one solution not mentioned on this thread is Anthony Walter's clever shell script for guiding Catalina users through an install:
  https://lists.lazarus-ide.org/pipermail/lazarus/2019-October/237082.html
The author clearly asks for testers to give feedback, so perhaps community members who want to see improved Catalina support can provide him with suggestions. From my perspective, it seems like an elegant script that is very close to a one-stop shop for ensuring all the components are installed and in the modern directories.

To sign on Mojave: 
user$ sudo codesign -s gdb-cert /opt/local/bin/ggdb

Worked on Mojave.  Will try on Catalina soon.  This script installs Lazarus 2.1.0
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: cobata on October 19, 2019, 11:20:40 am
I think that it is important this bug to be fixed and taken too:
https://bugs.freepascal.org/view.php?id=33990
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: skalogryz on October 23, 2019, 03:47:08 am
I think that it is important this bug to be fixed and taken too:
https://bugs.freepascal.org/view.php?id=33990
the good news is that we have Ondrej back.
so LCL HighDPI basis can be reconsidered from absolute values to a factor.
This only approach might take care of the issue, as there will no longer be a conflict between system and LCL values

Naturally it will not make it to 2.0.6, but maybe the next one
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: JuhaManninen on October 26, 2019, 08:25:55 am
It would be nice to see the following fixed for this release:   https://bugs.freepascal.org/view.php?id=35572 (https://bugs.freepascal.org/view.php?id=35572)
I was able to fix it. Please test in trunk ASAP. I will try to push it for 2.0.6 if it works. The release is not tagged yet.

I had to debug and scratch my head for some time before I understood the code. Finally I was able to simplify the code a little.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: laguna on October 26, 2019, 01:17:49 pm
Please complete run in Catalina OSX 64 bit

Tanks
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: nanobit on October 26, 2019, 09:36:50 pm
Lazarus fixes (unlike trunk) has this bug:
main.pp: function TMainIDE.DoRunProjectWithoutDebug: TModalResult;
The last "except" should be "finally". (heaptrc is your friend)
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: JuhaManninen on October 27, 2019, 04:29:39 am
Lazarus fixes (unlike trunk) has this bug:
main.pp: function TMainIDE.DoRunProjectWithoutDebug: TModalResult;
The last "except" should be "finally". (heaptrc is your friend)
Which revision in trunk fixed it?
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: nanobit on October 27, 2019, 12:01:16 pm
It looks like revision 60535 (Feb 2019) by mattias
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: useroflazarus on October 28, 2019, 04:42:37 am
2.0.6 final is released  :)
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Thaddy on October 28, 2019, 08:52:12 am
2.0.6 final is released  :)
Not that I am aware of....
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ccrause on October 28, 2019, 10:50:32 am
2.0.6 final is released  :)
Not that I am aware of....
The code has been tagged.  It takes about 3 days from tagging the source until a release is announced (based on the last couple of releases), probably to finalize the different target builds.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: JuhaManninen on October 28, 2019, 02:10:46 pm
It looks like revision 60535 (Feb 2019) by mattias
Too late. It will be in the next major release 2.2.0.
Fortunately it was not a fatal bug. We can live with it.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: ASBzone on October 29, 2019, 05:09:15 pm
It would be nice to see the following fixed for this release:   https://bugs.freepascal.org/view.php?id=35572 (https://bugs.freepascal.org/view.php?id=35572)
I was able to fix it. Please test in trunk ASAP. I will try to push it for 2.0.6 if it works. The release is not tagged yet.

I had to debug and scratch my head for some time before I understood the code. Finally I was able to simplify the code a little.


Thanks, I am only seeing this now, so I will test it in a few days with the expectation that it gets into 2.2.0, since 2.0.6 has already been tagged.
Title: Re: We are planning the next release: Lazarus 2.0.6
Post by: Soner on October 30, 2019, 08:11:02 pm
@Lazarus developers
Maybe you should merge this bugfix for the online package manager.
https://forum.lazarus.freepascal.org/index.php/topic,34297.msg337798.html#msg337798 (https://forum.lazarus.freepascal.org/index.php/topic,34297.msg337798.html#msg337798)