[XForms] Adding more calls to support fl_register_client_callback()?

Jean-Marc Lasgouttes Jean-Marc.Lasgouttes at inria.fr
Fri Apr 2 04:05:00 EST 2004


>>>>> "Angus" == Angus Leeming <angus.leeming at btopenworld.com> writes:

Angus> To subscribers of the xforms list
Angus> On Thursday 01 April 2004 2:41 am, Jeff wrote:
>> XInternAtom() is used to set the atom ID and must be called to set
>> an atom BEFORE client messaging can be used. XSendEvent is used to
>> send the event.
>> 
>> Now, do we want have a user use the raw X lib calls, or encapsulate
>> them in an fl_*? Like:
>> 
>> Atom fl_intern_atom(FL_FORM *form, char *atom_name, Bool
>> only_if_exists);

Angus> Would wrapping the X lib call give the user anything other than
Angus> a familiar fl_... ? If not, then I guess that we should use the
Angus> raw X lib call.

Well we could forget about the notion of atoms.
fl_create_client_message()
fl_send_client_message()
...

However, I do not know how these atoms are used in real life...

Angus, I do not think that there is any place in xforms where you need
to manipulate X objects to use a feature. Hmm, let's grep in
forms.h... OK, there are fl_XNextEvent and its friends, but I do not
know how common it is to use them.

Angus> Could you give us an example of all this in action. It's hard
Angus> to make any meaningful statements without some code.

Actually, it would be nice to have a demo program for the client
message feature. 

JMarc



More information about the Xforms mailing list