# To subscribers of the xforms list from Steve Lamont <spl@ncmir.ucsd.edu> :
> I know I asked about this ages ago, but is there any chance you could
> add the function
>
> int fl_input_changed(FL_OBJECT *obj)
> [...]
I suppose that's okay if it's okay with TC but I'm not sure why you
can't use a filter function to detect and record this information.
For example:
int filter( FL_OBJECT *obj, const char *old, const char *new, int c )
{
obj->u_ldata = 1;
return FL_VALID;
}
void cb( FL_OBJECT *obj, long parm )
{
obj->u_ldata = 0;
}
int check_changed( FL_OBJECT *obj )
{
return obj->u_ldata;
}
[...]
fl_set_input_filter( fd_try->i1, filter );
fl_set_input_filter( fd_try->i2, filter );
fl_set_input_return( fd_try->i1, FL_RETURN_END );
fl_set_input_return( fd_try->i2, FL_RETURN_END );
[...]
if ( check_changed( fd_try->i1 ) )
handle_change( fd_try->i1 );
if ( check_changed( fd_try->i2 ) )
handle_change( fd_try->i2 );
While it clearly is more application programmer code, I'm not sure
that adding additional functions to an already large API is the right
way to go.
My opinion, of course.
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuhs.mil or see
http://bob.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://world.std.com/~xforms
List Archive: http://bob.usuhs.mil/mailserv/list-archives/
This archive was generated by hypermail 2b29 : Mon Jul 10 2000 - 20:48:45 EDT