Rene Brun writes: > > If people think that diabling TPad::Range and SetPad, I can undo > this restriction. This will make the guiviewer working again without > any changes. Let me know. It depends on how the word ``Editable'' is interpreted. A TPad::Range doesn't change what is in the Pad, just how it is displayed. At times, an interactive user should be able to change a pad's range, but not able to modify its contents. So, yes, maybe Range() and SetPad() should be excluded from the lock-out. If Range() is excluded, guiviewer.cxx still needes the calls to SetEditable(kFALSE) to be moved after the Draw() calls in order to function properly in this new scheme. -Brett.
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:47 MET