mandel@vax.anes.tulane.edu (Jeff E Mandel MD MS) (01/24/91)
This may just be a reflection of the fact that I don't read manuals completely, but I seem to be having problems as a result of Lock Screen in HC 2.0 (I don't yet have v2). I have a project (for scheduling procedures in the operating room) which spans multiple stacks - one which contains most of the scripts, all XCMDs and resources, and which changes almost never, one which is an empty shell which is cloned and into which data for a given day is loaded by CL/1, and one which contains data applicable to all days, which evolves over time. This permits me to refine the code stack without having to worry about all those data stacks that people have created. The problem is that occasionally it is necessary to pop oer to another stack to read or write some data. Naturally, I would prefer to Lock Screen to avoid user confusion: on getData global theData Lock Screen push cd go to cd "dataCard" of stack "dataStack" put cd fld "theData" into theData pop cd Unlock Screen end getData Now without the Lock Screen, this works flawlessly, however, with Lock Screen, in some (but not all) cases fails with a "No such field" type error. When this happens, the problem is always fixed by removing the Lock Screen. Is this the way this is supposed to work, or is this a bug? Jeff E Mandel MD MS Asst Professor of Anesthesiology Tulane University School of Medicine New Orleans, LA
dmittman@beowulf.JPL.NASA.GOV (David Mittman) (01/25/91)
I have noticed that locking the screen also does not allow you to do something like the following: lock screen set the sharedText of fld "Foo" to true get fld "Foo" set the sharedText of fld "Foo" to false unlock screen In order to access the "other side" of the field (shared/unshared) you must have the screen unlocked. Anyone else see this, and is this a "bug"? - David