Lazarus

Announcements => Lazarus => Topic started by: Martin_fr on May 17, 2017, 03:43:52 pm

Title: Lazarus Release Candidate 1 of 1.8
Post by: Martin_fr on May 17, 2017, 03:43:52 pm
The Lazarus team is glad to announce the first 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 r36152 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 RC1" directory.

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

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_RC1

For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:
ftp://freepascal.dfmk.hu/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.8RC1 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 RC1.
- 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 RC1. 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 1 of 1.8
Post by: Eugene Loza on May 17, 2017, 03:53:41 pm
COOL!!! THANKS A LOT!!!!! :D :D :D
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: ahiggins on May 17, 2017, 04:05:14 pm
Great work, many thanks
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JZS on May 17, 2017, 04:13:24 pm
Thanks Lazarus Developers...
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: knuckles on May 17, 2017, 05:01:54 pm
Excellent work 8-)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: tr_escape on May 18, 2017, 08:58:37 am
In linux mint fpc_3.0.3-r36152_i386.deb gave a error but I able to installed with by shell.
All packages install with shell command:

sudo apt deb fpc_3.0.3-r36152_i386.deb
sudo apt deb fpc-src_3.0.3-r36152_i386.deb
sudo apt deb lazarus-project_1.8.0RC1-0_i386.deb

I think (maybe) previous version and my some trying to cross compiling can be effect.

After component/package install my project compiled.

Thank a lot to Lazarus & Fpc team.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: PeterX on May 18, 2017, 09:43:40 am
I'm on Windows.
Lazarus 32 Setup wants to write a QT4 dll into windows/system32
So Setup needs admin rights.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: PeterX on May 18, 2017, 10:29:10 am
Whyever, this window was left over after installation of RC1 ..

Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jma_sp on May 18, 2017, 11:21:50 am
Muchas gracias una vez más al equipo de FreePascal sin el cual Lazarus no sería posible y al equipo de Lazarus por hacer posible una nueva versión.

Lo he instalado y me ha dado un error al compilar un programa:

Compilar paquete CodeTools 1.0.1: Código de salida 1, Errores: 1
basiccodetools.pas(42,32) Fatal: no puedo encontrar Laz_AVL_Treeutilizado por BasicCodeTools, ppu incompatible=C:\lazarus18\components\lazutils\lib\i386-win32\laz_avl_tree.ppu, paquete LazUtils
Compilar paquete IDEIntf 1.0: Abortado, Errores: 1
actionseditor.pas(29,3) Fatal: no puedo encontrar LCLIntfutilizado por ActionsEditor, ppu incompatible=C:\lazarus18\lcl\units\i386-win32\lclintf.ppu, paquete LCLBase

Supongo que es mejor que reconstruir o hacer una instalación limpia sin la versión previa pero por el momento no puedo.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: dogriz on May 18, 2017, 12:01:28 pm
Tested crosscompilation (simple form with label, edit, button and checkbox) on Debian 9 (amd64)

Freepascal 3.0.3 + Lazarus 1.8 RC1

linux x86_64 (native)    OK
linux i386      OK
win32         OK
win64         OK
linux arm v7      OK

Looks promising so far. But will be tested more. Thanks for a great work!
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jma_sp on May 18, 2017, 12:48:06 pm
OK, ALL WORKS NOW, NO ERRORS, just CLEAN + REBUILD ALL.

In translation need to translate a button caption from English to  Spanish: Break to Interrumpir

De maravilla :)

Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Martin_fr on May 18, 2017, 01:35:04 pm
I'm on Windows.
Lazarus 32 Setup wants to write a QT4 dll into windows/system32
So Setup needs admin rights.

There is a checkbox allowing you to choose, if you want to install the qt lib.

You only need it, if you want to write qt apps. (which I guess most people do not need)

However, yes, it is checked by default.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: guest58172 on May 19, 2017, 01:49:28 am
Thanks for this version but it is not good at all. On a single application i have 3 breaking changes and (or) regressions. That's way too much.

Already spent 3  hours  trying to find workarounds. Once a thing fixed i discover another new issue. great.

Regressions or breaking changes have that of annoying is that you're asked to spend some time on things you're not responsible for breaking.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: zeljko on May 19, 2017, 09:01:44 am
Thanks for this version but it is not good at all. On a single application i have 3 breaking changes and (or) regressions. That's way too much.

Already spent 3  hours  trying to find workarounds. Once a thing fixed i discover another new issue. great.

Regressions or breaking changes have that of annoying is that you're asked to spend some time on things you're not responsible for breaking.

That's why it's name is RC1. Please open issues about  any regressions.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: guest58172 on May 19, 2017, 10:03:37 am
It's a beta. I think that usually a RC is almost usable so that people can actually use it much and find problems that are not so obvious. Here for me it's very obvious: things are broken and not working. At the beginning it even did not compile.

Maybe it's just bad luck. This happens sometimes, everyone thinks it's okay while a single person have many problems.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: wp on May 19, 2017, 10:08:57 am
Lamenting and complaining about broken things without saying what is broken is not helpful at all. To me, the 1.8RC1 is working perfectly.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Zoran on May 19, 2017, 10:31:33 am
It's a beta. I think that usually a RC is almost usable so that people can actually use it much and find problems that are not so obvious. Here for me it's very obvious: things are broken and not working. At the beginning it even did not compile.

Maybe it's just bad luck. This happens sometimes, everyone thinks it's okay while a single person have many problems.

Okay, we feel sorry for you. And now what? Should we start guessing here what these are?
You just don't tell us what things are broken. What is the point?

Did you report these regressions on bugtracker?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on May 19, 2017, 10:52:45 am
It would be helpful is BBasile simply lists his problems in more detail instead of simply stating "problems".
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: knuckles on May 19, 2017, 01:04:38 pm
I have a suggestion, well actually it was this post http://forum.lazarus.freepascal.org/index.php/topic,35821.msg237572.html#msg237572 (http://forum.lazarus.freepascal.org/index.php/topic,35821.msg237572.html#msg237572) by Akira1364 that gave the idea.

The default margin of 80 in the code editor is too narrow, I actually think something like 110 would be more better. I know this can come down to personal choice and I don't even know if this breaks any coding style guidelines but I think Delphi and Lazarus should rethink the default size of the margins to something more suiting to modern times.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: guest58172 on May 19, 2017, 01:17:55 pm
It would be helpful is BBasile simply lists his problems in more detail instead of simply stating "problems".

Done at the right place.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: guest58172 on May 19, 2017, 01:32:39 pm
Example of something stupid that breaks code is this commit

https://github.com/alrieckert/lazarus/commit/2e1e616eec8f9becc24fe547546cdafaf5f1c7d7

changes the signature of an event. The parameter added is not useful at all, it's just an helper. For things like this the procedure to follow is to deprecate the old event and add another one, not to change it like this, without transition.

This is not the worst. The worst is when a fix is merged to fix an example but breaks a real application.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on May 19, 2017, 01:55:21 pm
It's not the signature. But it is annoying that the default value is somehow lost or forgotten (or the method was not simply overloaded, but that won't work there). I can agree with you: that's a change for the worse in so far as that it needs fixing by inserting a default value. Somebody was not thinking at that moment when he wrote that.

Leaves some more issues plz: 2 to be precise?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 19, 2017, 02:47:27 pm
Example of something stupid that breaks code is this commit

https://github.com/alrieckert/lazarus/commit/2e1e616eec8f9becc24fe547546cdafaf5f1c7d7

changes the signature of an event. The parameter added is not useful at all, it's just an helper. For things like this the procedure to follow is to deprecate the old event and add another one, not to change it like this, without transition.
True, it is a breaking change from me. The change in code is very easy though, just add an empty string as property name. Also the PropName parameter is kind of logical because the event is about properties.
Is another event needed? Nobody complained during over a year, I thought it is not used much outside Lazarus IDE.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on May 19, 2017, 04:39:34 pm
just add an empty string as property name.
Should be done by the maintainer. NOT by users of that particular code.
If that can not be done that code should be reversed, because it handles something in the mind of the programmer, not an issue at hand.

That's bad coding. Because it is bad design. And break things where it should not break things. Fix it or reverse it. <Hmm.. usual, and hey it's Friday... still >:D >:D >:Db mode on>
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 19, 2017, 05:04:40 pm
I will look at the event issue later today and try to make it backwards compatible.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on May 19, 2017, 06:32:44 pm
Juha, it is a hell of a good release candidate. It will be a good release... ;)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 19, 2017, 08:14:30 pm
Juha, it is a hell of a good release candidate. It will be a good release... ;)
Wow, thanks! :)

I fixed the event issue in r55015. Now the signature of event TPropHookModified is restored. A new event TPropHookModifiedWithName is added.
It will be backported to 1.8 soon.

There are some nasty regressions, like this one:
  https://bugs.freepascal.org/view.php?id=31547
"You can't paste text copied from other Lazarus instance"
It was caused by removing an extra null from GTK2 clipboard buffer. Apparently it is not the right place to do it but I don't know how to fix it properly.

There is also a GTK2 related freezing but it is now solved using a workaround.
  https://bugs.freepascal.org/view.php?id=31138

What other regressions are there?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: guest58172 on May 19, 2017, 08:33:50 pm
The revision that "fixed" reloading of layouts in AnchorDocking miniIDE example is a huge PITA for Coedit, this is my biggest concern actually. You should see the issue in the recently modified.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: guest58172 on May 19, 2017, 08:36:38 pm
https://bugs.freepascal.org/view.php?id=31834
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 20, 2017, 01:52:02 pm
Hi, i don't know it this is a new one, I just tested 1.8rc1 on a bunch of my projects and i stumbled across:
Code: Text  [Select][+][-]
  1. Projekt kompilieren, Modus: Debug, Ziel: C:\projekte\Delphi\bin\x86_64-win64\prj_CompileErr.exe: Exit code 1, Fehler: 2
  2. unt_childclass.pas(23,28) Error: function header doesn't match any method of this class "class Something:{Dynamic} Array Of AnsiString;"
  3. unt_childclass.pas(15,20) Error: Found declaration: class Something:{Dynamic} Array Of AnsiString;
  4.  

BTW it compiles in Delphi (i just tested)

Compiler stops at:
Code: Pascal  [Select][+][-]
  1. class function TChildClass.Something: TStringArray; //<--- Here
  2. begin
  3.   setlength(Result, 2);
  4.   Result[0] := 'Hello';
  5.   Result[1] := Format('%s%s',['Wor','ld']);
  6. end;        
  7.  

Declaration of TChildClass:
Code: Pascal  [Select][+][-]
  1. { TChildClass }
  2.    // see §1
  3.   TChildClass = class(TBaseClass)
  4.     class function Something: TStringArray; override;
  5.   end;  
  6.  

Declaration of TBaseClass:
Code: Pascal  [Select][+][-]
  1. type
  2.   {$ifndef SUPPORTS_GENERICS}
  3.   TStringArray = array of string;
  4.   {$endif}
  5.   // see §1
  6.  
  7.   TBaseClass = class
  8.     class function Something:{$ifdef SUPPORTS_GENERICS}Tarray<String>{$else}TStringArray{$endif}; virtual; abstract;
  9.   end;
  10.  

It used to compile in older versions ...
Hint & spoiler:
See hint.txt
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 20, 2017, 02:10:26 pm
I got it to compile ...
Workaround: actually there is ... (2)
A Hint still would be usefull but this have to come from the compiler.

BTW delphi -> 983.552Bytes !!!
       fpc  -> 440.637Bytes  [edit](after strip)-> 245.760 Bytes
 
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 20, 2017, 02:23:12 pm
 :( OOps, here's another one :
A project using RunTimeTypeInfoControls
Code: [Select]
using config file C:\lazarus_rc\lazarus.cfg
SetPrimaryConfigPath NewValue="C:\ProgramData\laz_conf" -> "C:\ProgramData\laz_conf"
Hint: (lazarus) State file of LCL 1.8.0.1 is newer than state file of Package: RunTimeTypeInfoControls 0.1
Info: (lazarus) Execute Title="Kompiliere Package RunTimeTypeInfoControls 0.1"
Info: (lazarus) Working Directory="C:\lazarus_rc\components\rtticontrols\"
Info: (lazarus) Executable="C:\lazarus_rc\fpc\3.0.2\bin\x86_64-win64\fpc.exe"
Info: (lazarus) Param[0]="-MObjFPC"
Info: (lazarus) Param[1]="-Scgi"
Info: (lazarus) Param[2]="-O1"
Info: (lazarus) Param[3]="-g"
Info: (lazarus) Param[4]="-gl"
Info: (lazarus) Param[5]="-l"
Info: (lazarus) Param[6]="-vewnhibq"
Info: (lazarus) Param[7]="-FuC:\lazarus_rc\packager\units\x86_64-win64"
Info: (lazarus) Param[8]="-FuC:\lazarus_rc\components\lazutils\lib\x86_64-win64"
Info: (lazarus) Param[9]="-FuC:\lazarus_rc\lcl\units\x86_64-win64"
Info: (lazarus) Param[10]="-FuC:\lazarus_rc\lcl\units\x86_64-win64\win32"
Info: (lazarus) Param[11]="-FuC:\lazarus_rc\components\lazcontrols\lib\x86_64-win64\win32"
Info: (lazarus) Param[12]="-FuC:\lazarus_rc\components\ideintf\units\x86_64-win64\win32"
Info: (lazarus) Param[13]="-FuC:\lazarus_rc\components\rtticontrols\"
Info: (lazarus) Param[14]="-FUC:\lazarus_rc\components\rtticontrols\lib\x86_64-win64\win32\"
Info: (lazarus) Param[15]="-dLCL"
Info: (lazarus) Param[16]="-dLCLwin32"
Info: (lazarus) Param[17]="runtimetypeinfocontrols.pas"
Hint: (11030) Start of reading config file C:\lazarus_rc\fpc\3.0.2\bin\x86_64-win64\fpc.cfg
Hint: (11031) End of reading config file C:\lazarus_rc\fpc\3.0.2\bin\x86_64-win64\fpc.cfg
Free Pascal Compiler version 3.0.2 [2017/05/14] for x86_64
Copyright (c) 1993-2017 by Florian Klaempfl and others
(1002) Target OS: Win64 for x64
(3104) Compiling runtimetypeinfocontrols.pas
(3104) Compiling rttictrls.pas
(3104) Compiling rttigrids.pas
(1008) 5439 lines compiled, 1.9 sec
(1022) 2 hint(s) issued
An unhandled exception occurred at $00000001000B6EB3:
EAccessViolation: Access violation
  $00000001000B6EB3
  $00000001000D9C6D
  $000000010001E981
  $00007FF9EF4FAC1D
  $00007FF9EF49A2AA
  $000000010001E28A
  $00000001000D9CC8
  $00000001000DD857
  $00000001000DE721
  $0000000100015A20
  $0000000100029960
  $000000010000A066
  $000000010001A667
  $00007FF9ED478364
  $00007FF9EF4B70D1
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 20, 2017, 02:43:10 pm
Jc99, the problems do not look like related to 1.8. They may be related to switching from FPC 2.6.x to 3.0.x.
In the first case you maybe should define SUPPORTS_GENERICS.
StringArray is probably defined elsewhere.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Martin_fr on May 20, 2017, 02:57:47 pm
The "TStringArray" issue, is as old as time (nearly).
The problem has been seen countless times, whenever a type is re-declared in a unit used in implementation section.

Yes a hint would be nice. Not sure where best to generate this. In FPC which is where the error is detected, or later in codetools when the error is displayed.

Maybe create one (or two) feature requests on mantis.

------------------------
Quote
(1022) 2 hint(s) issued
An unhandled exception occurred at $00000001000B6EB3:
EAccessViolation: Access violation

This looks like a bug in fpc 3.0.2 (and maybe earlier). Please report in mantis.

To work around, try different compiler settings, and disabling inlining.
Also try to clean *All* ppu files (in this package and packages used by it  / but not in fpc itself), so they will be rebuild

If you can see what flag exactly causes the crash, then it can be checked that it is not set by default in the release
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 20, 2017, 03:59:19 pm
I'd like to, but I get
Code: Text  [Select][+][-]
  1. APPLICATION WARNING #2702: Your session has become invalidated.
even after several relogins...
Is there a bugtracker for the bugtracker or a Wiki ?
So maybe someone else could report it for me. (BTW: the project which cause the FPC-Err was nothing fancy just the plain $(Lazarusdir (1.8rc1))\examples\autosize\childsizinglayout
Second time it went through (no err, prog run (still 2 issues))
[edit]
Looking at the report, an due to the fact that the files in Question were actually compiled, i think it's somewhere near the routine, that checks if a package has to be compiled or not. 
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Martin_fr on May 20, 2017, 04:03:51 pm
I'd like to, but I get
Code: Text  [Select][+][-]
  1. APPLICATION WARNING #2702: Your session has become invalidated.
  2.  
even after several relogins...
Try removing all cookies for mantis.freepascal / bugs.freepascal....
https://www.mantisbt.org/bugs/view.php?id=15502
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 20, 2017, 09:07:16 pm
Now I got another one:
It started after closing all editor-windows, when reopening a sourcefile the first stays empty and a second source-editor is opened (Ok, I know this is an old one) but then the cursor is not updated or disappears fully what is really annoying.
I try to make a screenshot ...

BTW mantis on this computer still not working (it works on another .. but not this one. Got the message even when not logged in)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Martin_fr on May 21, 2017, 12:31:23 am
It started after closing all editor-windows, when reopening a sourcefile the first stays empty and a second source-editor is opened (Ok, I know this is an old one) but then the cursor is not updated or disappears fully what is really annoying.
I try to make a screenshot ...

First of all, can you make a backup of the project / including the lps session file, which may be in (below) the primary conf folder (where environment_option.xml is / in your user folder AppData/lazaru ... see also menu: view ide-internals)

There are 2 or 3 errors in this post.

But first of all:
* anchor docking ?
* OS / widgetset ?

1) the empty source-editor. This may be do to with the anchor docking (presumingly you use anchor docking, or is it another docking solution?)
- Without ADocking each SourceEditor stores its position on the screen. (I do not know A.D., nor how it changes those things.)
- If at any time you had 2 SourceEditor open, and then closed SourceEditor-1, then in future all files should always be in SourceEditor-2 (because that is the one you last used, and this way it will be on the correct position on the screen).
Without AnchorDocking only SourceEditor-2 will open.
If A.D. opens an empty SourceEditor-1 in that case, then that is a problem.

Well I am only guessing...
But in order for a bug report, that has any chance of being solved, it needs either steps to reproduce, or an attached project (incl lps) that causes the issue.
----

2) There is some empty space between the editors, and the tabs above them. That looks wrong to me?
Maybe report that to.
----

3) the caret.
Do you have steps to reproduce? Or a project that causes it when opened?
It may be something that is OS dependent, which would make it harder to track (cause someone with the same OS must look at it)
Do you know / Can you test, if it happens without AnchorDocking?

Actually I just compiled with AD, and I get immediate crashes (in SynEdit caret related code), so maybe there is a lead.

---
I dont know much about AnchorDocking, but if I can reproduce the caret, then I might be able to look at this.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Martin_fr on May 21, 2017, 12:38:00 am
About 1: empty source editor.

That means:
- empty - no tabs, on editors ? (I assumed that one)
- emyty - tabs, but the textarea is just blank

----------------------
Also:

- What settings is your IDE build with? eg what optimization level, what other fpc flags

- Does the error happen, if the two source editors are:
floating
docked to different positions (no tabs name sourceeditor)
docked to same positions (has tabs name sourceeditor)

For each test restart the IDE, so the 2 sourceedits are from the beginning in the described dock pos.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 21, 2017, 04:52:44 am
OK, first :
Win10, x64_86-Win64, Docked (anchordocking), Normal-IDE, (German), 1.8rc1 (of cause)

And, the first-editor-Area is empty, like when you close all files, except the docking bar on the side, or top, depends and seems functional.
restart of IDE, cursor works again, but to get rid of the second editor i have to kill the configfiles and then configure all windows back to where I'd like to have them.
in 1.6.X same behavior hoped it'd be fixed in this version. For 1.6.4 I've a backup config at hand, and also disabled autosave of layout.

Quote
... and then closed SourceEditor-1, then in future all files should always be in SourceEditor-2 ...
Haha, very funny  >:( they cant be closed, if it were that easy I would'nt even think of complaining about it. Only by closeing all files, when the last file closes, both editors disappear at the same time, when opening a file both editors appear again !!! (small correction) you can close the windows, but you can not close the editors,they are still in the windows-menu 
And no, i did not use any old config, I made a secondary installation with separate configuration.

Quote
- Does the error happen, if the two source editors are:
floating
docked to different positions (no tabs name sourceeditor)
docked to same positions (has tabs name sourceeditor)
when docked to same positions (has tabs name sourceeditor)
Second editor is floating somewhere mostly behind the (fullscreen-) main-window ...   

in the environment.xml are lines:
Code: XML  [Select][+][-]
  1.  <Desktop2 Name="default docked" DockMaster="TIDEAnchorDockMaster">
  2. ...
  3.    <Desktop Version="2" FormIdCount="49">
  4.  ...
  5.     </Desktop>
  6.       <MainIDE>
  7. ...
  8.       </MainIDE>
  9.       <SourceNotebook>
  10. ...
  11.       </SourceNotebook>
  12.      <SourceNotebook2>
  13.         <Caption Value="SourceNotebook2"/>
  14.         <CustomPosition Left="344" Top="291" Width="677" Height="440"/>
  15.       </SourceNotebook2>
  16.  
When I delete the "<SourceNotebook2>"-Tag, next restart 2.Editor is gone. But that doesn't explains why it got there in the first place.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JD on May 21, 2017, 08:21:33 am
Kudos to the Lazarus team for their hard work. I really appreciate you guys.

By the way, I just saw the new TTaskDialog  :D

http://wiki.lazarus.freepascal.org/TTaskDialog

Very good! I had relied on the mORMot SynTaskDialog in the past. It is nice to know that we now have a native component.

JD
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 21, 2017, 11:44:46 am
When I delete the "<SourceNotebook2>"-Tag, next restart 2.Editor is gone. But that doesn't explains why it got there in the first place.
Can you reproduce the problem when starting with empty default configuration?
If you can, please report with clear steps to reproduce.
If not, then just clean the configuration and be happy.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 21, 2017, 01:01:42 pm
Now I was after the second error, I recompiled Lazarus without AD then the following happend, on some (a few) source-files the caption of the Sourceeditor is "Quelltextedit (2)" in that moment you can see two Sourceeditors in the Windows-menu, but you actually see only one working editor. When closing the file and opening it again everthing is back to normal. So I think there are two problems, one, that somtimes the/a second editor is used, the other that AD can't cope with a second editor when the first is actually hidden.

I open files by double clicking on the file in the project-explorer or in the project-group-window (I know it's alpha).

The problem with the invisible cursor did not happen again.
The other problem seems not to be 1.8rc1 related, i used to have that in 1.6.X with AD too.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 21, 2017, 02:42:08 pm
I traced the Double-Editor problem a litte further:
The problem comes from the .lrs .lps(session-file) [edit]
in the unit-section there are two entrys (maybe from older versions)
Code: XML  [Select][+][-]
  1.      <Unit1>
  2.         <Filename Value="foo.pas"/>
  3. ...
  4.         <EditorIndex Value="1"/> <!-- these -->
  5.         <WindowIndex Value="-1"/> <!-- these -->
  6. ...
  7.      </Unit1>
  8.  
If those are present, the second editor is opened. Normally that goes undetected because everything seems to work normal except for an aditional (2) in the title of the editor-window. But when you use AD it starts to get ugly.
[edit]
BTW, just reinstalled Laz 1.8rc1, (and deleted all files remaining in the folder (~1.200 ?!) and the config-dir) same behavior.
See:
https://github.com/joecare99/Public/tree/master/Examples/FPC (https://github.com/joecare99/Public/tree/master/Examples/FPC)
--> Prj_DblEditTest1.* and Prj_DblEditTest2.*
you may also need ../Source/DblEditTest/*
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 21, 2017, 03:19:59 pm
BTW, just reinstalled Laz 1.8rc1, (and deleted all files remaining in the folder (~1.200 ?!) and the config-dir) same behavior.
Reinstalling Lazarus makes no difference if the problem is your project session file.
Can you reproduce after deleting the session file?
If you find a way to reproduce with default configuration and with a new project, please report.
Otherwise please forget the whole issue.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 21, 2017, 03:32:44 pm
So you ask people to delete all their session-files in all of their projects when going to a new version, because problems by a lack of backward compatibility is not an issue ?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Martin_fr on May 21, 2017, 03:45:18 pm
Session files should always keep working. At least upwards. Not downwards.

However. IIRC there have been session files that got broken for unknown reasons. Maybe there is an undiscovered bug, that sometimes writes a broken session, I do not know. If a broken session files gets loaded by one version, there is no guarantee that it will be by the next version.

As for your particular session files, regarding Anchordocking, I dont know if they are ok or broken. I don't use anchordocking, and I don't maintain it either.

---------------

I havent looked at the code, but
"windowindex" of -1
might be a bug.
(EditorIndex -1 seems to exist though)

At least none of my sessions has it (and I use 2 source editors all the time).


-------
As I said, not sure if this is a bug, If windowindex -1 is a bug, then fixing it should include to read the broken session...


 
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 21, 2017, 04:21:59 pm
I think the (let's call it) hazy behavior lies between Laz and AD, only in AD you actually see the consequences.
How to reproduce: Compile Laz with AD and then move the Window to another editor. The now empty window stays empty because the editor is closed, but not the container.
Now you can go even further, move the editor from Window 2 to a new window, now you have two empty window and a third window. I think that can be played along ... 
The closing-routine of the editor-window when the last window is moved might look different to the standard closing routines.

@Juha: So yes, i can reproduce (with plain Laz & AD) and new, clean project.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on May 21, 2017, 04:26:30 pm
Session files should always keep working. At least upwards. Not downwards.
I would very much appreciate that ..

And thanks, you pointed me (and hopefully a laz-coder) in the right direction.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Martin_fr on May 21, 2017, 07:41:07 pm
Session files should always keep working. At least upwards. Not downwards.
Infact like config files, they have a version
Code: Text  [Select][+][-]
  1. <Version Value="10"/>

So that for example changes to default can be limited to new versions.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: cpicanco on May 22, 2017, 03:15:13 am
Laaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaazarus 1.8.0 RC1 is out !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 22, 2017, 07:33:37 am
@Juha: So yes, i can reproduce (with plain Laz & AD) and new, clean project.
Should be reported in bug tracker.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: BSaidus on May 22, 2017, 12:02:03 pm
Nothing to Say !! JUST THANK YOU VERY MUCH !! it is wonderfull !! :)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: cpicanco on May 22, 2017, 02:38:03 pm
For me 1.8.0 RC1 is working great after recompiling the native compiler:

https://bugs.freepascal.org/view.php?id=31490
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: dstritt on May 23, 2017, 06:05:32 am
Sorry for reporting here, but the bug tracker isn't letting me create an account. Every time it gives me a url to click in my email it says it's already used or invalid and to try again. When I try to sign up again it says that user name is already in use. Tried with 2 user names and no luck.

Anyway, trying 1.8 RC1 Windows 64bit on Windows 10 is acting up. If you open any project, even a new one, then open the Todo list, then close Lazarus when you repopen it you get an error that says:

TLazSourceFileManager.FindUnitsOfOwner: invalid owner nil.

If you press OK Lazarus loads just fine. If you open the Todo list then close it, then restart Lazarus everything is ok.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: BobS on May 23, 2017, 06:47:25 am
Sorry for reporting here, but the bug tracker isn't letting me create an account.
Same for me you're not alone.  Glad to know it's not just me :).
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: m.abudrais on May 23, 2017, 08:42:32 am
I like the new menu editor :D, thank you Lazarus team.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 23, 2017, 09:54:48 am
Sorry for reporting here, but the bug tracker isn't letting me create an account. Every time it gives me a url to click in my email it says it's already used or invalid and to try again. When I try to sign up again it says that user name is already in use. Tried with 2 user names and no luck.
Could Martin help with that? It seems many people have similar problems.

Quote
Anyway, trying 1.8 RC1 Windows 64bit on Windows 10 is acting up. If you open any project, even a new one, then open the Todo list, then close Lazarus when you repopen it you get an error that says:
TLazSourceFileManager.FindUnitsOfOwner: invalid owner nil.
I was a regression from last Noverber.
 https://bugs.freepascal.org/view.php?id=31006
I fixed it in trunk r55059. Please test.
This proves the release candidates are usefull. This could have gone to the release. :)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: dstritt on May 23, 2017, 11:17:35 pm
I fixed it in trunk r55059. Please test.

How can I go about doing that? I am kinda new to this.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on May 24, 2017, 12:03:41 am
How can I go about doing that? I am kinda new to this.
Easy when you already have FPC installed.
 http://wiki.freepascal.org/Getting_Lazarus#Getting_Lazarus_SVN_development_version
You can have many Lazarus versions around. Just start from cmd line or from desktop link.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: dstritt on May 24, 2017, 02:00:23 am
Ok, I tried trunk 55069 and the problem I was having seems to be resolved. Thanks.
Title: Lazarus Release Canditate 1 of 1.8
Post by: PeterX on May 26, 2017, 02:50:19 pm
I started working on one of my projects this week,
until now everything works fine with Lazarus 1.8 RC1 !

 :D
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Handoko on May 28, 2017, 05:30:13 pm
Hello all.

I found some minor issues and 1 critical issue in Lazarus 1.8.0 RC1:

- Installation - FPC Conflict
- First Time Starting IDE - Wrong Version
- First Time Starting IDE - Package Registration Error
- IDE Keyboard Typing !!! Critical !!!

I posted those problem on different thread, if you're interested you can visit here:
http://forum.lazarus.freepascal.org/index.php/topic,37022.msg247603.html#msg247603

Note:
The tests were performed on Ubuntu Mate 16.10 64-bit and the installation was using 3 deb files (2017-05-15) downloaded from here:
https://sourceforge.net/projects/lazarus/files/Lazarus%20Linux%20amd64%20DEB/Lazarus%201.8.0RC1/
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: chentung on May 28, 2017, 05:34:17 pm
report :
win10 , 64bit, Chinese

C:\lazarus18rc1\components\printers\win32\winutilprn.pas
line 251 is commented out :
-->//function OpenPrinter(_para1:LPSTR; _para2:PHANDLE; _para3:LPPRINTER_DEFAULTSA):BOOL;stdcall; external LibWinSpool name 'OpenPrinterA';

but package fortesreport-3.24-LCL-R2 \ rlprinterd.pas
line 127 need the function OpenPrinter() :
-->if not OpenPrinter(PChar(PrinterDevice.Name),@hPrinter,@foodefs) then ...

I  changed that to
-->  if not OpenPrinterW(PWideChar(PrinterDevice.Name),@hPrinter,@foodefs) then ...

then it can be compiled and installed.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: cpicanco on May 30, 2017, 06:33:42 pm
http://forum.lazarus.freepascal.org/index.php/topic,36093.msg247835/topicseen.html#new

I am guessing this issue (see link above) will be properly resolved when unstable debian becomes stable. It seems that official (from Lazarus) FPC 3.0.2 (also FPC 3.0.3) was compiled using unstable debian source. If you are someone from the official release team, please, could you confirm if this is the case? Also, can you imagine some alternative solution in order to avoid such problems for future releases? Newbies like me will appreciate. Thanks.

PS.: The fix is just a workaround. As noted by Marco van de Voort, there is no official release of FPC *.deb files. In other words, the Lazarus Team (not FPC Team) is redistributing a buggy .deb FPC file. 
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Handoko on May 30, 2017, 06:48:24 pm
I ever got "Error while linking" issue. But it fixed after I properly compile/cross-compile the FPC.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: cpicanco on May 30, 2017, 06:58:27 pm
Quote
I ever got "Error while linking" issue. But it fixed after I properly compile/cross-compile the FPC.

What is your OS Handoko?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on May 30, 2017, 07:05:50 pm
Quote
I ever got "Error while linking" issue. But it fixed after I properly compile/cross-compile the FPC.

What is your OS Handoko?
Multiple ;) I know that. But anyway a linker problem like yours is fixed by updating your toolchain properly.
The only OS for which that is unlikely is Windows 32/64 because those have an internal linker.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Handoko on May 30, 2017, 07:08:58 pm
Main OS: Ubuntu Mate 16.10 64-bit.

I remember I ever got that error several times, because
- I tried to cross-compile but I did it wrong
- I tried to combine Lazarus/FPC with different version of FPC-source

I sometimes naughty, I do thing not following the correct way. I learned the lesson. That "error while linking" just gone if I do it correctly.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Deepaak on May 31, 2017, 04:44:11 pm
 ;D ;D Amazing! million thanks to team Lazarus.  ;D ;D

Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: amarryat on May 31, 2017, 10:30:46 pm
Not knowing what's the best way to report an issue, I'll describe it here.  This was not an issue in 1.6.4, but is a bug in 1.8.0RC1.  I'm using the win32 version.

StringGrid.CellRect returns the improper coordinates when the form isn't visible yet, but works correctly once the form is visible.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: cpicanco on June 01, 2017, 10:20:07 pm
Handoko, as noted by Marco van de Voort, there is no official release of FPC *.deb files. In other words, the Lazarus Team (not FPC Team) is redistributing a .deb FPC file that will cause the linker error for machines with Debian 8 Stable.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: zeljko on June 01, 2017, 10:26:09 pm
Not knowing what's the best way to report an issue, I'll describe it here.  This was not an issue in 1.6.4, but is a bug in 1.8.0RC1.  I'm using the win32 version.

StringGrid.CellRect returns the improper coordinates when the form isn't visible yet, but works correctly once the form is visible.

Best was is to report issue here: https://bugs.freepascal.org , choose lazarus project and fill bug report + example project.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on June 01, 2017, 11:45:37 pm
Best was is to report issue here: https://bugs.freepascal.org , choose lazarus project and fill bug report + example project.
Unless the login problem still prevents him doing so.
Anyway it will be fixed in near future, I understood somebody is working on it.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Ondrej Pokorny on June 02, 2017, 09:54:51 am
Anyway it will be fixed in near future, I understood somebody is working on it.

Who?

Btw. I cannot reproduce it. This code works just fine in trunk and 1.8 RC1:

Code: [Select]
procedure TForm1.FormCreate(Sender: TObject);
var
  R: TRect;
begin
  WriteLn('Creating grid');

  FGrid := TDrawGrid.Create(Self);
  with FGrid do
  begin
    Parent := Self;
    Width := 0;
    Flat := True;

    FixedRows := 1;
    FixedCols := 0;

    // At least 2 columns.
    while Columns.Count < 2 do
      Columns.Add;

    // First column wider than grid width.
    ColWidths[0] := 250;
    ColWidths[1] := 50;

    R := CellRect(0, 0);
    Writeln(Format('%d %d %d %d', [R.Top, R.Left, R.Bottom, R.Right]));

    Row := 4;
  end;
  WriteLn('Done');
end;

end.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on June 02, 2017, 11:00:44 am
Who?
Last I saw mails in fpc-pascal list titled "Mantis/Bugtracker registrations fixed" by Karoly Balogh (Charlie/SGR) and Martin. Michael van Canneyt tried to fix it. Martin still got problems, maybe it is not fixed yet.

Mantis should be updated to latest version which is already 2.4.1. Unfortunately it is a lot of work as was discussed earlier.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Ondrej Pokorny on June 02, 2017, 11:50:31 am
Who?
Last I saw mails in fpc-pascal list titled "Mantis/Bugtracker registrations fixed" by Karoly Balogh (Charlie/SGR) and Martin. Michael van Canneyt tried to fix it.

Ahh OK, you were talking about the mantis problem and not the LCL grid problem  :)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: amarryat on June 02, 2017, 04:26:37 pm

Btw. I cannot reproduce it. This code works just fine in trunk and 1.8 RC1:



I'm using a StringGrid, and it was created in the designer. In my case, CellRect(0, 0) returns something like 80,27 when it should return 0,0.  Once the form is visible, a call to CellRect(0,0) again returns 0,0
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on June 02, 2017, 04:41:08 pm
I'm using a StringGrid, and it was created in the designer. In my case, CellRect(0, 0) returns something like 80,27 when it should return 0,0.  Once the form is visible, a call to CellRect(0,0) again returns 0,0
As always, attach an example project to compile and test.
The explanation you gave is not very useful.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: wp on June 02, 2017, 04:42:28 pm
Still not clear how to reproduce. The attached demo has a design-time created stringgrid, and in the FormCreate event (i.e. before the grid is shown) the coordinates of Grid.CellRect(0,0) are written to a Label. Later, when then form has been shown, you can click on the button to measure CellRect(0, 0) again, and the label does not change.

Code: Pascal  [Select][+][-]
  1. // Use a form with a TStringGrid, a Button and a Label.
  2.  
  3. procedure TForm1.Button1Click(Sender: TObject);
  4. var
  5.   R: TRect;
  6. begin
  7.   R := StringGrid1.CellRect(0, 0);
  8.   Label1.Caption := Format('CellRect = %d, %d, %d, %d', [R.Left, R.Top, R.Right, R.Bottom]);
  9. end;
  10.  
  11. procedure TForm1.FormCreate(Sender: TObject);
  12. begin
  13.   Button1Click(nil);
  14. end;
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: amarryat on June 02, 2017, 07:23:06 pm
I'm using a StringGrid, and it was created in the designer. In my case, CellRect(0, 0) returns something like 80,27 when it should return 0,0.  Once the form is visible, a call to CellRect(0,0) again returns 0,0
As always, attach an example project to compile and test.
The explanation you gave is not very useful.

Thanks - I've attached a zip file containing a simple project that illustrates this.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Ondrej Pokorny on June 02, 2017, 08:35:49 pm
Thanks - I've attached a zip file containing a simple project that illustrates this.

I fixed it in r55163. Please report to mantis the next time so that we have track of the bugs.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: amarryat on June 02, 2017, 10:33:33 pm
Thanks - I've attached a zip file containing a simple project that illustrates this.

I fixed it in r55163. Please report to mantis the next time so that we have track of the bugs.

Thanks - looking forward to the update.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: ermeneuta on June 03, 2017, 12:52:22 am
Tried today to install fpc + lazarus on Linux Mint 18.1
fpc_3.0.3-r36152_i386.deb  installed without problems.
fpc-src_3.0.3-r36152_i386.deb also installed without problems.
lazarus-project_1.8.0RC1-0_i386.deb gave this error message :

Error: Dependency is not satisfiable: fpc(=3.0.3) | fp-compiler (=3.0.3)

What can I do ?  Thanks

Al
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: mattias on June 03, 2017, 11:44:48 am
Tried today to install fpc + lazarus on Linux Mint 18.1
fpc_3.0.3-r36152_i386.deb  installed without problems.
fpc-src_3.0.3-r36152_i386.deb also installed without problems.
lazarus-project_1.8.0RC1-0_i386.deb gave this error message :

Error: Dependency is not satisfiable: fpc(=3.0.3) | fp-compiler (=3.0.3)

What can I do ?  Thanks

Please create a bug report.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on June 03, 2017, 12:02:44 pm
Error: Dependency is not satisfiable: fpc(=3.0.3) | fp-compiler (=3.0.3)
Just to be sure: you haven't installed any FPC version from Mint's repository, right?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: otoien on June 03, 2017, 12:52:44 pm
Great work with a new release! A minor anomaly: After recompiling for the Anchordocking the IDE Coolbar no longer showed (as it did before compile and on the last release) and I had to fiddle quite a bit to get it back - it is a little while ago so I do not remember exactly what worked - there were a couple of re-compiles involved but I am not sure that was what made it.

Also I now notice that the new shaded area does not align with the coolbar - may be this is by design to create a shading effect? System is Win7 professional and with size is > 125%.  should add that I cleared the folders of all files before reinstall, but allowed conversions of the settings.


Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: ermeneuta on June 03, 2017, 11:33:47 pm
Error: Dependency is not satisfiable: fpc(=3.0.3) | fp-compiler (=3.0.3)
Just to be sure: you haven't installed any FPC version from Mint's repository, right?
No, I downloaded both fpc and lazarus  .deb packages from the SourceForge repository, from this URL :
https://sourceforge.net/projects/lazarus/files/Lazarus%20Linux%20amd64%20DEB/Lazarus%201.8.0RC1/ (https://sourceforge.net/projects/lazarus/files/Lazarus%20Linux%20amd64%20DEB/Lazarus%201.8.0RC1/)

Al
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Tommi on June 04, 2017, 05:00:49 pm
This bug is still alive : http://forum.lazarus.freepascal.org/index.php/topic,32863.msg212126.html#msg212126

When you resize the window you obtain ugly artifacts. You can see them in attached image.

It would be great if you could solve it.

(Lazarus 1.8rc1 64bit on Windows 7 64bit)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: wp on June 04, 2017, 05:32:55 pm
I can confirm, even with Laz trunk (win 10/64 bit, Laz-trunk/fpc3.02/32 bit). Is there a valid bug report for it?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: zeljko on June 04, 2017, 08:14:27 pm
I can confirm, even with Laz trunk (win 10/64 bit, Laz-trunk/fpc3.02/32 bit). Is there a valid bug report for it?

Maybe, but such example is needed to fix it...or open new one and attach example from above screenshoot.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: ermeneuta on June 05, 2017, 12:17:18 am
Tried today to install fpc + lazarus on Linux Mint 18.1
fpc_3.0.3-r36152_i386.deb  installed without problems.
fpc-src_3.0.3-r36152_i386.deb also installed without problems.
lazarus-project_1.8.0RC1-0_i386.deb gave this error message :

Error: Dependency is not satisfiable: fpc(=3.0.3) | fp-compiler (=3.0.3)

What can I do ?  Thanks

Al
Problem solved, though I don't know how and why....
I simply reformatted the partition, reinstalled Mint 18.1 from scratch, then, before trying to install fpc and lazarus, did an apt update and an apt dist-upgrade...  this time both fpc and lazarus installed without fusses, and my program did compile and run correctly.

Still have to understand why some lcl components do show differently when the program is executed under a different distribution of Linux, but this a topic for another forum...

Al
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on June 05, 2017, 09:22:34 am
Still have to understand why some lcl components do show differently when the program is executed under a different distribution of Linux, but this a topic for another forum..
Because themes for GTK2 are different in those distributions. LCL uses native controls instead of custom drawing them.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: ermeneuta on June 05, 2017, 04:52:22 pm
Still have to understand why some lcl components do show differently when the program is executed under a different distribution of Linux, but this a topic for another forum..
Because themes for GTK2 are different in those distributions. LCL uses native controls instead of custom drawing them.
Thanks for the explanation. At this point, is there anything I can do to be reasonably sure that my program behaves exactly, or almost exactly, on the users' machines as it does on mine ? Are those GTK2 themes changeable programmatically ?

TNX

Al
 
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Bart on June 05, 2017, 05:29:59 pm
Use fpGUI?

Bart
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on June 05, 2017, 05:35:37 pm
Or ownerdrawn
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: zeljko on June 05, 2017, 05:42:44 pm

Thanks for the explanation. At this point, is there anything I can do to be reasonably sure that my program behaves exactly, or almost exactly, on the users' machines as it does on mine ? Are those GTK2 themes changeable programmatically ?

TNX

Al

Maybe yes, google for $HOME/.gtkrc or similar names...maybe $HOME/.gtk2rc ...
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: JuhaManninen on June 05, 2017, 06:43:47 pm
Are those GTK2 themes changeable programmatically ?
No. They idea is that a user can customise his environment as he pleases.
All applications should follow the customised theme and thus look consistent.
A themable desktop system is a good thing, I don't know why anybody would want to make an alien looking app which does not respect the user settings.

Linux distributions by definition are diverse because of competing desktop and widget systems.
Even so there is effort to get consistent look between applications. For example my KDE has specific settings for GTK+ applications, and they look more or less like KDE apps do. Their level of desktop integration obviously does not match with the real KDE apps.
Other desktop environments have similar efforts.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: ermeneuta on June 05, 2017, 06:53:16 pm
A themable desktop system is a good thing, I don't know why anybody would want to make an alien looking app which does not respect the user settings.
The problem is that, using Linux Mint 18.1 and Lazarus 1.8 RC1, I wrote a program with a couple of sliders, which I set of color Silver.
When run on different distribution, the sliders were of color black, thus not visible on the form background, also black....

Al
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on June 05, 2017, 09:11:09 pm
A themable desktop system is a good thing, I don't know why anybody would want to make an alien looking app which does not respect the user settings.
The problem is that, using Linux Mint 18.1 and Lazarus 1.8 RC1, I wrote a program with a couple of sliders, which I set of color Silver.
When run on different distribution, the sliders were of color black, thus not visible on the form background, also black....

Al
Then install the proper dependencies, silly < not only grumpy but really angry >:D >:D>  Oh, well, it's not like the olden days for grumpy old man that happen to know about , well,nix (which means "nothing" in Dutch)  O:-) 8-) :-* :-X
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: mogenslarsen on June 06, 2017, 07:36:22 am
Hello! I have a computer with 32-bit Windows. I wanted to compile for Win64.

I have installed the compiler:
lazarus-1.8RC1-fpc-3.0.2-win32.exe
Then I installed the cross-compiler:
lazarus-1.8RC1-fpc-3.0.2-cross-x86_64-win64-win32.exe

I lauched Lazarus and pressed F9. The default Project1 compiled and run successively.
Then I choose Project -> Project Options -> Compiler Options -> Config and Target -> Target OS (-T) -> Win64 -> OK.

The following warning appeared:
[Warning]
The current FPC has no config file. It will probably miss some units. Check your installation of fpc.
[OK] [Ignore]

And when I attempted to compile, the following errormessage appeared:
Compile package FCL 1.0.1: Exit code 1, Errors: 1
Error: Illegal parameter: -Twin64
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: Thaddy on June 06, 2017, 08:35:26 am
Did you also compile everything for win64? rtl, fcl, packages?
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on June 06, 2017, 08:40:13 am
@Thaddy: that's normally part of the lazarus-1.8RC1-fpc-3.0.2-cross-x86_64-win64-win32.exe package
but
@mogenslarsen: You only mentioned the win64 did you also set the the TargetCPU to x86_64 ?
 [edit] Because i386_win64 is an illegal combination (Maybe a better Message : Illegal parameter -Twin64 in combination with -Pi386 would help)
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: mogenslarsen on June 06, 2017, 07:04:46 pm
Thank you. After I changed "Target CPU family (-P)" from default to x86_64 the problem was solved.
By the way, I need not to change "Target processor (-Cp)" from default. It seems to be inconsistent and confusing for me as a novice.
Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: ermeneuta on June 07, 2017, 01:07:55 am
Use fpGUI?

Bart
Sorry for being so dumb, but I tried without much success...
I followed the instructions in the  http://wiki.lazarus.freepascal.org/fpGUI_Interface (http://wiki.lazarus.freepascal.org/fpGUI_Interface) page,
my project compiled up to a given point, then an error message appeared, saying :

fpguiwscalendar.pp(38,28) Error: Identifier not found "TWSCalendar"

Maybe I missed some important steps ?

TNX

Al


Title: Re: Lazarus Release Canditate 1 of 1.8
Post by: jc99 on June 07, 2017, 08:36:04 pm
Thank you. After I changed "Target CPU family (-P)" from default to x86_64 the problem was solved.
By the way, I need not to change "Target processor (-Cp)" from default. It seems to be inconsistent and confusing for me as a novice.
Yes a plausibility-check would be nice, ...
But that's why there is the Wiki, and it's written nearly everywhere: "Read the Wiki!" ...
TinyPortal © 2005-2018