Recent

Author Topic: Lazarus Release Candidate 2 of 1.8  (Read 74820 times)

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4459
  • I like bugs.
Re: Lazarus Release Candidate 2 of 1.8
« Reply #45 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.
« Last Edit: June 09, 2017, 03:34:25 pm by JuhaManninen »
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

Handoko

  • Hero Member
  • *****
  • Posts: 5130
  • My goal: build my own game engine using Lazarus
Re: Lazarus Release Candidate 2 of 1.8
« Reply #46 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>
« Last Edit: June 09, 2017, 04:22:17 pm by Handoko »

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4459
  • I like bugs.
Re: Lazarus Release Candidate 2 of 1.8
« Reply #47 on: June 09, 2017, 04:21:19 pm »
@Handoko, that is weird. Can anybody else reproduce?
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

mattias

  • Administrator
  • Full Member
  • *
  • Posts: 184
    • http://www.lazarus.freepascal.org
Re: Lazarus Release Candidate 2 of 1.8
« Reply #48 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.

Handoko

  • Hero Member
  • *****
  • Posts: 5130
  • My goal: build my own game engine using Lazarus
Re: Lazarus Release Candidate 2 of 1.8
« Reply #49 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.
« Last Edit: June 09, 2017, 08:05:38 pm by Handoko »

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4459
  • I like bugs.
Re: Lazarus Release Candidate 2 of 1.8
« Reply #50 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.
« Last Edit: June 10, 2017, 06:58:00 am by JuhaManninen »
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

otoien

  • Jr. Member
  • **
  • Posts: 89
Re: Lazarus Release Candidate 2 of 1.8
« Reply #51 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.
Unless otherwise noted I always use the latest stable version of Lasarus/FPC x86_64-win64-win32/win64

chayimamaral

  • Newbie
  • Posts: 3
Lazarus Release Candidate 2 of 1.8
« Reply #52 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.

Phil

  • Hero Member
  • *****
  • Posts: 2737
Re: Lazarus Release Candidate 2 of 1.8
« Reply #53 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

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9791
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 2 of 1.8
« Reply #54 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"

matthius

  • Full Member
  • ***
  • Posts: 155
  • Creating VRAD...
    • LIBERLOG - Développement rapide
Re: Lazarus Release Candidate 2 of 1.8
« Reply #55 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
M. GIROUX
13 rue Tanguy PRIGENT
35000 RENNES - France
(33)(0)2 23 46 06 54
http://liberlog.fr

amarryat

  • New Member
  • *
  • Posts: 12
Re: Lazarus Release Candidate 2 of 1.8
« Reply #56 on: June 12, 2017, 11:17:27 pm »
Drag a TAChart onto a form.

A range check error popup occurs.

Windows 7.

wp

  • Hero Member
  • *****
  • Posts: 11854
Re: Lazarus Release Candidate 2 of 1.8
« Reply #57 on: June 12, 2017, 11:46:43 pm »

Ondrej Pokorny

  • Full Member
  • ***
  • Posts: 220
Re: Lazarus Release Candidate 2 of 1.8
« Reply #58 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 :/

michaelthuma

  • New Member
  • *
  • Posts: 49
Re: Lazarus Release Candidate 2 of 1.8
« Reply #59 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://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.


 

TinyPortal © 2005-2018