[Starkit] corruption of starkits by double access

[Jean-Claude Wippler]

Steve Blinkhorn wrote:

> From our experiments, building identical starkits write-enabled or
> not, it seems that a starkit that is write-enabled is written to even
> though no change has been made.   In other words some commit or other
> happens, even when no change has been made, and this causes the
> problem we started with.   Have I understood this correctly?

Well, the underlying Mk4tcl would not do anything on commit if there  
has been no change.  But yeah, probably something in the VFS layer  
writes a value back (even if it's the same).

Hmmm.  My hunch is that it's a "-1" in the parent field of the dirs  
view, row 0.  Lemme check.  Yep, that's it: line 338 in mk4vfs.tcl in  
tclvfs.  If you change that to not set the value if row 0 already  
exists (with its parent set to -1), then I expect the commit won't do  
a write anymore.

-jcw