Lazarus 1.6 - 1st Release Candidate

[JuhaManninen]

Neither, It's the third option "Add Files" (files in editor ?)

Ok, "Add Editor Files". Why didn't you say so?
It also works here. You must select all the editor files you want in the final window.

Files are in the same.
If they are invalid for some reason, why are they shown ... ?

There is some inconsistent filtering when adding files in different ways. It must be harmonized later. However it does not cause your issue.

[jc99]

Ok, "Add Editor Files". Why didn't you say so?

Because my popup-menu actually says: "Dateien hinzufügen" (I have to reverse-translate that from german into english)

It also works here. You must select all the editor files you want in the final window.

I also tried with a new project and several files, no problems here, maybe it's related to that specific project file. (or files of that kind)

BTW, see edit and edit2 of my last post.

[jc99]

I think i found the problem:
The "Add editor files"-  function has a problem adding another file when the file first added is already referenced in the .lpr/.dpr- file but not in the .lpi-file.
this also makes funny things in Laz 1.4.4

[Edit]
BTW: "Add files in directory" has the same problem/feature

[arneolav]

My timezone is UTC +1 too
I can confirm this bug.
And also for other timezones, both procedures work in the wrong direction.  (The delta seems ok though)

This is an FPC issue fixed in r31356 (FPC trunk). You can ask the FPC team to merge it into 3.0 branch.

Thanks ondrejpokorny, temporary I did only switch the procedures. Problem solved until new version.

[russdirks]

If I open an existing project with 1.6, and maybe make some changes and try a few things out, can I then go back and open the project in 1.4.4?  Or does the project then become non-backwards compatible?

[balazsszekely]

@russdirks
If I open an existing project with 1.6, and maybe make some changes and try a few things out, can I then go back and open the project in 1.4.4?  Or does the project then become non-backwards compatible?

A backup it's always a good idea and it only takes a few seconds.  Alternatively you can put your project under version control.

[russdirks]

For sure, backups or version control is definitely the way to go.  But I guess I'm still wondering ... does opening my project in 1.6 make some kind of fundamental change to it that then makes it incompatible with 1.4.4?  I guess I'm thinking mostly of configuration settings and various other IDE options.

[arneolav]

I'm installing Lazarus in different directories; Lazarus14, Lazarus16.
And in this early periode, opens my project from the one or other, looking for errors.
No problems observed.
But, of course, as soon as you implement new funcitions from 1.6 in your source, then you will get error by opening from 1.4.
As other has said, allways make a backup.

[guest58172]

Did TSyncompletion change ?

in Lazarus 1.4.4:   fun(ident -> completion -> fun(identifier
in Lazarus 1.6.0:   fun(ident -> completion -> identifier

in Lazarus 1.4.4:   agreggate. -> dot completion -> agreggate.member
in Lazarus 1.6.0:   agreggate. -> dot completion -> member

The previous tokens that are not separated by a blank are completly replaced. I tried to change TSynEdit.WordBreaker but it didn't help.  TSyncompletion.EndOfTokenChar by default already includes the parens...

My usage shouldn't be too exotic I think.
(hint search for fCompletion in the target)

[Martin_fr]

Did TSyncompletion change ?

Not intentionally, unless mentioned on release nodes.

please bug report / ideally with small stand alone example

[JuhaManninen]

... does opening my project in 1.6 make some kind of fundamental change to it that then makes it incompatible with 1.4.4?  I guess I'm thinking mostly of configuration settings and various other IDE options.

You are now confusing 2 different things:

1. A project and its settings is compatible. At least I don't remember any change that would break it. You can work on the same project using both Lazarus 1.4.4 and 1.6.

2. IDE configuration has changed a lot. There is a new desktops feature and a new configurable IDE Coolbar. Many items in configuration XML files were reorganized so they can be part of a saved desktop. Thus it is important to use separate configurations for Lazarus 1.4.4 and 1.6, using --pcp parameter.

[guest58172]

Did TSyncompletion change ?

please bug report / ideally with small stand alone example

Unfortunately on a simple test the completion works fine.
Maybe I have missed something when updgrading my project: I just fixed a few uses then it compiled directly.

Is there anything to do related to the new UTF-8 LCL ?

[JuhaManninen]

Is there anything to do related to the new UTF-8 LCL ?

Only if your code depends on system codepage. See:
  http://wiki.freepascal.org/Lazarus_with_FPC3.0_without_UTF-8_mode

[guest58172]

I've fixed the problem mentioned previously, IMO there's something to change in Synedit:

To test what TSynAutocomplete has to overwrite, it reads the previous word. The charset that defines a word relies on two things (1):

• The function (isIdentifierChar) that tests the basic ASCII chars (A..Z, a..z, _ , 0..9): ok no problem, it excludes the symbols. (2)
• The result of the current highlither function IdentifierChars(): the problem is here, the default implementation of this virtual function returns [#33..#255], which obviously includes all the ASCII symbols. (3)

The basic demo I prepared before was not failing because the editor hadn't an highlighter.
So only the isIdentifierChar() was called.

I suggest to change the implementation of  TSynCustomHighlighter.GetIdentChars to

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

1. function TSynCustomHighlighter.GetIdentChars: TSynIdentChars;
2. begin
3.   Result := ['_', 'A'..'Z', 'a'..'z', '0'..'9'];
4. end;
5.  

(1): https://github.com/alrieckert/lazarus/blob/master/components/synedit/syncompletion.pas#L1756-L1757
(2): https://github.com/alrieckert/lazarus/blob/master/components/synedit/syncompletion.pas#L449
(3): https://github.com/alrieckert/lazarus/blob/master/components/synedit/synedithighlighter.pp#L1483

[Martin_fr]

please bug report...

need to find previous behaviour