Recent

Author Topic: Lazarus 1.6 - 2nd Release Candidate  (Read 86225 times)

Ondrej Pokorny

  • Full Member
  • ***
  • Posts: 220
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #15 on: January 15, 2016, 07:15:55 pm »
Why did I not notice it earlier? ...

AFAIR, it has been already discussed somewhere (forum or mailing list [?]), but it looks like we all have forgotten about it - probably because nobody reported it in mantis.

(If I am not wrong - I don't remember exactly.)

Josh

  • Hero Member
  • *****
  • Posts: 1270
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #16 on: January 15, 2016, 10:30:33 pm »
Hi
Just done a fresh install of 1.6rc2 on osx 10.6.8.
At first it seems ok, so I tried to just rebuild lazarus
and get the following error.
LAZUTILs error code 256
and cant rebuild lazarus.
Obviously I have not tried to install any packages as they will fail..

Any Ideas

Josh
The best way to get accurate information on the forum is to post something wrong and wait for corrections.

eny

  • Hero Member
  • *****
  • Posts: 1634
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #17 on: January 16, 2016, 12:21:17 am »
"Object Inspector:  The Boolean property editor now uses a CheckBox by default. A ComboBox with "False", "True" can still be selected in options. The control is now a custom drawn TCheckBoxThemed which is used for both selected and non-selected properties, thus making them visually identical. "

It is much better to leave these kind of overengineered features off by default.
No need to shove them down our throats.
All posts based on: Win10 (Win64); Lazarus 2.0.10 'stable' (x64) unless specified otherwise...

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #18 on: January 16, 2016, 01:23:34 am »
"Object Inspector:  The Boolean property editor now uses a CheckBox by default. A ComboBox with "False", "True" can still be selected in options. The control is now a custom drawn TCheckBoxThemed which is used for both selected and non-selected properties, thus making them visually identical. "

It is much better to leave these kind of overengineered features off by default.
No need to shove them down our throats.

Why do you feel that a CheckBox for a boolean value is overengineering?
CheckBox is the most natural control for booleans. That is what CheckBox was created for in the first place.
In my opinion a ComboBox with 2 values ("False" and "True") to change a simple boolean is overengineering. That's why I changed it to a more natural and logical control.

Delphi has a hybrid control with both CheckBox and ComboBox. That can be called overengineering, yes.
Anyway, I did not quite understand your reasoning but fortunately you can configure the boolean property editor to your liking.
« Last Edit: January 16, 2016, 01:31:23 am by JuhaManninen »
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

fic

  • New Member
  • *
  • Posts: 14
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #19 on: January 16, 2016, 08:32:36 am »
Just wondering... Why did all my previous installed component-palletes dissapeare?

Josh

  • Hero Member
  • *****
  • Posts: 1270
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #20 on: January 16, 2016, 10:03:36 am »
Going on from previous post
Quote
Hi
Just done a fresh install of 1.6rc2 on osx 10.6.8.
At first it seems ok, so I tried to just rebuild lazarus
and get the following error.
LAZUTILs error code 256
and cant rebuild lazarus.
Obviously I have not tried to install any packages as they will fail..

Any Ideas

Josh

I removed lazarus and went back to 1.4.4, and all ok. removed 1.4.4 re-installed 1.6rc2 and same problem. So now am back on 1.4.4.

Can anyone verify this?
The best way to get accurate information on the forum is to post something wrong and wait for corrections.

Bart

  • Hero Member
  • *****
  • Posts: 5265
    • Bart en Mariska's Webstek
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #21 on: January 16, 2016, 10:34:38 am »
Blaazen, are you reading this? Any idea why TCheckBoxThemed affects the key presses?
Anyway I will look at this during the weekend.

I attached a patch to the issue.
It resolves the behaviour in OI, but I am not sure if it will lead to other problems.

The original line in the constructor looked odd to me.
I think, form the comments in that line, the purpose was to have csNoStdEvents, not to remove it.

Mind you, there is another issue with the ThemedCheckBox, which was hidden by a wrong compiler directive.
See http://bugs.freepascal.org/view.php?id=29412

I took the liberty of assigning both issues to you.

Bart

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #22 on: January 16, 2016, 01:29:35 pm »
About the TCheckBoxThemed Boolean editor in Object Inspector:
I solved it by removing define UseOINormalCheckBox and added UseOICheckBoxThemed, inverting the logic, in r51304.
Now the normal CheckBox is used by default. I marked it for merging to 1.6.
The issue with TCheckBoxThemed is still valid but there is no urgent hurry to fix it.

Please test now with trunk, or use define UseOINormalCheckBox when building 1.6RC2. Does the normal CheckBox Boolean editor work OK for everybody?
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #23 on: January 16, 2016, 01:33:17 pm »
Just wondering... Why did all my previous installed component-palletes dissapeare?

You must rebuild Lazarus, just like when installing new component packages.
Tools -> Configure "Build Lazarus" ...
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #24 on: January 16, 2016, 01:35:42 pm »
Just done a fresh install of 1.6rc2 on osx 10.6.8.
At first it seems ok, so I tried to just rebuild lazarus
and get the following error.
LAZUTILs error code 256
and cant rebuild lazarus.

Does the compiler work? Try with a simple cmd line prog.
Lazarus 1.6 includes the new FPC 3.0.
I don't have OSX to test here.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

Josh

  • Hero Member
  • *****
  • Posts: 1270
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #25 on: January 16, 2016, 02:26:45 pm »
Hi JuhaManninen,

I could create a simple GUI app with a tbutton, and this would compile and run, but I cannot re-build lazarus, or add any components that require a rebuild of lazarus to function.
I have tried re-freshing lazarus files from menu, and removing all pp files as a last ditch attempt, but this did not help.
It maybe something in my config, but odd as to 1.4.4 running.
the main difference is fpc 3.0.0 over 2.6.4..

Any steps/tests you want me to do let me know

Josh
The best way to get accurate information on the forum is to post something wrong and wait for corrections.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #26 on: January 16, 2016, 02:42:17 pm »
Any steps/tests you want me to do let me know

Sorry, I cannot help with OSX. I understood some people are running the latest Lazarus there. I hope they can help.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9754
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #27 on: January 16, 2016, 02:55:29 pm »
I am not using Mac either.

But in any case, you need to provide more output.

If the error is in the "message window", then right click it, and find "Copy all and hidden ...." and paste this.

Also run lazarus from console (inside the bundle, or it will not work), and see if there is any output on stdout/stderr. Or redirect this to a file (maybe use --debug-log= )

eny

  • Hero Member
  • *****
  • Posts: 1634
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #28 on: January 16, 2016, 03:19:45 pm »
Why do you feel that a CheckBox for a boolean value is overengineering?
I don't feel that way.

CheckBox is the most natural control for booleans. That is what CheckBox was created for in the first place.
I agree to some extent.
But not within the context of the Object Inspector!

The OI is now broken with an inconsistent look and feel:
  • the checkboxes create a very 'busy', irregular OI window; that by itself is enough reason to not activate such a feature by default;
  • the checkboxes are no longer consistent with the way the other options work (black text, white background and blue highlight color when selected/clicked); also the color to indicate a non-default value is inconsistent;
  • when going through the options with the cursor keys the checkboxes are skipped; in case of 2 adjacent true/false options the cursor stops at the 2nd one  :(
  • and the piece de resistance: for people that do not know the meaning of a v-shaped symbol in a small white box, the text '(true)' is placed to the right of it %) (if a text would have been required for whatever reason it should have been yes/no or on/off and no parentheses).
Quote
That's why I changed it to a more natural and logical control.
No problem with the change by itself, as long as the options to fall back to the original, more efficient behavior, are enabled by default (indeed a checkbox in the right location).
'more natural and logical control' does not apply to his particular situation.

Quote
Anyway, I did not quite understand your reasoning but fortunately you can configure the boolean property editor to your liking.
See above and yes, that is fortunate indeed.
« Last Edit: January 16, 2016, 03:21:49 pm by eny »
All posts based on: Win10 (Win64); Lazarus 2.0.10 'stable' (x64) unless specified otherwise...

balazsszekely

  • Guest
Re: Lazarus 1.6 - 2nd Release Candidate
« Reply #29 on: January 16, 2016, 03:46:23 pm »
Quote
@josh
I could create a simple GUI app with a tbutton, and this would compile and run, but I cannot re-build lazarus, or add any components that require a rebuild of lazarus to function.
I have tried re-freshing lazarus files from menu, and removing all pp files as a last ditch attempt, but this did not help.
It maybe something in my config, but odd as to 1.4.4 running.
the main difference is fpc 3.0.0 over 2.6.4..
Probably the symlink inside the bin folder points to the wrong version of fpc. You should remove fpc2.6.4/Lazarus 1.4.4 completely:
1. Download the script(attachment)
2. Change to the directory where the script is located
3. Execute the script:
    chmod +x uninstall.sh
    sudo ./uninstall.sh
4. Remove config dir
    cd ~/
    rm -rv .lazarus
5. Install 1.6 RC2

 

TinyPortal © 2005-2018