Re: Anybody using the pre/post submit callbacks?

[Roger H. <rog...@mi...>]

Microspot do not use these. The small extra overhead and the extra
complexity do not worry me greatly but it would be better without them.
I doubt if anyone else (other than yourself) uses them, if so then they
should please speak now or be prepared to have to modify their code
to the new API.




On 1 Jul, 2005, at 03:20, James W. Walker wrote:

> A while back I added a callback mechanism specified via custom 
> elements:
>
> kQ3CallbackElementTypeBeforeRender
> kQ3CallbackElementTypeAfterRender
> kQ3CallbackElementTypeBeforePick
> kQ3CallbackElementTypeAfterPick
>
> I just realized that we could take a different approach which would be 
> more powerful and have less overhead.  One could create a custom 
> subclass of the View class, and override appropriate methods such as 
> submit-retained-for-rendering.  To make this possible, I would need to 
> make a couple of simple changes in E3View.c, and define some method 
> type constants in some public header.
>
> One nice thing about the approach I am suggesting is that you wouldn't 
> need separate before and after functions.  You could just do some 
> stuff before, call through to the standard method, and then do some 
> more stuff.   Furthermore, your method could actually submit a 
> different object than was passed to you, which is not possible with 
> the current callbacks.
> -- 
>   James W. Walker, ScriptPerfection Enterprises, Inc.
>   <http://www.write-brain.com/>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Quesa-develop mailing list
> Que...@li...
> https://lists.sourceforge.net/lists/listinfo/quesa-develop
>