[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] re: callback from event loop in wxPython
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] re: callback from event loop in wxPython |
Date: |
Sat, 31 Jan 2004 06:54:10 +0100 |
User-agent: |
Mutt/1.3.22.1i |
> could also use a polling function as in (?) wxTimer,
You mean like setting up a timer that periodically calls
acquire_scripting_portal_events() ? Should work, certainly,
but sounds like being heavy on the main thread as opposed to a
dedicated thread.
My favourite would still be to teach the main event acquisition
loop to go look at some socket each spin.
> still not sure why the gui needs remote controlling:
> can't it just do user input and display backend state?
Huh ? What you are asking seems to be: Why can't the GUI do
what a GUI usually does ?
As for why I need remote controlling:
- legacy medical practice app without document archive selects
a patient
- it attaches to gnumed
- it tells gnumed to call up its document archive plugin for
that patient
- it tells gnumed to stay locked onto that patient
- user works with the gnumed gui handling various documents
- user decides to add a vaccination for this patient - this is
possible but it is not possible to change to another patient
from inside the gui
- user "returns" to legacy app thereby releasing the gnumed
lock
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346