Есть такой вопрос - зачем хуки расширяются от Kernel.Hook? Какие от этого профиты?
Gerhard.Marent@vkw.at a écrit :
> Hello everybody
>
> When reading the code of Module Dialog,
> I noticed something that I do not understand.
>
> There is an exported procedure
>
> PROCEDURE SetGetHook*(h: GetHook);
> that doesn't apear in the interface and it is
> possible to call that procedure from outside.
>
> Can someone explain that behaviour?
>
> Gerhard Marent
>
Hello Gerhard,
Oberon microsystems explained in a mail of 2006 that:
types which extend Kernel.Hook are a configuration mechanism
intended to be used only by framework programmers. "Normal"
BlackBox clients should neither use nor see hooks. That's why
DevBrowser masks them out.
Andrew Thomas added:
Marc at OMsystems has solved the puzzle. Look at the source code
for the Browser, in particular the procedure IsHook. Looking
father down to the Browser procedure you see that you can edit
the opts string so that the Hook shows up.
and Dominik Gruntz showed that:
Btw, they are shown if you use the &-Option of DevBrowser, e.g.
"DevBrowser.ShowInterface('c&')"
Regards.
Gérard