[Top][All Lists]

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

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

From: Horst Herb
Subject: Re: [Gnumed-devel] self.locked in gmTmpPatient
Date: Mon, 2 Jun 2003 07:41:10 +1000
User-agent: KMail/1.5

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 themselves correctly. 
It should be irrelevant which module triggers that message, and when.
How else could a modular plugin architecture work?


reply via email to

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