Hi,

I report a related issue already in the Bug Tracker back in 2009:

http://bugs.freepascal.org/view.php?id=13994

No solution has been implemented in Lazarus yet. As a work-around, is there any way to tell Code Completion (Ctrl+Shift+C) for event handlers, to only generate the code in the interface of the unit, and not the implementation section?

I like to keep my code implementation in the same order as I have it defined in the Class definition (as defined in Code Tools settings: Method Insert Policy = class order). Currently it place the event handler method always in the undefined published section of my class, and thus the implementation of that method is in the wrong place too. So writing the event handler code, then ask Code Completion to implement the event handler method, I would prefer it (while bug 8135 is not fixed) if Code Tools could only write the method in the interface section only. I can then manually move it to the correct location in my class definition, then do Code Completion again, to implement the interface section in the correct location.

Is this possible in Lazarus IDE 0.9.30.x? I can't see an obvious option in Code Tools to adjust this, so I guess the answer is No. I just thought it worth asking to be sure though.

----8<-------------8<-------------8<-------------8<-------------8<----
  TKeyGenerateForm = class(TfpgForm)
    procedure   meKeyPhraseChanged(Sender: TObject); //<< WRONG LOCATION
  private
     KeyGenerateForm}
    Label1: TfpgLabel;
    cbKeyType: TfpgComboBox;
    btnOK: TfpgButton;
    btnCancel: TfpgButton;
    btnGenerateKey: TfpgButton;
    Label2: TfpgLabel;
    memKeyPhrase: TfpgMemo;
    Label3: TfpgLabel;
    edtBlockKey: TfpgEdit;
    edtByteBlockKey: TfpgEdit;
     KeyGenerateForm}
    FKey: TKey;
    FKeyType: TKeyType;
    procedure   SetKeyType(AValue: TKeyType);
    procedure   FormCreate(Sender: TObject);
    procedure   FormShow(Sender: TObject);
    procedure   cbKeyTypeChanged(Sender: TObject);
  public
    constructor Create(AOwner: TComponent); override;
    procedure   AfterCreate; override;
    procedure   SetKey(AValue: TKey);
    procedure   GetKey(var AValue: TKey);
    property    KeyType: TKeyType read FKeyType write SetKeyType;
  end;

----8<-------------8<-------------8<-------------8<-------------8<----

Regards,
- Graeme -

?
?

Graeme Geldenhuys hat am 13. Mai 2011 um 09:48
geschrieben:

Not yet.
I will add the checkbox for the implementation to my todo list.

?
Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/cd29723f/attachment.html>

That reminds me of an idea, a feature I would like. And that would solve this too.

It would be cool if one could with a single copy (or cut; as in copy/paste) copy a method (or procedure/function) declaration, including the implementation.
Or even several methods, if one selects several lines in the interface.

This would/should allow to:
- copy/cut paste a method from one place in a class to another place in the same class (adjusting order of implementation too)
- copy/cut paste a method from one class to any other class (adjusting the classname in the "procedure FOOCLASS.metho" line) This one would hugely add to the ability of refactoring, moving things up/down in the class hierachy, or even to rlated classes
- copy/cut paste a plain procedure into a class, making it a method
- copy/cut paste a method to become a plain procedure. So this one still requires some clean up, for any reference to self

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/2e221fec/attachment.html>

I'm all for this one. A 'Remove method/procedure' and 'Insert method/procedure'.

As long as it doesn't interfere with regular copy&paste.

Michael.

This is what I was anticipating earlier: items for the Refactoring menu.

Juha

I wish something like this:

//--- into form's private/public/etc
a, b, c: TMyClass;
(some keys are pressed)
...FormCreate...
a := TMyClass.Create;
b := TMyClass.Create;
c := TMyClass.Create;
...FormDestroy
a.Free;
b.Free;
c.Free;

2011/5/13 Mattias Gaertner

?
?

Michael Van Canneyt hat am 13. Mai 2011 um 12:55
geschrieben:

Good idea.
?

As long as it doesn't interfere with regular copy&paste.

I agree, it should not use the Cut/Copy shortcuts. But I see no problem with Paste. Do you see one?

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/9a01420d/attachment.html>

That would be very specific to LCL TForm descendants only. Not a general class definition or even forms from other toolkits like fpGUI. Why? Because only LCL forms have the generic FormCreate() and FormDestry() methods. And those identifier names are not even a must either, I can name my LCL.TForm.OnCreate and .OnDestroy event handlers whatever I want.

Maybe you should play with the Code Templates with macros enabled. They are pretty powerful. I have macros here that create multiple classes and associated list classes from simply copying a single word into the clipboard and triggering the macro.

But who knows, maybe the Lazarus Wizards can conjure up something for you. :)

Regards,
- Graeme -

it should copy (or cut) to clipboard => but as indicated via different shortcut/command.

It does therefore need a different clipboard format (a mixed one plain text / codetool-format). The plain text would allow to paste into other apps (SynEdit does the same for copy with fold info / or copy column-mode selection)

If required, synEdit could get a callbackon paste => so codetool can check for the special format, and intercept it.
At some future point, I can provide insight, how this could even include foldstate info.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/85cc98d5/attachment.html>

I think this is the way to go.

Michael.

?
?

Martin hat am 13. Mai 2011 um 14:44 geschrieben:

[...] IMHO it should copy (or cut) to clipboard => but as indicated via different shortcut/command.

?
Yes. Remove method/procedure. Or maybe better two functions: Copy- and Cut method/procedure.
?

Yes, a special format would be useful.
?
The format must contain ?
- the source of the headers, because they might contain comments and ifdefs
- the implementations
- the source position. This is needed to resolve the identifiers, which could be used in a later extension to automatically extend the uses section of the target unit.

?
Mattias
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/544413e3/attachment.html>

Maybe even synedit could be told to create this format => it has already some nice code to create clipboard stuff.

Or it can be extended in SynSourceEditor

Actually, there should be (at least) 2 paste methods. (But for starters one would do)

1) Paste, without any question.
Necessary/Optional actions such as units-dependencies, or replacing identifiers, can be globally configured
IMHO kept to a minimum by default (insert units into uses, but do not update identifiers

2) Paste via feedback dialog (like "extract procedure " already has. Could offer a growing amount of options. Such as an identifier, to use as prefix for calls to the originating-class. Or creation of missing fields....

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/9fd48374/attachment-0001.html>

?
?

Martin hat am 13. Mai 2011 um 15:36 geschrieben:

[...] Maybe even synedit could be told to create this format => it has already some nice code to create clipboard stuff.

?
Can you explain this??
?

?
This could happen on normal Paste.?
?

2) Paste via feedback dialog (like "extract procedure " already has. Could offer a growing amount of options. Such as an identifier, to use as prefix for calls to the originating-class. Or creation of missing fields....

This can be a menu item under Refactor.

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/926181f6/attachment.html>

for example in line 1509
procedure TCustomSynEdit.DoCopyToClipboard(SText: string; FoldInfo:
String = '');

SynEdit has TSynClipboardStream which accepts various parts of information (e.g the selection mode; and the fold state) It then generates text content, and a custom clipboard format version with the extra info

This class could be extended in TSynSourceEditor (which is a subclass of TSynEdit, but in hte IDE). So odetools would not have to bother to much how to store stuff in the clibpoard or read it. It could use the existing code...
Of course SynSourceEditor would have to expose some methods that can be used, As codetools would decide what text, and what format info need to be copied....

You could also just take a copy of this class and use it directly in codetools.

That's the idea.

+1

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110513/a61e57ca/attachment.html>