Hi Thierry,

I think the code in the click() of a pageframe is not interpreted

No message, just ignored

Hi Vincent,

You're the first in 10 years who ever noticed that!
Good catch!

To see how VFP behaves, DO Home(1) + "tools\ab\aw\samples\fic\fictuto\tutolan.prg" with 'event.scx' (time line is bottom-up):

&& click on page, outside tab:
Page          pgf.pag1.Click
Page          pgf.pag1.MouseUp(1,0,30,99)
Page          pgf.pag1.MouseDown(1,0,30,99)


&& click on page tab:
Pageframe     pgf.MouseUp(1,0,88,24)

Page          pgf.pag1.Click

Pageframe     pgf.Click
Pageframe     pgf.MouseUp(1,0,88,24)

Page          pgf.pag1.Activate
Page          pgf.pag1.Deactivate

Pageframe     pgf.MouseDown(1,0,88,24)

Conclusion:

1. pgf.Click() fires only when clicking a page tab (not sure if it ever fires when pgf.Tabs = .F.
2. pgf.Click() fires before pgf.pag1.Click
3. pgf.MouseUp() fires twice

Does it match your experience?

Would it help if we implement something exactly the same? Or would this code be enough?

procedure awPag.ClickInet
…
this.Parent.Click && regardless where user has clicked, in or outside tab.
this.Click

Thank you Thierry for this complete answer.

The click in the page works, it is simply to avoid repetition in each tab. Not sure that this justifies a development.

To your good heart ...

I answered you too quickly, sorry.

In fact, the click() in the tab is not interpreted either.

Only Activate() is

We will make this event model more similar to what happens in VFP.

Thanks in advance

The FoxInCloud Live Tutorial Event Sample now implements this:

&& click on page tab:
Page          pgf.pag1.Click
Pageframe     pgf.Click

Not sure why .mouse*() don't fire -- will investigate

Will update V 3.0.0-beta.7 installation on our site with this new feature.

Will update V 3.0.0-beta.7 installation on our site with this new feature.

done!

Great, thanks !

Not sure why .mouse*() don't fire

Fixed and new V 3.0.0-beta.7 uploaded