[Top][All Lists]

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

[Gnumed-devel] self.locked in gmTmpPatient

From: Karsten Hilbert
Subject: [Gnumed-devel] self.locked in gmTmpPatient
Date: Sun, 1 Jun 2003 15:13:47 +0200
User-agent: Mutt/

Sorry Syan,

but this got nothing to do with thread interlocking (which may
become necessary but isn't in the design at the moment).

I do admit to not having documented this except for, perhaps,
an odd posting somehwere so here goes:

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

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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