How can I stop autogenerating code blocks?

[dpap]

When I add a control's event the IDE auto-duplicates some other event blocks (empty of code).
How can I prevent this?

[LV]

If you do not require Lazarus' assistance, you can manually write the code, including the event handlers. Good luck and have patience on this journey.   
Simple example: dynamically generated button. https://wiki.freepascal.org/TButton.

[MarkMLl]

I see what you're getting at, and agree that it could be an irritant. /However/ the action of "adding a control's event" is fundamentally that of assigning a named handler, which is what the IDE is doing on your behalf.

Try selecting "none" in the dropdown, or selecting an existing name.

Apart from that the obvious questions: what version of Lazarus etc.?

MarkMLl

[Martin_fr]

When I add a control's event the IDE auto-duplicates some other event blocks (empty of code).
How can I prevent this?

You mean, if you e.g., add on "OnClick" for "Button1", then it will also add maybe "FormOnPaint" => even thought that already exists. So you then have twice "TForm1.OnPaint", one with your code, and one empty?

That would be a bug. I have heard of it before, never had it myself. Not sure what causes it.

If I would guess, I would say, it may happen if
- your code has errors, and the IDE does not find the already existing code (because the IDE stops reading at the error)
- If the IDE for other reasons cannot read your code. (E.g. there are some issues with generic functions).
- maybe other reasons....

But unfortunately I don't know the real answer.

[LV]

It would be helpful if the OP provided a simple, reproducible example; otherwise, we're just guessing while solving a puzzle.

[dpap]

To be more clear, I want to autogenerate the event's implementation block ONLY when I double click at the event's row at object inspector. Now, when I'm doing this, the IDE generates the block (as expected) but duplicates other event's block that already exist! This behavior makes me crazy because every time I must delete them. It seems that the IDE checks the existents of all the events implementation and some of them could not find, although they exist, and recreates them.
The program compiles and runs ok, so the code hasn't problems. Anyway, I want to prevent this auto generation except the one witch I really needed

[cdbc]

Hi
That must indeed be annoying, (never experienced it my self) does it happen in other apps / projects too, if so, are there any common traits between them, that peeks the eye?!?
Just curious - Benny

[dpap]

Yes! it is VERY ANNOING

[Martin_fr]

To be more clear, I want to autogenerate the event's implementation block ONLY when I double click at the event's row at object inspector. Now, when I'm doing this, the IDE generates the block (as expected) but duplicates other event's block that already exist! This behavior makes me crazy because every time I must delete them. It seems that the IDE checks the existents of all the events implementation and some of them could not find, although they exist, and recreates them.

Yes, the 2nd part of this is a bug. See my previous post. But I don't know more about it.

Also yes, the first part: If the IDE completes a method then it completes all of them. Of course it should only update the ones that are really missing.
There is a setting "Update all method signatures" in Tools > Options > Codetools >Class completion.
I don't know, if it will work. It is meant for when you complete a class in the editor using shift ctrl C. So I don't know if it affects completion via OI.
Also, by the name, it is meant about updates, which is, if a method exist, but a parameter was changed/renamed. Though I believe it includes creation too.

Even if that "solves" the issue, it may leave you with other misbehaviour. Because it would not fix the underlying problem, and that is likely to cause issues in other situations too.

Check if there is an open issue for it.

And see if you can provide a sample project on which it happens.

Also check, if it is related to any config you have.
Start your ide with a clean config
  lazarus.exe --pcp-c:\new_empty_folder
If that fixes it, then also supply your config if you create an issue. Otherwise no one will be able to ever reproduce it.

[LV]

I attempted to reproduce the problem without knowing the specifics of your project. I started by creating an empty project and adding two buttons. In the Object Inspector, I assigned OnClick events to both buttons.

Next, I decided to delete Button1 both from the form and the source code editor in the implementation section: procedure TForm1.Button1Click(Sender: TObject); (yellow rectangle).

Then in the object inspector, I assign OnEnter events to Button2.

The result is shown in the attached screenshot.

The issue arises because, when Button1 is deleted from the form, the corresponding procedure declaration in the interface section—`procedure Button1Click(Sender: TObject);`—remains in the type description, indicated with a red rectangle. Once I manually deleted this procedure, everything worked fine.

[Martin_fr]

The issue arises because, when Button1 is deleted from the form, the corresponding procedure declaration in the interface section—`procedure Button1Click(Sender: TObject);`—remains in the type description, indicated with a red rectangle. Once I manually deleted this procedure, everything worked fine.

Not sure if that is the same issue.

You only have 1 (ONE) method "Button1Click"
And most important, there is only on >Body< for that method (only one occurrence in the implementation section).

Hovewer, if I understand dpap correct (and the sporadic few other reports of the past), then dpap gets TWO method bodies.

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

1.   TForm1=class
2.      procedure Button1Click(Sender: TObject);
3.    ...
4.    end;
5.  
6. implementation
7.  
8. procedure TForm1.Button1Click(Sender: TObject);
9. begin
10.   // dpap's code
11. end;  
12.  
13. procedure TForm1.Button1Click(Sender: TObject);
14. begin
15.  
16. end;  
17.  

The last block is an empty duplicate. And it breaks the code.


@LV: What you have, that the method is not deleted, when you delete the button => look at "auto remove empty procedures" => that should help.

Obviously if you have actual code inside, you need to clean it up yourself. The IDE shouldn't just delete your code.

[LV]

@Martin_fr. OK, inverse problems often have multiple solutions. It would be interesting to know the reason for this case.

[dpap]

@Martin_fr. Yes this is the case. Where can you find "auto remove empty procedures" option in Laz3.6?

[Martin_fr]

@Martin_fr. Yes this is the case. Where can you find "auto remove empty procedures" option in Laz3.6?

Tools > Options > Editor > Completion and hints

But that is unlikely to do anything. If it can't find them before creating them, it wont find them for removal.

There is the
 "Update all method signatures" in Tools > Options > Codetools >Class completion.
as mentioned before.

But to really get it fixed, there needs to be a bug report, and a way to reproduce it. All else will just replace one problem with another problem.

[Paolo]

Something related to ?

https://forum.lazarus.freepascal.org/index.php/topic,55819.msg415098.html#msg415098