OnEnter Event ???

[J-G]

I'm fairly familiar with 'Events' and can usually understand what is expected (logically) for many but have not had a need to use the [OnEnter] event until today.

It seems to me that an [OnEnter] event ought to fire as soon as the focus is taken by the component (in this case a TEdit). What I want to do is decide whether to allow an edit if a certain flag has been set after an edit in a different TEdit.  To this end I created an [OnEnter] event which just puts a message up asking if the user really does want to 'edit' the value which is dependent upon the previous entry.

When this message didn't appear as expected, I set a break-point at the start of the event but that never 'fired'  - and I can't understand why!

[Zvoni]

Some code, please?

[dseligo]

It fires in Lazarus 2.0.10 and 2.2.0 on Windows 11, I just tried it.

[J-G]

It fires in Lazarus 2.0.10 and 2.2.0 on Windows 11, I just tried it.

Are you suggesting that my logic is not flawed?  -  just that [OnEnter] is not implemented for a TEdit in Laz 1.6 ?

That would make sense - though somewhat disappointing since the event is listed in the Object Inspector  - and creates a procedure as expected.

[J-G]

Some code, please?

I doubt that any code would help Zvoni

[Zvoni]

OnEnter is one of the most basic events, and without knowing i would bet, that it was part of Lazarus in the 0.X-versions, and that it worked there already.

I'm rather guessing there is something else going on

[J-G]

OnEnter is one of the most basic events, and without knowing i would bet, that it was part of Lazarus in the 0.X-versions, and that it worked there already.

I'm rather guessing there is something else going on

This was my thought.

Am I wrong in assuming that using the mouse to 'enter' a TEdit should be thought of as [OnEnter]?

This is the procedure created :

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

1. procedure TForm1.TPI_ParamEnter(Sender: TObject);
2. begin
3.   If UNS then
4.       ShowMessage('Really?');
5. end;
6.  

UNS (Unified Number Series) is a boolean which is set to true in the other TEdit (on condition) but I can't check the status because the break-point (set at 'If UNS then') doesn't get called.

[Zvoni]

Just moving the mouse or clicking into that TEdit?

[J-G]

Just moving the mouse or clicking into that TEdit?

Clicking into the TEdit in preparation to make an edit.

[dseligo]

Create new project.
Put TEdit on a form.
Click on it, go to events on Object inspector, double click OnEnter event (on the right side).
It should create new method (Edit1Enter).
Type this in the body:
ShowMessage('x');

Method should look like this:

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

1. procedure TForm1.Edit1Enter(Sender: TObject);
2. begin
3.   ShowMessage('x');
4. end;

Run the project.
If the message doesn't show, compress files from project (not exe) and upload it here.

[dbannon]

Clicking into the TEdit in preparation to make an edit.

Clicking into the TEdit from outside the TEdit. If you are already in there, clicking in there again will not fire the event....

Davo

[Josh]

hi

earliest i have is 1.9 from 2017, and the event is firing fine.

attached simple project with 3 tedits and 3 tlabels that count every time the event is fired when you either click in and tab into the tedits,

[wp]

I still have a Laz 1.6.4 on my disk, and josh's demo project runs correctly with it. I don't know what's wrong in your setup.

But maybe you should take this as a hint to upgrade to a recent version. You can keep your old version and install the new version as a "secondary" installation - check the corresponding box in the installer; this leaves your old installation untouched. But note that loading a project created for Laz 1.6 into Laz 2.x will add new properties so that you cannot load the project by Laz 1.6 again... - always use backup copies for such experiements unless you are sufficiently experienced and can undo the changes.

[J-G]

Apologies for the tardy response - been busy with other parts of the program 

As you will all appreciate, creating a new project (as suggested by dseligo) with just a TEdit and a TLabel shows that the [OnEnter] event does fire as it should - but of course with only one TEdit it fired immediately so wasn't a proper test.

Adding a second TEdit and making that Tab Order 0 forced the original TEdit to correctly test 'On Enter'  - - -  and of course it does.

I now need to look at that part of my program again to see if I can see something I've obviously missed.

@wp I'm aware that it is posible to have multiple versions of FP/Laz installed and yes I have considered it but I've been away from programming for some while so haven't needed any new 'bells and whistles' as yet

[dseligo]

As you will all appreciate, creating a new project (as suggested by dseligo) with just a TEdit and a TLabel shows that the [OnEnter] event does fire as it should - but of course with only one TEdit it fired immediately so wasn't a proper test.

Adding a second TEdit and making that Tab Order 0 forced the original TEdit to correctly test 'On Enter'  - - -  and of course it does.

Check two things first:
1. Be absolute sure that TEdit's OnEnter event is assigned to method you want to
2. Put some memo on your form (just for testing) and put this in the very beginning of your OnEnter method:

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

1. Memo1.Append('OnEnter fired');