Hi Dan:
The problem with the demo is that rt_task_delay() stalls the RTL task while a
whole bunch of other state machines need attention.
Think of KCL objects as small inter-related finite state machines. It may be be
apropriate to wait for one, but you must be prepared to act for all the others.
An individual rtl_task for each fsm would quickly become unmanageable.
Over the weekend I have given up on Qt and decided that FLTK will be a much
better GUI - check it out. I'm holding
onto KDE though. The power of FLTK is FLUID. At last, I can forget about
fucking around with the geometry of the
windows and dialogs.
Please, try to think through the demo file you emailed. I have some ideas on
how to use YACC to simplify writing
KCL classes and virtual functions.
I'll be busy this week catching up with customers... but I'll be back.
Regards,
Pierre
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
