[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] self.locked in gmTmpPatient

From: Karsten . Hilbert
Subject: Re: [Gnumed-devel] self.locked in gmTmpPatient
Date: Mon, 2 Jun 2003 00:06:56 +0200 (MEST)

> On Sun, 1 Jun 2003 23:13, Karsten Hilbert wrote:
> > When controlling GnuMed from third-party applications it will
> > be necessary to lock GnuMed into the patient selected by the
> > controlling application. It is dangerous to allow the user to
> > change the active patient in that GnuMed instance since the
> > controlling application will still think it deals with the
> > initial patient. This is what gmCurrentPatient.locked is used
> > for.
> No. When the patient gets changed, the message "patient changed" is
> dispatched  - all widgets depending on a patient will then update
> correctly. 
No again :-))   Or else I'd be massively interested in learning how you are
going to teach TurboMed (the commercial application my parents are using) or
MediStar (the commercial app I am using) or MCS/IsyNet (the commercial app I
am using at my pediatrics post) to listen to GnuMed "patient changed"


+++ GMX - Mail, Messaging & more +++
Bitte l├Ącheln! Fotogalerie online mit GMX ohne eigene Homepage!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]