[bfprog] Unregistering Handlers
Steven Hartland
killing at multiplay.co.uk
Sun Jul 24 12:51:34 PDT 2005
Its not very fancy I can tell you that :( I considered proxying
all the calls but as we dont have any concrete info on what
calls require what parameters to be accepted that would be
very messy :(
I think its just better we ensure that DICE adds this functionality
in the next patch than put very dirty workarounds in.
Steve / K
----- Original Message -----
From: ""Einar S. Idsø"" <esi at itk.ntnu.no>
> Like Steven said, this method don't seem to exist. I don't know what
> technique Steven uses in his Modmanager, though I am looking forward to
> seeing his work, but, depending on why you need to unregister the event
> handler, you might get by by simply reassigning the function being
> called to do absolutely nothing? It would still incur the time to call,
> obviously, but just let it pass/return immediately.
>
> You could use a simple dummy-function for this which takes nothing but
> key/val arguments, so that each and every function you want to
> cancel/unregister can be redirected to this single dummy-function.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to postmaster at multiplay.co.uk.
More information about the BFProg
mailing list