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

[Horst Herb]

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?

Horst