Lazarus

Announcements => Lazarus => Topic started by: Martin_fr on June 06, 2017, 11:48:54 pm

Title: Lazarus Release Candidate 2 of 1.8
Post by: Martin_fr on June 06, 2017, 11:48:54 pm
The Lazarus team is glad to announce the second release candidate of
Lazarus 1.8.

This release was built with FPC 3.0.2.
The previous release Lazarus 1.6.4 was built with FPC 3.0.2 too.
The Linux releases are built with FPC 3.0.3 r36408 due to bug
https://bugs.freepascal.org/view.php?id=31629

Here is the list of fixes for Lazarus 1.8.x:
http://wiki.freepascal.org/Lazarus_1.8_fixes_branch

Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_1.8.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.0.2

The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 1.8 RC2" directory.

Checksums for the SourceForge files:
http://www.lazarus-ide.org/index.php?page=checksums#1_8_0RC2

Minimum requirements:

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.

Mac OS X:
  10.5 to 10.12, LCL only 32bit, non LCL apps can be 64bit.

The svn tag is
http://svn.freepascal.org/svn/lazarus/tags/lazarus_1_8_0_RC2

For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:
ftp://ftp.freepascal.org/pub/lazarus/releases/
and later at (after some time for synchronization)
http://mirrors.iwi.me/lazarus/

== Why should everybody (including you) test the release candidate? ==

In the past weeks the Lazarus team has stabilized the 1.8 fixes branch. The resulting 1.8RC2 is now stable enough to be used by any one for test purposes.

However many of the fixes and new features that where committed since the release of 1.6 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million.

Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it.

Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 1.8.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features.

== How to test ==

Download and install the 1.8 RC2.
- On Windows you can install as a 2ndary install, that will not affect your current install:
  http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus
- On other platforms, if you install to a new location you need to use --primary-config-path

In either case you should make backups. (including your primary config)

Open your project in the current Lazarus (1.6.x), and use "Publish Project" from the project menu. This creates a clean copy of your project.

You can then open that copy in the RC2. Please test:
- If you can edit forms in the designer
   - rename components / change properties in Object inspector / Add new events
   - Add components to form / Move components on form
   - Frames, if you use them
- If you can navigate the source code (e.g. jump to implementation)
- Auto completion in source code
- Compile, debug and run
- Anything else you use in your daily work

Title: Re: Lazarus Release Canditate 2 of 1.8
Post by: ermeneuta on June 07, 2017, 01:12:36 am
I saw a Linux Lazarus V1.9.0  ..... is that a bogus release, or what ?

The About says :

Version #: 1.9.0
Date 2017-05-03
FPC Version: 3.0.2
SVN Revision: 54803
arm-linux-gtk2



Title: Re: Lazarus Release Canditate 2 of 1.8
Post by: Martin_fr on June 07, 2017, 01:50:09 am
1.9.0 is currently trunk. That is the development version with daily (untested) changes.

Versions with an odd digit in 2nd or 3rd are between releases.

1.9.0 => trunk (before branching 1.8, trunk was 1.7)
1.6.5 => development on the 1.6 branch
Title: Re: Lazarus Release Canditate 2 of 1.8
Post by: thijsvandien on June 07, 2017, 03:09:44 am
Just a minor remark not directly related to the RC: both topic titles have 'candidate' misspelt. :)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Martin_fr on June 07, 2017, 04:12:27 am
Fixed, form auto-complete explains the second.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JZS on June 07, 2017, 04:42:36 am
Thank you Lazarus Team.

Your efforts are appreciated.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: ahiggins on June 07, 2017, 11:40:09 am
Great work, many thanks  :)
Title: Re: Lazarus Release Canditate 2 of 1.8
Post by: Zoran on June 07, 2017, 11:58:33 am
I saw a Linux Lazarus V1.9.0  ..... is that a bogus release, or what ?

See http://wiki.lazarus.freepascal.org/Version_Numbering (http://wiki.lazarus.freepascal.org/Version_Numbering)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: bobihot on June 07, 2017, 01:35:26 pm
Thanks,
Run well on Windows and Linux Mint. 1.8RC1 was not linked in Linux.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Eugene Loza on June 07, 2017, 02:46:13 pm
Thanks a lot!!!  :D
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 07, 2017, 04:25:11 pm
Yeah, yeah, yeah !!!   :)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Tommi on June 07, 2017, 06:30:31 pm
This bug : http://forum.lazarus.freepascal.org/index.php/topic,36907.msg248260.html#msg248260 is still alive
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 07, 2017, 08:45:02 pm
This bug : http://forum.lazarus.freepascal.org/index.php/topic,36907.msg248260.html#msg248260 is still alive

Report to mantis with a demo application. Is this a regression?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Tommi on June 07, 2017, 08:53:16 pm
No,it isn't a regression. Ok, I am going to report to mantis
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Tommi on June 07, 2017, 08:55:58 pm
It seems that no forum user is named "mantis"
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Bart on June 07, 2017, 09:04:43 pm
It seems that no forum user is named "mantis"

"mantis" is the bugtracker: http://bugs.freepascal.org/ (http://bugs.freepascal.org/).

Bart
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Edgardo M. López on June 07, 2017, 11:50:00 pm
Hola, al compilar un proyecto fpweb en un servidor apache 2 corriendo en ubuntu 16.04 me da error no definido y la página cgi-bin no funciona.

Hello, when you compile a project fpweb on an apache 2 server running on ubuntu 16.04 gives me undefined error and the page cgi-bin does not work.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: otoien on June 08, 2017, 12:06:51 pm
Small followup from last thread: The setting to keep the IDE coolbar visible (under Options-Environment- IDE Coolbar) is not kept when recompiling for Anchordocking Design layout, even when upgrading from RC1 to RC2. Once changed after recompile it will stick though, so not a real problem.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 08, 2017, 01:00:09 pm
Small followup from last thread: The setting to keep the IDE coolbar visible (under Options-Environment- IDE Coolbar) is not kept when recompiling for Anchordocking Design layout, even when upgrading from RC1 to RC2. Once changed after recompile it will stick though, so not a real problem.
Actually it has been mentioned by many people. Could you please report it in the bug tracker.
It is a weird problem because Anchordocking does not change the IDECoolbar settings in any way.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 08, 2017, 01:36:27 pm
Small followup from last thread: The setting to keep the IDE coolbar visible (under Options-Environment- IDE Coolbar) is not kept when recompiling for Anchordocking Design layout, even when upgrading from RC1 to RC2. Once changed after recompile it will stick though, so not a real problem.
Actually it has been mentioned by many people. Could you please report it in the bug tracker.
It is a weird problem because Anchordocking does not change the IDECoolbar settings in any way.

Anchordocking uses a different desktop from the non-docked environment. It means when switching from non-docked to docked and vice-versa, your desktop(s) get switched as well. So yes, installing AnchorDocking, your IDECoolbar settings are changed (unless both are equal :) ).

AFAIK Michl fixed the issue with corrupted default AnchorDocking desktop. Maybe you have a corrupted AnchorDocking desktop from a previous installation?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 08, 2017, 01:49:20 pm
Anchordocking uses a different desktop from the non-docked environment. It means when switching from non-docked to docked and vice-versa, your desktop(s) get switched as well. So yes, installing AnchorDocking, your IDECoolbar settings are changed (unless both are equal :) ).

AFAIK Michl fixed the issue with corrupted default AnchorDocking desktop. Maybe you have a corrupted AnchorDocking desktop from a previous installation?
Is the fix in 1.8RC2?
I did not test now but earlier I could reproduce the problem. Then I checked that the IDECoolbar visibility setting has default value True everywhere. It means the IDECoolbar should remain visible in new desktop configurations always, AnchorDocking or not, but it didn't.

@otoien, can you reproduce it also with a new clean configuration using 1.8RC2?
A clean configuration eliminates any possible corrupt configuration issues.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: amarryat on June 08, 2017, 02:51:25 pm
Thank you.  This fixed an error I saw in RC1.

I installed and compiled my program on Windows 7 (using 32 bit Lazarus), Fedora 25 32 bit, and Fedora 25 64 bit.  All fine.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 08, 2017, 03:00:22 pm
Is the fix in 1.8RC2?

Yes, it was already in 1.7: https://mantis.freepascal.org/view.php?id=31084 (https://mantis.freepascal.org/view.php?id=31084)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 08, 2017, 03:49:02 pm
Yes, it was already in 1.7: https://mantis.freepascal.org/view.php?id=31084 (https://mantis.freepascal.org/view.php?id=31084)
That must be a different problem then.
I just tested with Lazarus trunk on Linux. I started it like:
Code: Pascal  [Select][+][-]
  1. $ ./lazarus --pcp=~/.lazarus_test &
The directory "~/.lazarus_test" did not exist before this test, so we are talking about a clean configuration.
IDECoolbar was visible as expected. Then I installed AnchorDockingDsgn and rebuilt.
A docked IDE started but IDECoolbar was not there. I went to Environment -> "IDE Coolbar" options. The "Coolbar is visible" checkbox was not checked. This is the same behavior I saw already a long time ago.
Then I checked the checkbox manually and clicked OK. To my surprice IDECoolbar still was not visible. Finally I figured it was there but its width was zero. I had to grab and move the component palette to reveal IDECoolbar.
The IDE is built with QT bindings but I remember the widgetset has no effect on this issue.

Ondrej, can you reproduce?

[Edit] The "Coolbar is visible" setting is cleared every time when I switch using a docked IDE, meaning every time I install AnchorDocking from an IDE that didn't have it.
I am keeping the same ~/.lazarus_test configuration when testing it.
In the old docked IDE I had set the IDECoolbar visible. The setting should be waiting there but it is not.
When I remove AnchorDocking, rebuild, then install AnchorDocking again, somewhere the visibility setting is cleared actively. It is not an uninitialized variable or corrupt configuration.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Michl on June 08, 2017, 04:14:25 pm
@Juha: I can have a look at this issue. I know that problem, as I use always AnchorDockingDsgn and SpartaDockedFormEditor. For me till now, it was a very minor problem, as one click after a fresh install in project options (Tools -> Options ... -> IDE Coolbar -> Button "Restore defaults") solves it. This works for me all the time.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 08, 2017, 04:20:15 pm
@Juha: I can have a look at this issue.
Thanks.

Quote
I know that problem, as I use always AnchorDockingDsgn and SpartaDockedFormEditor. For me till now, it was a very minor problem, as one click after a fresh install in project options
It may be a bigger problem for new users who don't know about the issue, or for users who like to switch between docked and non-docked IDE.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: mercury on June 08, 2017, 04:30:13 pm
1. Where is precompiled qt5pas.dll?
2. No QWebEngine binding in qt56.pas?
3. I don’t like the new icons, any way to switch back?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: zeljko on June 08, 2017, 04:47:20 pm
1. Where is precompiled qt5pas.dll?
2. No QWebEngine binding in qt56.pas?
3. I don’t like the new icons, any way to switch back?

1.I'll commit qt5pas1.dll in binaries/i386-win32/qt next week (mingw build),
2.QWebEngine isn't yet inside bindings because I must create all stuff manually since I don't any scripts for
automatic bindings creation, on the other side QWebKit is deprecated so that's the reason why it's moved away from
bindings.
3.Don't know
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 08, 2017, 04:47:53 pm
3. I don’t like the new icons, any way to switch back?

No, Lazarus moves only forward, no step back :)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 08, 2017, 06:29:59 pm
@Juha: I can have a look at this issue. I know that problem

Thanks. In this case, please reopen the issue https://mantis.freepascal.org/view.php?id=29863 (https://mantis.freepascal.org/view.php?id=29863) and assign it to yourself. I though the issue was solved - I must have checked wrongly.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Michl on June 08, 2017, 11:47:58 pm
@Juha: I can have a look at this issue.
Thanks.

Quote
I know that problem, as I use always AnchorDockingDsgn and SpartaDockedFormEditor. For me till now, it was a very minor problem, as one click after a fresh install in project options
It may be a bigger problem for new users who don't know about the issue, or for users who like to switch between docked and non-docked IDE.
It is fixed in trunk revision 55269 and requested for merge in 1.8: https://bugs.freepascal.org/view.php?id=31981 (https://bugs.freepascal.org/view.php?id=31981)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 09, 2017, 12:48:42 am
It is fixed in trunk revision 55269
Cool! The Coolbar indeed stays visible now.
I still don't quite understand what happened. Why it affected only the IDECoolbar visibility option and no others? Defaults are set also for docked desktop, right?
I would need to debug the code to understand.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Phil on June 09, 2017, 02:32:44 am
Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it.

I trust that these regressions will be fixed before 1.8 ships. They're still there in RC2. Worked fine in 1.6.4.

https://bugs.freepascal.org/view.php?id=31912

https://bugs.freepascal.org/view.php?id=31908

I don't see any fixes to Carbon or Cocoa widgetsets in RC2 since early April.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: ps on June 09, 2017, 06:49:36 am
I don't see any fixes to Carbon or Cocoa widgetsets in RC2 since early April.

Maybe Lazarus for macOS is dead, this is last year for Carbon 32bits aps and still not full working Cocoa.  :(

https://www.macrumors.com/2017/06/06/apple-to-phase-out-32-bit-mac-apps/
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 09, 2017, 08:03:12 am
Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it.

I trust that these regressions will be fixed before 1.8 ships. They're still there in RC2. Worked fine in 1.6.4.

https://bugs.freepascal.org/view.php?id=31912

https://bugs.freepascal.org/view.php?id=31908

I don't see any fixes to Carbon or Cocoa widgetsets in RC2 since early April.

Unfortunately there is no active macOSX LCL/Lazarus maintainer. I have very limited debug possibilities. (I have no Mac hardware.) We need your help.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: tudi_x on June 09, 2017, 08:15:47 am
hi,
what kind of specs you would need for a mac os test machine?
would it be useful if you could connect remotely?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 09, 2017, 08:37:41 am
hi,
what kind of specs you would need for a mac os test machine?

Nothing special - just to be able to run the Lazarus trunk via SVN.

would it be useful if you could connect remotely?

IMO yes, I can try.

To be honest, I have no deep experience with Carbon/Cocoa, so probably it would be better if somebody with Carbon experience would take a look at the issue. I assume it is due to the LCL internal DPI change from 72 to 96: http://wiki.freepascal.org/Lazarus_1.8.0_release_notes#DPI_value_change_for_all_Mac_OSX_widget_sets (http://wiki.freepascal.org/Lazarus_1.8.0_release_notes#DPI_value_change_for_all_Mac_OSX_widget_sets).
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Handoko on June 09, 2017, 10:41:30 am
I've just downloaded and tried Lazarus 1.8.0RC2. I installed it using 3 deb files downloaded from SourceForge. And I found some issues.

Note: I use Ubuntu Mate 16.10 64-bit.

When installing FPC, I got "".Error: Breaks existing package 'fpc' conflict: fpc (). I had Lazarus 1.6.4 installed previously but I have uninstalled it and renamed the ".lazarus" in my home folder before I installed 1.8.0RC2. This issue can be ignored and no serious problem will happen.

The Source Editor is (almost) unusable to me. If I type "Begin", the result will be "BBeeggiinn". This is bad, hope it can be fixed soon.

I have discussed the issues on other thread:
http://forum.lazarus.freepascal.org/index.php/topic,37022.msg247603.html#msg247603
Note: Issue #2 and #3 didn't happen on my test on RC2.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 09, 2017, 11:07:33 am
The Source Editor is (almost) unusable to me. If I type "Begin", the result will be "BBeeggiinn". This is bad, hope it can be fixed soon.
That is related to input methods with GTK2 and certain desktop systems. There are workarounds to fix it.
See this and the related issues:
 https://bugs.freepascal.org/view.php?id=30863

One "fix" is also to build Lazarus with QT bindings.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ñuño_Martínez on June 09, 2017, 11:14:59 am
The Source Editor is (almost) unusable to me. If I type "Begin", the result will be "BBeeggiinn". This is bad, hope it can be fixed soon.
Almost all Lazarus versions have that problem in their first releases.  And yes, it is a problem with GTK+.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 09, 2017, 11:32:02 am
Almost all Lazarus versions have that problem in their first releases.  And yes, it is a problem with GTK+.
What does that mean? It has not been fixed in the following releases either.
Yes, it is a nasty interaction with GTK+, input method, desktop and OS combinations. It can be seen as a downside of having so many distributions and variations there.
You can fix it in your particular system by tweaking input method settings. I personally don't know details of it. I use KDE and have never seen such problems. I have used XFCE, too, but didn't see the problems then either.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Handoko on June 09, 2017, 11:40:17 am
The Source Editor is (almost) unusable to me. If I type "Begin", the result will be "BBeeggiinn". This is bad, hope it can be fixed soon.
Almost all Lazarus versions have that problem in their first releases.  And yes, it is a problem with GTK+.

I never had this issue until 1.8.0.

Anyway, I noticed the font in Source Editor is hard to read. See the image below, the upper image is Lazarus 1.6.4 and the lower one Lazarus 1.8.0RC2. It is not a serious problem because I can change the font, but I think I should report it here.

Also, why by default the line number is turn off?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 09, 2017, 12:11:38 pm
Anyway, I noticed the font in Source Editor is hard to read. See the image below, the upper image is Lazarus 1.6.4 and the lower one Lazarus 1.8.0RC2. It is not a serious problem, but I think I should report it here.
Also, why by default the line number is turn off?
You have different editor settings, including font, between those two for whatever reason.
The 1.8 version itself does not cause so big changes.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ñuño_Martínez on June 09, 2017, 01:01:27 pm
Almost all Lazarus versions have that problem in their first releases.  And yes, it is a problem with GTK+.
What does that mean?
I had that problem (duplicated characters when writting) in almost all versions since 1.0 'til 1.6, in Fedora, Lubuntu and Xubuntu.  The fix in all cases was to wait until an update fixed it (don't ask me who and how, but somebody did).  I didn't test 1.8 yet (and I'll don't until version 1.8.1*) so I can't say if I have te same problem right now.
_____________________________________

* In most cases I never use the "just released" version of open source software.  I try to wait until the "dot one" version is out.  This is just because I'm very bad evaluating and explaining other people bugs (specially in English) .  I hope this doesn't sound too selfish, it is not my intention.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Handoko on June 09, 2017, 01:10:48 pm
@JuhaManninen

I use Ubuntu Mate and I found Lazarus keeps its editor settings in "/home/.lazarus". I removed that folder (after I made a backup) and tested both Lazarus 1.6.4 and 1.8.0RC2 several times. The results are same:

- Lazarus 1.6.4 (for Linux) uses DejaVu Sans Mono as default editor font if the ".lazarus" folder cannot be found (deleted).

- Lazarus 1.8.0RC2 (for Linux) uses -adobe-courier-medium-r-normal-*-*-*-*-*-*-*-iso10646-1 as default editor font if the ".lazarus" folder cannot be found (deleted). And the show line numbers option is not checked.

The tests were performed on Ubuntu Mate 16.10 64-bit.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 09, 2017, 03:30:32 pm
... Lazarus keeps its editor settings in "/home/.lazarus".
Actually it is "/home/handoko/.lazarus" if your user name is "handoko".

Quote
I removed that folder (after I made a backup) and tested both Lazarus 1.6.4 and 1.8.0RC2 several times. The results are same:
- Lazarus 1.6.4 (for Linux) uses DejaVu Sans Mono as default editor font if the ".lazarus" folder cannot be found (deleted).
- Lazarus 1.8.0RC2 (for Linux) uses -adobe-courier-medium-r-normal-*-*-*-*-*-*-*-iso10646-1 as default editor font if the ".lazarus" folder cannot be found (deleted). And the show line numbers option is not checked.
Ok, that sounds serious.

Do you use AnchorDocking? Not sure from the screenshot.
First please test without AnchorDocking. Do you still have the same problems?

Then test with trunk after revisions r55269 + r55277. They fixed issue:
 https://bugs.freepascal.org/view.php?id=31981
which was about wrong options for a docked IDE. This issue could be related. The revisions will be merged to fixes_1_8.
--- Ok, this affects only if you used AnchorDocking. ---

If the given revisions do not help, then please report with steps to reproduce.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Handoko on June 09, 2017, 03:53:22 pm
... Lazarus keeps its editor settings in "/home/.lazarus".
Actually it is "/home/handoko/.lazarus" if your user name is "handoko".
Sorry, my mistake.

No, I don't use AnchorDocking. Those screenshots were taken right after Lazarus installed (without any option changed nor any extra package installed).

I searched the text "-adobe-courier-medium-r-normal-*-*-*-*-*-*-*-iso10646-1" and I found it in [lazarus_source]/components/synedit/synedit.pp:

Code: Pascal  [Select][+][-]
  1. // synedit.pp
  2. procedure InitSynDefaultFont;
  3. begin
  4.   if SynDefaultFontName <> '' then exit;
  5.   Screen.Fonts;
  6.   {$UNDEF SynDefaultFont}
  7.   {$IFDEF LCLgtk}
  8.     SynDefaultFontName   := '-adobe-courier-medium-r-normal-*-*-140-*-*-*-*-iso10646-1';
  9.     SynDefaultFontHeight := 14;
  10.     {$DEFINE SynDefaultFont}
  11.   {$ENDIF}
  12.   {$IFDEF LCLcarbon}
  13.     SynDefaultFontName   := 'Monaco'; // Note: carbon is case sensitive
  14.     SynDefaultFontHeight := 12;
  15.     {$DEFINE SynDefaultFont}
  16.   {$ENDIF}
  17.   // LCLgtk2 and LCLQt use default settings
  18.   {$IFnDEF SynDefaultFont}
  19.     SynDefaultFontName   := 'Courier New';
  20.     SynDefaultFontHeight := -13;
  21.   {$ENDIF}
  22.   if Screen.Fonts.IndexOf(SynDefaultFontName) >= 0 then
  23.     exit;
  24.   if Screen.Fonts.IndexOf('DejaVu Sans Mono') >= 0 then begin
  25.     SynDefaultFontName   := 'DejaVu Sans Mono';
  26.     SynDefaultFontHeight := 13;
  27.   end;
  28. end;

But InitSynDefaultFont in both my version 1.6.4 and 1.8.0RC2 are same. My computer has DejaVu Sans Mono installed. I guess Lazarus 1.8.0RC2 failed to detect DejaVu Sans Mono in my system or maybe failed to save it to my editoroptions.xml.

This is my editoroptions.xml right after Lazarus 1.6.4 installed:
Quote
<?xml version="1.0" encoding="UTF-8"?>
<CONFIG>
  <EditorOptions Version="11">
    <Display DoNotWarnForFont="DejaVu Sans Mono"/>
    <KeyMapping>
      <default>
        <Version Value="6"/>
      </default>
    </KeyMapping>
    <CodeTools CodeTemplateFileName="/home/handoko/.lazarus/lazarus.dci" CompletionLongLineHintTypeCompletionLongLineHintType="sclpExtendRightOnly"/>
    <Mouse>
      <Default Version="1"/>
    </Mouse>
    <Color Version="11"/>
  </EditorOptions>
</CONFIG>

And this is my editoroptions.xml right after Lazarus 1.8.0RC2 installed:
Quote
<?xml version="1.0"?>
<CONFIG>
  <EditorOptions Version="2">
    <Display EditorFont="-adobe-courier-medium-r-normal-*-*-*-*-*-*-*-iso10646-1" ExtraLineSpacing="2"/>
  </EditorOptions>
</CONFIG>
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 09, 2017, 04:21:19 pm
@Handoko, that is weird. Can anybody else reproduce?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: mattias on June 09, 2017, 04:34:14 pm
The "-adobe-courier-medium-r-nor..." comes from the default /etc/lazarus/editoroptions.xml, since Lazarus svn revision 16920, which means ages.
1.6.4 should have the same. Strange that you see a difference.
This default is no longer needed. I will remove it.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Handoko on June 09, 2017, 05:19:51 pm
Yes I found it in my /etc/lazarus.

I did a test again and this are the steps and result:
01. Tested on my Ubuntu Mate 16.10 64-bit.
02. I deleted both my "/etc/lazarus" and "/home/handoko/.lazarus" folders.
03. Started my Lazarus 1.6.4 and quit.
04. Lazarus 1.6.4 created the missing configuration files automatically.
05. But Lazarus 1.6.4 didn't create "/etc/lazarus".
06. I uninstall Lazarus 1.6.4 (also FPC, FPC-source).
07. I deleted my "/home/handoko/.lazarus".
08. I installed Lazarus 1.8.0RC2 using deb files.
09. Started Lazarus 1.8.0RC2 and quit.
10. Lazarus 1.8.0RC2 created the missing configuration files automatically (See #4)
11. Lazarus 1.8.0RC2 created "/etc/lazarus/editoroptions.xml" (See #5)
12. Lazarus 1.8.0RC2 did not use DejaVu Sans Mono font.
13. I exited Lazarus 1.8.0RC2.
14. I deleted both my "/etc/lazarus" and "/home/handoko/.lazarus" folders.
15. I started 1.8.0RC2 again.
16. Lazarus 1.8.0RC2 created the missing configuration files automatically (See #10)
17. Lazarus 1.8.0RC2 did not created "/etc/lazarus" (See #11)
18. Lazarus 1.8.0RC2 now use DejaVu Sans Mono font (See #12)

Isn't it strange?  %)

Edit:
My problem has solved, but the bug is still there. Also the Gtk input issue still not fixed.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 09, 2017, 10:38:32 pm
Can you people reproduce this with RC2?
 https://bugs.freepascal.org/view.php?id=31995

[Edit] Ok, it was fixed already but not backported to fixes_1_8 branch.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: otoien on June 10, 2017, 09:15:49 am
Anchordocking uses a different desktop from the non-docked environment. It means when switching from non-docked to docked and vice-versa, your desktop(s) get switched as well. So yes, installing AnchorDocking, your IDECoolbar settings are changed (unless both are equal :) ).

AFAIK Michl fixed the issue with corrupted default AnchorDocking desktop. Maybe you have a corrupted AnchorDocking desktop from a previous installation?
Is the fix in 1.8RC2?
I did not test now but earlier I could reproduce the problem. Then I checked that the IDECoolbar visibility setting has default value True everywhere. It means the IDECoolbar should remain visible in new desktop configurations always, AnchorDocking or not, but it didn't.

@otoien, can you reproduce it also with a new clean configuration using 1.8RC2?
A clean configuration eliminates any possible corrupt configuration issues.

I got busy with other things so I am late to this and it looks  from the other posts like this has been fixed, but I tried the clean install (Lazarus uninstalled all settings removed) in a VM anyway and can confirm the behavior. After ticking on the visible option, the coolbar does not immediately show up, but does so after a restart of Lazarus.
Title: Lazarus Release Candidate 2 of 1.8
Post by: chayimamaral on June 10, 2017, 04:42:55 pm
Can't debug on Sierra 10.12.5
Can't debug on Windows 10
Can't read libpq.dll (Postres 9.4) on Windows 10.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Phil on June 10, 2017, 04:45:33 pm
Can't debug on Sierra 10.12.5

For the foreseeable future, I would recommend creating a "dummy" Xcode project for your Lazarus project and debugging with lldb in Xcode. Here's how:

https://macpgmr.github.io/ObjP/ProjectXC.html
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Martin_fr on June 11, 2017, 04:51:00 am
Can't debug on Sierra 10.12.5
Can't debug on Windows 10
Can't read libpq.dll (Postres 9.4) on Windows 10.

Are those problems new in 1.8, or already present in 1.6.4?

On Windows, is that every app (e.g, a Form with a Button1Clicked doing Caption:='foo':)?
Or only more complex apps?
Or only apps with libpg.

You might try some of those (win):
- http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#gdb.exe_has_stopped_working
- In Project settings, under debugging change "debug type info" between "stabs" and "dwarf 2 with sets"
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: matthius on June 11, 2017, 11:33:32 am
I have a linking error on qt5 with Ancestromania.
I have started lazarus with terminal, showing nothing new.
I had to create qt5 directories on virtualtreeview and lclextension.

https://bitbucket.org/matthieugiroux/ancestromania-gpl-fully-lazarus-genealogy-project (https://bitbucket.org/matthieugiroux/ancestromania-gpl-fully-lazarus-genealogy-project)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: amarryat on June 12, 2017, 11:17:27 pm
Drag a TAChart onto a form.

A range check error popup occurs.

Windows 7.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: wp on June 12, 2017, 11:46:43 pm
Drag a TAChart onto a form.

A range check error popup occurs.

Read this: http://forum.lazarus.freepascal.org/index.php/topic,37163.0.html
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 13, 2017, 09:50:06 am
Drag a TAChart onto a form.

A range check error popup occurs.

Read this: http://forum.lazarus.freepascal.org/index.php/topic,37163.0.html

Thanks wp for merging it to fixes for the RC3. I must have added r55098 directly to "Fixes for 1.8 RC2 (merged)" instead of to "merge requests". My mistake :/
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: michaelthuma on June 14, 2017, 09:25:49 am
The problem affects the source editor.

Just for the sake of completeness ..

That problem is caused by XIM and yes the problem did exist before too under Unbuntu

echo $GTK_IM_MODULE
im-config
have a look at .xinitrc

I simply removed this specific setting using im-config simply by configuring no input method so Ubuntu defaulted to iBUS which is more or less a SCIM

https://wiki.ubuntu.com/InputMethods/SCIM/Setup (https://wiki.ubuntu.com/InputMethods/SCIM/Setup)

https://unix.stackexchange.com/questions/260601/understanding-setting-up-different-input-methods (https://unix.stackexchange.com/questions/260601/understanding-setting-up-different-input-methods)



---

The package conflict doesn't matter. Agree, it's little confusing.

--

Debugger under 64-bit Linux. Turn off optimisation otherwise debugger stops working when it comes to more complex datatypes.

The font is grey - really not the best choice.




I've just downloaded and tried Lazarus 1.8.0RC2. I installed it using 3 deb files downloaded from SourceForge. And I found some issues.

Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jujibo on June 14, 2017, 10:01:36 am
Package sparta_dockedformeditor fails to compile because requires sparta_MDI and it has been removed.

branches/fixes_1_8
Rev: 55345

Note: Fixed in rev. 55350  Thanks.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 14, 2017, 06:27:28 pm
Hi all,
first i want to thank the whole team for this excellent piece of software.

I really like to work with it.

Now I stumbled on something, maybe It's something old, maybe something went wrong with my version ... but I could verify it with the released version:
I use the x86_64 version on win10:
I write :
Code: [Select]
{$IfOpt H-}S{$Else}PChar(S){$EndIf} ... and I set the cursor on $else then I press [Ctrl]-[Space] for the List of options
then I use the cursor-keys to set the cursor on PChar and press [Space] i get:
Code: [Select]
{$IfOpt H-}S{$Else}ElseIf(S){$EndIf}I expected the list to close or to show options about PChar but not that. Is it something new or something old ? Is it a Bug ? Will it be fixed ?

Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 15, 2017, 12:06:01 am
Whole project compiles even though source code is "blue".
There's one bracket too much in line 64, pos 1 ..

Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 15, 2017, 12:09:52 am
Example :

Code: Pascal  [Select][+][-]
  1. unit Unit1;
  2.  
  3. {$mode objfpc}{$H+}
  4.  
  5. (***************************************************)
  6. (*    comments ..
  7.  
  8. (***************************************************)
  9.  
  10. interface
  11.  
  12. uses
  13.   Classes, SysUtils;
  14.  
  15. implementation
  16.  
  17. end.
  18.  
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 15, 2017, 10:43:15 am
The validity of your code depends on the "nested comments" FPC option.
IIRC both CodeTools and the editor highlighting are clever enough to respect that option.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 15, 2017, 11:40:10 am
The validity of your code depends on the "nested comments" FPC option.
IIRC both CodeTools and the editor highlighting are clever enough to respect that option.

Hm. I installed Lazarus 1.8RC2, clean.
Nice to hear that the validity of code
depends on the "nested comments" FPC option.
But I didn't change any settings.  %)

Well, I thought, blue lines  are - always - just comments, not valid code ?
I never saw Lazarus accepting and compiling blue code lines ...  :o
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 15, 2017, 12:33:54 pm
Ok, there is no specific compiler option for nested comments but it is included in modes.
{$mode objfpc} supports nested comments while {$mode delphi} does not.
{$MODESWITCH NESTEDCOMMENTS} can be used in source code, too.

However there seems to be a compiler bug when '(*...*)' style comments are used. Nesting is not recognized then. To test, put an intentional syntax error into your unit's implementation section and compile.
With '{...}' style comments everything works.
Lazarus syntax highlighting works as intended with both styles.

Please report the FPC bug. I found only one existing open report about nested comments but it is not related.
  https://bugs.freepascal.org/view.php?id=4587
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Zoran on June 15, 2017, 12:40:02 pm
This really seems to be a compiler bug. This works, while it shouldn't with this switch turned on:

Code: Pascal  [Select][+][-]
  1. program Project1;
  2.  
  3. {$ModeSwitch nestedcomments+}
  4.  
  5. (*
  6. (***)
  7.  
  8. begin
  9.   writeln('see');
  10.   readln;
  11. end.
  12.  

But, if you change the middle asterisk in second commented line to anything else, it (correctly) does not compile:
Code: Pascal  [Select][+][-]
  1. program Project1;
  2.  
  3. {$ModeSwitch nestedcomments+}
  4.  
  5. (*
  6. (*a*)
  7.  
  8. begin
  9.   writeln('see');
  10.   readln;
  11. end.
  12.  

In these tests, modeswitch directive can be replaced with {$mode objfpc},  behaves same.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Zoran on June 15, 2017, 12:54:08 pm
I reported: https://bugs.freepascal.org/view.php?id=32019
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 15, 2017, 01:00:41 pm
I reported: https://bugs.freepascal.org/view.php?id=32019
Thanks !
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Eugene Loza on June 16, 2017, 09:33:16 am
As strange as it goes, when I copy something from Lazarus (1.8.0RC2 64 bit * Debian Jessie 64 bit) it adds a "sharp" symbol (#) in the end:
Code: Pascal  [Select][+][-]
  1. if not isLoaded then begin
  2.   WriteLnLog('DMusicTrack.Start','ERROR: Music is not loaded!');
  3.   exit;
  4. end;#
The symbol is not visible when pasted in Lazarus, but appears when pasting into other app.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 18, 2017, 12:30:25 am
I currently work on lots of dialogs in my large project,
[shift]-[F12] shows up the list.

This windows doesn't remember it's position
and called again, always overlays the sourcecode editor window.
I now always have to drag it to the right again ..

Is it possible anyhow to make it remember it's last used position ?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: balazsszekely on June 18, 2017, 08:05:22 am
@PeterX
Quote
currently work on lots of dialogs in my large project,
[shift]-[F12] shows up the list.

This windows doesn't remember it's position
and called again, always overlays the sourcecode editor window.
I now always have to drag it to the right again ..

Is it possible anyhow to make it remember it's last used position ?

1. Open ViewUnit_Dlg.pp (IDE subfolder, Lazarus directory)
2. Change Position from poScreenCenter to poDesigned
3. Move the form to desired position
4. Rebuild the IDE(MainMenu-->Tools-->Build Lazarus with profile: Normal IDE
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 18, 2017, 11:05:19 am
I currently work on lots of dialogs in my large project, [shift]-[F12] shows up the list.

This windows doesn't remember it's position and called again, always overlays the sourcecode editor window.
I now always have to drag it to the right again ..
That is a bug. Most IDE windows have these calls:
Code: Pascal  [Select][+][-]
  1.   IDEDialogLayoutList.ApplyLayout(Self);
  2.   IDEDialogLayoutList.SaveLayout(Self);
when opening / closing the window. The purpose is to remember the window position and size.
I tested with many windows, the same bug is there.

It may have been there for some time. Did it work with Lazarus 2.6.4 1.6.4?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: taazz on June 18, 2017, 11:19:32 am
It may have been there for some time. Did it work with Lazarus 2.6.4?
lazarus 1.4.4 exhibits the same behavior. Pressing shift+f12 opens the dialog in the center of the screen. moving it anywhere of center and closing and next time it will reopen on the center of the screen. Personally I prefer the current behavior, its a dialog and it should always open and close on the same spot regardless of user actions. It is not a floating toolbar that it should intergrade with the applications layout.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 18, 2017, 11:47:05 am
Personally I prefer the current behavior, its a dialog and it should always open and close on the same spot regardless of user actions. It is not a floating toolbar that it should intergrade with the applications layout.
Ok, that is a valid point, too. Maybe it should be one more option.
Anyway the code does not do what it is intended to do. I try to figure out later what happens there.
It will not affect Lazarus 1.8 though.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 18, 2017, 02:53:22 pm
Pressing shift+f12 opens the dialog in the center of the screen.
But it remembers Width and Height. So Position is the only thing that gets lost.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 18, 2017, 03:31:40 pm
Pressing shift+f12 opens the dialog in the center of the screen.
But it remembers Width and Height. So Position is the only thing that gets lost.
Actually it is a feature, not a bug.
Class TIDEDialogLayout has properties Width and Height but no Top and Left.
They should be added IMO, and maybe an option for restoring the position added.
If somebody makes a patch we can have it soon. Otherwise I can look at it later.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 18, 2017, 07:38:44 pm
Speaking of the IDE-Macros, is it right that
$(ProjOutDir) as well as $Project(OutputDir) are pointing to the Units-Output Directory, and there is no macro pointing to the Directory of the executable-binary ?
In my Opinion one of them ($Project(OutputDir))should point to the directory of the executable.
Or is there a reason why there is no macro to the executable-directory ?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: taazz on June 18, 2017, 08:06:46 pm
Speaking of the IDE-Macros, is it right that
$(ProjOutDir) as well as $Project(OutputDir) are pointing to the Units-Output Directory, and there is no macro pointing to the Directory of the executable-binary ?
In my Opinion one of them ($Project(OutputDir))should point to the directory of the executable.
Or is there a reason why there is no macro to the executable-directory ?
project is not the executable, and the project's output directory is the units output directory see attachment. I guess you are searching for the target's directory
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: PeterX on June 18, 2017, 10:50:55 pm
Pressing shift+f12 opens the dialog in the center of the screen.
But it remembers Width and Height. So Position is the only thing that gets lost.
Actually it is a feature, not a bug.
Class TIDEDialogLayout has properties Width and Height but no Top and Left.
They should be added IMO, and maybe an option for restoring the position added.
If somebody makes a patch we can have it soon. Otherwise I can look at it later.

I would never have come across that, but yesterday + today I opened
most of the more than 100 dialog templates in my large project to check + repair.
So, because it was time consuming, always dragging this window to the right,
I would very much appreciate this feature enhancement ..  :)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 19, 2017, 12:43:12 am
project is not the executable, and the project's output directory is the units output directory see attachment. I guess you are searching for the target's directory
Thanks that was the clue i needed
SOLUTION
But it's more complicated than I thought
I need $Path($(TargetFile))\$NameOnly($(TargetFile)).new to get the equivilent of ChangeFileExt
$(TargetFile)  is replaced by the full Target (incl.path & extension) (Thanks to Taazz for pointing me to the right direction
$Path($(TargetFile))  gives the path of the target
$NameOnly($(TargetFile)) gives the Name (without ext) of the target
$Name($(TargetFile)) would give the Name with extension of the target.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 20, 2017, 09:20:13 am
As strange as it goes, when I copy something from Lazarus (1.8.0RC2 64 bit * Debian Jessie 64 bit) it adds a "sharp" symbol (#) in the end:
Code: Pascal  [Select][+][-]
  1. if not isLoaded then begin
  2.   WriteLnLog('DMusicTrack.Start','ERROR: Music is not loaded!');
  3.   exit;
  4. end;#
The symbol is not visible when pasted in Lazarus, but appears when pasting into other app.
Is it related to this issue?
 https://bugs.freepascal.org/view.php?id=21453
Can you copy/paste between 2 Lazarus instances?
Please see also:
  http://forum.lazarus-ide.org/index.php/topic,37097.msg248196.html#msg248196
What happens if you build Lazarus with GTK_REMOVE_CLIPBOARD_NULL?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: ps on June 20, 2017, 10:30:23 pm
Mac OS X:
  10.5 to 10.12, LCL only 32bit, non LCL apps can be 64bit.
This is end of macOS support? "From January next year, all new apps must support 64-bit". MacOS High Sierra will be the last version to support 32-bit apps.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Eugene Loza on June 21, 2017, 03:20:03 am
Is it related to this issue?
 https://bugs.freepascal.org/view.php?id=21453
Sorry, I can't tell if it does. I don't have a clipboard hex analyzer... And have no idea where to get one.
I have a CLIPMAN installed in Debian+XFCE, however, it looks inactive unless launched manually. And it doesn't show # in the end.

WAIT???? WHERE DID # GO????
It was just here a week ago. I didn't change anything (just updated the OS packages)
It's no more here when I paste something.

FOUND IT.
It only appears when pasting into LibreOffice. Now I remember that was the case - I didn't think to check it.

Quote
Can you copy/paste between 2 Lazarus instances?
Everything works perfectly. (UPD: it was working prior to next step.)
As I've just found out the problem relates only to LibreOffice.

Quote
Please see also:
  http://forum.lazarus-ide.org/index.php/topic,37097.msg248196.html#msg248196
What happens if you build Lazarus with GTK_REMOVE_CLIPBOARD_NULL?
Yes, that fixed the # symobl perfectly.
LibreOffice now doesn't add # in the end.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Eugene Loza on June 21, 2017, 03:30:05 am
Quote
Please see also:
  http://forum.lazarus-ide.org/index.php/topic,37097.msg248196.html#msg248196
What happens if you build Lazarus with GTK_REMOVE_CLIPBOARD_NULL?
Yes, that fixed the # symobl perfectly.
LibreOffice now doesn't add # in the end.
BUT!
Now I can't copy-paste between Lazarus instances.  %)
(Just as you've suggested in the forum link)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 21, 2017, 06:54:09 am
Hi all,
first i want to thank the whole team for this excellent piece of software.

I really like to work with it.

Now I stumbled on something, maybe It's something old, maybe something went wrong with my version ... but I could verify it with the released version:
I use the x86_64 version on win10:
I write :
Code: [Select]
{$IfOpt H-}S{$Else}PChar(S){$EndIf} ... and I set the cursor on $else then I press [Ctrl]-[Space] for the List of options
then I use the cursor-keys to set the cursor on PChar and press [Space] i get:
Code: [Select]
{$IfOpt H-}S{$Else}ElseIf(S){$EndIf}I expected the list to close or to show options about PChar but not that. Is it something new or something old ? Is it a Bug ? Will it be fixed ?
No comments ? Is it wanted that way ? Can someone confirm this behaviour ?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 21, 2017, 07:22:33 am
Then test with trunk after revisions r55269 + r55277. They fixed issue:
 https://bugs.freepascal.org/view.php?id=31981 (https://bugs.freepascal.org/view.php?id=31981)
which was about wrong options for a docked IDE. This issue could be related. The revisions will be merged to fixes_1_8.
No it isn't, when loading lazarus default (no-AD) all AD-desktop-settings are deleted (they only should be deactivated). I don't thonk that it ever worked, so it maybe not a bug related to 1.8rc2, but would be a C.o.o.l. (see ([spoiler] scroll code to end): http://forum.lazarus.freepascal.org/index.php/topic,37229.msg249746.html#msg249746  ) if it's fixed in the 1.8 final.
I send a request to Bug-Reports accordingly.
If the given revisions do not help, then please report with steps to reproduce.
I just did.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Michl on June 21, 2017, 08:58:35 am
Then test with trunk after revisions r55269 + r55277. They fixed issue:
 https://bugs.freepascal.org/view.php?id=31981 (https://bugs.freepascal.org/view.php?id=31981)
which was about wrong options for a docked IDE. This issue could be related. The revisions will be merged to fixes_1_8.
No it isn't, when loading lazarus default (no-AD) all AD-desktop-settings are deleted (they only should be deactivated).
I just tested the issue again. In my point of view it is working correct:

If you make changes in a undocked (default) IDE in the settings, these settings are taken to a initially docked desktop after installing package AnchorDockedDsgn. You can now make changes in this new created (default docked) desktop. The last unused (default) desktop isn't deleted and not changed (see Mainmenu -> Tools -> Desktops ...).

If you now uninstall package AnchorDockedDsgn, the previous default desktop is loaded again. The docked desktops are deleted and this is correct, as they come with the package AnchorDockedDsgn (all things that a package installs have to be removed, if the package is uninstalled).

If you later want to reuse docked settings, you have do export and import these docked desktops. Of course this is not working now (https://bugs.freepascal.org/view.php?id=29200 (https://bugs.freepascal.org/view.php?id=29200)). So the current workaround is to make a copy of your environmentoptions.xml and use it after reinstalling AnchorDockedDsgn, don't uninstall that package or adapt your divergent settings from your default desktop after package reinstalling.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: SunyD on June 21, 2017, 12:27:50 pm
Speaking of the IDE-Macros, is it right that
$(ProjOutDir) as well as $Project(OutputDir) are pointing to the Units-Output Directory, and there is no macro pointing to the Directory of the executable-binary ?
In my Opinion one of them ($Project(OutputDir))should point to the directory of the executable.
Or is there a reason why there is no macro to the executable-directory ?
I am using this in tools menu:
Project output path(exe directory):
$Path($TargetFile())

Current editorfile path:
$Path($EdFile())

Maybe they can be used in project options.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: MISV on June 21, 2017, 01:23:48 pm
1)
When trying to install package that uses bgratext.pas I get error

Quote
bgratext.pas(361,30) Error: Identifier not found "lpNoGUI"
bgratext.pas(405,64) Error: Identifier not found "lpNoGUI"


2)
when trying to install BGRABitmapPacl 9.2.2 it seems LCLWin32 is not defined... causing
error in OpenGLContext.pas

Quote
openglcontext.pas(71,4) Error: User defined: this LCL widgetset/OS is not yet supported

Not sure if this is a Lazarus 1.8 error but in Configure "Build Lazarus" i have LCL widget type set to win32/win64
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 21, 2017, 06:37:23 pm
I just tested the issue again. In my point of view it is working correct:

If you make changes in a undocked (default) IDE in the settings, these settings are taken to a initially docked desktop after installing package AnchorDockedDsgn. You can now make changes in this new created (default docked) desktop. The last unused (default) desktop isn't deleted and not changed (see Mainmenu -> Tools -> Desktops ...).

If you now uninstall package AnchorDockedDsgn, the previous default desktop is loaded again. The docked desktops are deleted and this is correct, as they come with the package AnchorDockedDsgn (all things that a package installs have to be removed, if the package is uninstalled).

If you later want to reuse docked settings, you have do export and import these docked desktops. Of course this is not working now (https://bugs.freepascal.org/view.php?id=29200 (https://bugs.freepascal.org/view.php?id=29200)). So the current workaround is to make a copy of your environmentoptions.xml and use it after reinstalling AnchorDockedDsgn, don't uninstall that package or adapt your divergent settings from your default desktop after package reinstalling.
I didn't deinstall AD i just switch from Lazarus with AD to Orginal released Lazarus to test if an error is there too, and You mean i have to reinstall all my carefully layouted desktops again ?
Which - If you really had tested it - isn't working correctly too (Windows don't appear, or appear on another place and hiding other windows), but that would be another issue.
XML(rared) attached
How about: "If a desktop-setting isn't meant for you, don't touch it, yust deactivate it, or activate only the parts you understand but NEVER delete it (at least not without questioning the User) !!!
BTW: when working with Sparta (at the moment) you have to switch often, when you work with incompatible (Delphi) Form-Files.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Michl on June 21, 2017, 09:30:12 pm
I didn't deinstall AD i just switch from Lazarus with AD to Orginal released Lazarus to test if an error is there too
How do you test it? If AnchorDockingDsgn is installed, you can't switch to default destop. Please explain, what steps you made.

and You mean i have to reinstall all my carefully layouted desktops again ?
Which - If you really had tested it - isn't working correctly too (Windows don't appear, or appear on another place and hiding other windows), but that would be another issue.
Yes, that is a known problem. Currently don't use more then one desktop with installed AnchorDocking. See linked bugreport above.

How about: "If a desktop-setting isn't meant for you, don't touch it, yust deactivate it, or activate only the parts you understand but NEVER delete it (at least not without questioning the User) !!!
I don't understand what you mean with that.

BTW: when working with Sparta (at the moment) you have to switch often, when you work with incompatible (Delphi) Form-Files.
In the last time, I always work with installed AnchorDockingDsgn and Sparta_DockedFormEditor. But I don't work with Delphi form files. I don't have any problems here, how I use the IDE. Please create for any unknown issue, you found in your daily work, a bug report. Only if the bug is known and repeatable, there is a chance that someone can fix it.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 21, 2017, 09:57:24 pm
How about: "If a desktop-setting isn't meant for you, don't touch it, yust deactivate it, or activate only the parts you understand but NEVER delete it (at least not without questioning the User) !!!

As I wrote in the bug tracker:

Unfortunately, currently there is no chance to preserve the docked desktops when AnchorDocking is not installed. It's because AnchorDocking directly saves the desktops. If it is not installed, Lazarus has no idea how to save them.

AnchorDocking takes care of its desktops. If it's not there, AnchorDocking desktops cannot be resaved. (The whole environment settings are loaded at start and saved on demand -> the whole XML file is rewritten.) The AnchorDocking-only parts can be loaded/rewritten only if AnchorDocking is installed. No chance to change this unless you have an idea and a patch.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 21, 2017, 10:18:23 pm
That's normaly the point when using XML-Files, things you don't understand, you just store as they are, (or leave it alone), and when saving something, the parts are saved as read, that's the way it (should) work in Opendocument, and other XML-related Programs.
The best thing as always is to ask the User. Somthing like:
3 Desktop-Layout have been found that cannot be used now shall they be deleted or preserved ? Please select the layouts to be deleted then a listbox where you could check the layouts to be deleted.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 21, 2017, 10:38:07 pm
That's normaly the point when using XML-Files, things you don't understand, you just store as they are, (or leave it alone)

How it works now: the options XML file is parsed into pascal structures and the content is trashed/forgotten. What cannot be read is lost.

As I stated before: feel free to improve it.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 21, 2017, 10:47:38 pm
How do you test it? If AnchorDockingDsgn is installed, you can't switch to default destop. Please explain, what steps you made.
Since I Use win10 the release executable is preserve in the folder (as a nomal User I don't have write-rights in that directory)
So i close the Lazarus-win-AD, go to the Lazarus directory (in this case it's \Lazarus_rc\ (secondary Instalation) )
and start Lazarus.exe there
Switch back: Close Lazarus(release) and Start Lazarus with Startlazarus.exe (I've got a link vor that on the desktop)
Do I really have to explain how to Stop and Start Lazarus ?

[..] use only one Docked-Desktop
normaly I do. But somtimes you want to store a specific layout for a Project with two or more Editor-Windows ... Debug-Desktop, or just for other reasons I want to preserve the actual layout.

I don't understand what you mean with that.
The Desktop-Layout are stored in a xml-file. So when you find a Desktop file with A(Or other Unknown )-Layouts you just save the data separatly and restore it as it was when saving the file, or ask the User what to delete,
Or copy/rename the file to a extra place/name so AD( or whatever Component stored its Data there can retreive it from there (maybe also after asking the User). How do others feel about this ?

In the last time, I always work with installed AnchorDockingDsgn and Sparta_DockedFormEditor. But I don't work with Delphi form files. I don't have any problems here, how I use the IDE. Please create for any unknown issue, you found in your daily work, a bug report. Only if the bug is known and repeatable, there is a chance that someone can fix it.

One Example: Make a master-Form (an invisible TForm-descendant with some extra properties) then make a (visible) Child-Form descended from the Master-form. Close the Project
Open the Project again and see the result when looking at the Child-Form. To edit this you need the Standard editor, for this I need the Release-Version, or a Version without SDFE.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 21, 2017, 10:51:00 pm

How it works now: the options XML file is parsed into pascal structures and the content is trashed/forgotten. What cannot be read is lost.

As I stated before: feel free to improve it.
Point me to Where is the Data read (File & place) [edit]( in the trunk of cause)
and also Where is the Data written (File & place) I hope it's Component.
I'll have a look, when I found something I'll send a patch. I'd go for the first option "save unknown data and restore on writing". But first I'll implement the "Save file separately (and a User dialog)-option".
Then when switching back I (and other Users) could restore the file manually or with a batch.
Does this sound reasonable ?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 21, 2017, 10:54:59 pm
Point me to Where is the Data read (File & place) [edit]( in the trunk of cause)
and also Where is the Data written (File & place) I hope it's Component.

ide\environmentopts.pp:

procedure TDesktopOpt.Load(Path: String);
procedure TDesktopOpt.Save(Path: String);

See the "if Assigned(FDockedOpt) then" part.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Ondrej Pokorny on June 21, 2017, 11:00:54 pm
In the last time, I always work with installed AnchorDockingDsgn and Sparta_DockedFormEditor.

Maybe having 2 Lazarus folders/EXEs, one with AnchorDocking installed and one without it would help you as well.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: bastynator on June 23, 2017, 01:12:05 pm
Installed it and works fine. Thanks for all your effort.

I noticed improvements on connect/disconnect second screen.  8)
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 23, 2017, 02:59:25 pm
Maybe having 2 Lazarus folders/EXEs, one with AnchorDocking installed and one without it would help you as well.
Yes, and using separate configurations for them with --pcp=...
Then a docked and non-docked layouts must be configured only once.
That is a workaround however.
Making the IDE aware of AnchorDocking settings also when AnchorDocking is not installed sounds like a right solution.
Maybe there can be default Load and Save functions that only retain the data. Then AnchorDocking can register its own Load and Save functions.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 23, 2017, 04:19:11 pm
Yes, and using separate configurations for them with --pcp=...
Then a docked and non-docked layouts must be configured only once.
That is a workaround however.
You are right it's a reasonable workaround, only when testing something it  at best has to be with the same configuation otherwise you'll never know if its the config or the program.
Making the IDE aware of AnchorDocking settings also when AnchorDocking is not installed sounds like a right solution.
I'd call it make the IDE aware that there may be other components writing configurations (e.G: AnchorDocking)
Maybe there can be default Load and Save functions that only retain the data. Then AnchorDocking can register its own Load and Save functions.
That sounds like a better solution, but a bigger change, because it involves both, the Base-IDE and the component. Maybe in the next step.
... so let me have a look ...
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 23, 2017, 04:44:48 pm
That sounds like a better solution, but a bigger change, because it involves both, the Base-IDE and the component. Maybe in the next step.
Obviously the Base-IDE must be involved when AnchorDocking is not installed. I don't know how you planned to do it.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 27, 2017, 09:35:03 pm
procedure TDesktopOpt.Load(Path: String);
procedure TDesktopOpt.Save(Path: String);

See the "if Assigned(FDockedOpt) then" part.

This is not the solution !
Since DesktopCanBeLoaded [line 652] is a Class-Procedure how about:
line 1062 ff
Code: Pascal  [Select][+][-]
  1.   dskDockMaster := FXMLCfg.GetValue(Path+'DockMaster', '');
  2.  
  3.   if not  TEnvironmentOptions.DesktopCanBeLoaded(dskDockMaster) or (IndexOf(dskName) >= 0) then
  4.     Exit;{^Here Classname instead of variable}
  5.  
  6.   dsk := TDesktopOpt.Create(dskName, dskDockMaster<>'');
  7.  
This makes the class TDesktopOptList less dependend on a specific EnvironmentOptions.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: jc99 on June 28, 2017, 12:24:05 am
Here comes the promised patch:
The idea behind this patch was to keep the Information rather than deleting it. I order to do so I had to return the information, that the desktop was understood (added to the list of desktops) and an index of the desktops had to be created to replace only the actual added desktops on saving.
There are also three minor changes, not related to the task:
DbgIntfDebuggerBase now belongs to DebufferIntf appended a comment about this
two Class-Variables were replaced by their Classname, because the Method called are class-methods.
(  TEnvironmentOptions and TTransferMacroList )

Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: BeniBela on June 28, 2017, 01:21:58 pm
This works as well as usual with fpc 3.1.1:

Code: [Select]
/opt/lazarus/ide/sourcefilemanager.pas(6450,29) Error: (5038) identifier idents no member "DesignPPI"
/opt/lazarus/ide/sourcefilemanager.pas(6452,71) Error: (5038) identifier idents no member "DesignPPI"
/opt/lazarus/ide/sourcefilemanager.pas(6454,88) Error: (5038) identifier idents no member "DesignPPI"
/opt/lazarus/ide/sourcefilemanager.pas(6455,88) Error: (5038) identifier idents no member "DesignPPI"
/opt/lazarus/ide/sourcefilemanager.pas(6457,86) Error: (5038) identifier idents no member "DesignPPI"
/opt/lazarus/ide/sourcefilemanager.pas(6458,86) Error: (5038) identifier idents no member "DesignPPI"
/opt/lazarus/ide/sourcefilemanager.pas(6459,27) Error: (5038) identifier idents no member "DesignPPI"
sourcefilemanager.pas(8456) Fatal: (10026) There were 7 errors compiling module, stopping
Fatal: (1018) Compilation aborted
Makefile:3961: recipe for target 'lazarus' failed


And the different icons are gone. In 1.6. some Lazarus windows had differently colored icons, and now they are all blue. How are you supposed to use Alt+TAB, when all the icons are the same?
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Mando on June 28, 2017, 01:57:26 pm
Hello:
 I detect that TbuffDataSet works worst than in version 1.6.2.
The TbuffDataset control works worse than version 1.6.2.
In my application, I load a file with insert and post.
The file I was uploading in 3s now takes 6s.

regards

Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: JuhaManninen on June 28, 2017, 02:26:43 pm
This works as well as usual with fpc 3.1.1:
Works well here. FPC trunk is a moving target. Please update.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: BeniBela on June 28, 2017, 11:30:37 pm
This works as well as usual with fpc 3.1.1:
Works well here. FPC trunk is a moving target. Please update.

Nice try. I am not updating to trunk. With my luck I get a fpc bug and then cannot compile anything anymore
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Thaddy on June 28, 2017, 11:46:22 pm
Then don't use trunk, simple.Stick to non-moving targets  8-)
Before you can report against trunk you always verify against the latest trunk you can download when you verify and even then  you may be late because it's fixed.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: mercury on June 29, 2017, 04:30:54 am
3. I don’t like the new icons, any way to switch back?

No, Lazarus moves only forward, no step back :)

It looks like 90's style. :(
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: mercury on June 29, 2017, 04:45:14 am
1.I'll commit qt5pas1.dll in binaries/i386-win32/qt next week (mingw build),
2.QWebEngine isn't yet inside bindings because I must create all stuff manually since I don't any scripts for
automatic bindings creation, on the other side QWebKit is deprecated so that's the reason why it's moved away from
bindings.

AFAIK mingw build doesn't support QWebEngine. That's why I ask for a precompiled DLL. Because I don't want install that huge Visual Studio IDE.
May I ask when you or others will finish QWebEngine bindings.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: tattila on June 30, 2017, 10:19:45 am
Hi!

I have two question:

1. This working good on 64bit win, not than previous builds?

2. How can i Activate the single window mode?

Thank you for your help!
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Thaddy on June 30, 2017, 11:22:56 am
Hi!

I have two question:

1. This working good on 64bit win, not than previous builds?

2. How can i Activate the single window mode?

Thank you for your help!

1. It already worked very good in 64 bit mode from 1.6. so that is a bit of nonsense unless you were sleeping for a couple of years.
2. I think you mean anchor docking. Well, install anchor docking. It is available from the package list.
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: ermeneuta on June 30, 2017, 05:21:25 pm
Does it exist a  .deb  package for the ARM processor of the Raspberry, for 1.8.0RC2 ?
If yes, where ?
If not, is it possible to compile 1.8.0RC2 from source on the Raspberry ? Details, anyone ?

TNX
Title: Re: Lazarus Release Candidate 2 of 1.8
Post by: Thaddy on June 30, 2017, 09:11:13 pm
No. But it is rather easy.
Do you have fpc 3.0.2 already installed?
And subversion?
TinyPortal © 2005-2018