MAExternalFileModel does not belong to the Smalltalk
start-up list, and the
cached *baseDirectory* value is not updated by program. Consequently, when a
Pier image is moved from directory A to B, PRFiles keep referencing
'A/files' instead of 'B/files'.
Has this been designed this way by purpose?
Yeah, FileDirectory always represents an absolute path.
Maybe using FileDirectory wasn't such a good idea in the first place.
Maybe we should change it to a string to do a relative/absolute lookup
from the image directory? Or, oh well, we could use the Filesystem
framework
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch