This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Mon, 2003-07-21 at 04:17, Gary R. Van Sickle wrote: > > Unless there will ever be a need to ask a page whether > > it would take activation in the future, but not activate it immediately, > > even if it is possible to do so, I think the 2 calls should be merged. Will > > there ever be such a case? > > I cannot think of one. It exists soley to give OnActivate a "default return > code". It *can't* be called anywhere else, since in the general case, > OnAcceptActivation won't know if it needs to refuse activation until after > OnAccept is called. Hmm. My intention when I suggested a query method was for it to be called *instead* of OnActivate, and OnActivate only called if it returned true. Will doing that break anything? For clarity: if (OnAcceptActivate()) OnActivate() Rob -- GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.
Attachment:
signature.asc
Description: This is a digitally signed message part
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |