a while back , a threaded draft solution was offered for a slow tree browser ? - any progress in gmClinicalRecord towards this problem ? - I was thinking some sort of callback interface might work, like the python twisted framework. e.g. the browser and the journal manage their own threaded callback functions, which update their respective gui, and gmClinicalRecord has a callback register function, and has an incremental fetch, which fetches by health issue/episode , and returns e.g. an iterator whose next() function fetches the next episode.
- is this planned for the next release , or is there a testing version available? _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
