Recent

Author Topic: Lazarus Bugfix Release 4.8  (Read 11221 times)

jplandolt

  • Newbie
  • Posts: 1
Re: Lazarus Bugfix Release 4.8
« Reply #15 on: June 29, 2026, 07:49:32 pm »
Will anyone on the Lazarus Team be updating the Brew Cask file for the MacOS installation? 

It is a great benefit for those who use command-line tools (like brew) to automate provisioning their machines with these great tools.

dsiders

  • Hero Member
  • *****
  • Posts: 1679
Re: Lazarus Bugfix Release 4.8
« Reply #16 on: June 29, 2026, 09:58:47 pm »
Will anyone on the Lazarus Team be updating the Brew Cask file for the MacOS installation? 

It is a great benefit for those who use command-line tools (like brew) to automate provisioning their machines with these great tools.

Are you referring to this? https://github.com/Homebrew/homebrew-cask/blob/main/Casks/l/lazarus.rb

Ask on their issue tracker: https://github.com/Homebrew/homebrew-cask/issues.

Lazarus does not include or maintain this.

geraldholdsworth

  • Sr. Member
  • ****
  • Posts: 295
Re: Lazarus Bugfix Release 4.8
« Reply #17 on: July 12, 2026, 04:35:14 pm »
Quickie question...what's the best procedure to follow to upgrade from an earlier version?
E.g., I have both 4.2 and 4.4 installed on my macOS machine, along with a non-working 4.6. Should I completely uninstall all three then start afresh?

n7800

  • Hero Member
  • *****
  • Posts: 740
  • Lazarus IDE contributor
    • GitLab profile
Re: Lazarus Bugfix Release 4.8
« Reply #18 on: July 13, 2026, 04:56:57 pm »
Quickie answer... you can install as many versions as you want at once, in different folders. You can also use the same configuration for all of them, but it's recommended to create separate ones.

It all depends on the installation method (manually from source or via the installer). The Windows installer even has a checkbox for this, but I have no idea about the MacOS...

papillon33

  • Guest
Re: Lazarus Bugfix Release 4.8
« Reply #19 on: July 14, 2026, 05:11:43 pm »
Bonjour

J'utilise depuis quelques temp Lazarus Mac et Lazarus Windows. Donc je vous fais une petit remarque sur l'IDE
Le texte du panneau d'aide  de l'inspecteur et en Anglais. Pour être sympa, il suffit de rendre le texte du panneau d'aide de l'inspecteur copiable. Après on se débrouille avec un quelconque traducteur.

Merci

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 12641
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Bugfix Release 4.8
« Reply #20 on: July 14, 2026, 05:23:04 pm »
Well, and for this forum we prefer posts written in English, please.

At least on Windows the text can be copied to clipboard. Though, indeed the context menu (right mouse button) does not contain that option.

You should be able to select it, and then press Ctrl-C.

I do agree a menu entry "Copy" to copy the entire text would be nice. You could make a feature request on our bug tracker. Maybe someone will pick it up (I am too busy / not all others read the forum, and if they do, post on the forum often get forgotten)

papillon33

  • Guest
Re: Lazarus Bugfix Release 4.8
« Reply #21 on: July 14, 2026, 10:20:14 pm »
Bonsoir

Merci de votre retour. Désolé, tous le monde entier n’utilise pas la langue de Donald. Google et Mac OS dispose de traducteurs.

Je ne vous demande en aucun cas de tout changer pour que les autres langues soit considérées normalement.
Simplement faire un copier coller du texte en question.

En effet devant la complexité de la gestion de la taille de fenêtres et composants entre Lazarus Mac et Lazarus Windows, j’utilise l’IDE Lazarus Mac et je me contente de compiler mes applications en version Windows en utilisant cet IDE au strict minimum.

Je pensais bien faire en vous proposant cette modification qui doit être minime. Je me fais jeter. Ok

Vous semblez être surtout Windows dans votre réponse. Merci de transmettre SVP ma requête à quelqu’un de plus Lazarus MAC.

Jean HUNTER

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 12641
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Bugfix Release 4.8
« Reply #22 on: July 14, 2026, 10:55:23 pm »
As you say (or I think you say / I couldn't be bothered to open a translator tool):there are such tools => please use them, and translate before you post.

English is a second language to most people here (including myself). But everyone else manages to use it, so there is no reason you couldn't either.

Well, you can chose, there are French forums that are about Lazarus/FPC.



Moderation notice:

If you want to stay here, and use our forum, then respect the rules. One of which is, that posts are made in English.

n7800

  • Hero Member
  • *****
  • Posts: 740
  • Lazarus IDE contributor
    • GitLab profile
Re: Lazarus Bugfix Release 4.8
« Reply #23 on: July 17, 2026, 01:13:52 am »
At least on Windows the text can be copied to clipboard. Though, indeed the context menu (right mouse button) does not contain that option.

You should be able to select it, and then press Ctrl-C.

I do agree a menu entry "Copy" to copy the entire text would be nice. You could make a feature request on our bug tracker. Maybe someone will pick it up (I am too busy / not all others read the forum, and if they do, post on the forum often get forgotten)

I thought this would be an easy task, but it turned out to be more complicated... I'd already added popup items to Object Inspector, and it was complicated by the fact that it uses a common menu and needs to specify the component being clicked.

But the info box text field in this window is created entirely outside of this unit and package, directly in the IDE code. OI itself only provides a panel for placement and logically can't be responsible for this component, since it could be anything, not even text.

If add a context menu for this control from the IDE code, it will override OI's own menu. Even if do this, it seems there are different "providers" for creating this component (for example, the TurboPowerIProDsgn package), and they have different component ancestors...

In short, the change is too complex for such a minor purpose, especially since the standard [Ctrl+C] works. I wash my hands of it ((

papillon33

  • Guest
Re: Lazarus Bugfix Release 4.8
« Reply #24 on: July 17, 2026, 08:15:45 am »
<<<In short, the change is too complex for such a minor purpose, especially since the standard [Ctrl+C] works. I wash my hands of it ((>>>
Ce n'est pas le cas. Vous parlez de [Ctrl+C] , donc vous parlez de l'IDE sous Windows. Sous Mac c'est [Command+C].
Je parle de l'IDE sous Mac.
Je comprends que c'est un détail sous Windows, il y a beaucoup plus important à faire, en particulier avec le comportement baroque de cette IDE en relation avec la complexité de la gestion de la taille de fenêtres et composants entre Lazarus Mac et Lazarus Windows.

Je complete mon explication. Je crée mes applications avec Lazarus Mac et j'utilise Lazarus Windows juste pour compiler sous Windows. Si j'ai le malheur de toucher et même d'ouvrir pour voir une fenêtre, Lazarus Windows me pourrit le fichier .ifm

Google translate
That’s not the case. You’re referring to [Ctrl+C], so you’re talking about the IDE on Windows. On Mac, it’s [Command+C].
I am talking about the IDE on Mac.
I realize this is a minor detail on Windows—there are far more important things to address, especially given the IDE's quirky behavior regarding the complex handling of window and component sizes between the Mac and Windows versions of Lazarus.

Let me elaborate. I create my applications using Lazarus on Mac and use Lazarus on Windows solely for compiling. If I make the mistake of touching—or even just opening—a window, Lazarus on Windows messes up the .ifm file.

n7800

  • Hero Member
  • *****
  • Posts: 740
  • Lazarus IDE contributor
    • GitLab profile
Re: Lazarus Bugfix Release 4.8
« Reply #25 on: July 19, 2026, 10:59:09 pm »
Let me elaborate. I create my applications using Lazarus on Mac and use Lazarus on Windows solely for compiling. If I make the mistake of touching—or even just opening—a window, Lazarus on Windows messes up the .ifm file.

Disabling the option IDE Options > Environment > Form Editor > Open designer on open unit will make cross-platform use a bit easier (and, by the way, will speed up project opening). The Designer will only open when explicitly requested (by pressing [F12]).

However, I can't be sure how different IDE versions will behave; it seems there have been some behavioral changes.

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 12984
  • FPC developer.
Re: Lazarus Bugfix Release 4.8
« Reply #26 on: July 27, 2026, 03:59:09 pm »
This is already fixed in trunk(since 2024) and fixes, but was not in 3.2.4RC1. But it should be in FPC 3.2.4 when it (finally) lands, as that should be based on fixes.
« Last Edit: July 27, 2026, 04:02:02 pm by marcov »

PascalDragon

  • Hero Member
  • *****
  • Posts: 6421
  • Compiler Developer
Re: Lazarus Bugfix Release 4.8
« Reply #27 on: July 27, 2026, 09:55:39 pm »
# fcl-res: COFF resource writer emits uninitialized NumAuxSymbol, producing a malformed object file

**Component:** Packages / fcl-res
**Version:** 3.2.2 and 3.2.4 (code identical in trunk as of writing)
**Target:** all COFF targets (win32/win64/wince/arm), reproduced on x86_64-win64
**Severity:** minor in normal use, but causes a hard linker crash with `-Xe -XX`
[...]

If you need to copy-paste some AI text then at least take the time to translate it to the formatting used by the forum. Or better yet: don't post such a message at all. 🙄

vlevunliev

  • Newbie
  • Posts: 1
Re: Lazarus Bugfix Release 4.8
« Reply #28 on: July 28, 2026, 10:31:42 am »
:) Ok removed.

Zoran

  • Hero Member
  • *****
  • Posts: 1993
    • http://wiki.lazarus.freepascal.org/User:Zoran
Re: Lazarus Bugfix Release 4.8
« Reply #29 on: July 29, 2026, 09:48:38 am »
The name of the official chm help file is doc-chm-fpc3.2.4-laz4.8-0.zip (see here: https://sourceforge.net/projects/lazarus/files/Lazarus%20Documentation/Lazarus%204.8/).

The name suggests that it contains fpc 3.2.4 help files (not fpc 3.2.2, which is what the official version is compiled with).
Is it a mistake just in naming the file or are fpc help files from release candidate accidentally included, or is it deliberate for some reason?
Swan, ZX Spectrum emulator https://github.com/zoran-vucenovic/swan

 

TinyPortal © 2005-2018