Thanks mariano
We are trying to find all the places that are writing to disc and others
and we should be able to turn them on and off.
Stef
Le 31/5/16 à 14:29, Mariano Martinez Peck a écrit :
There used to be a #discardChanges or #forgetChanges or some message
like that that allowed one to discard .changes file. But I cannot seem
to find that anymore in 5.0. Maybe it is #closeSourceFiles.
The reason could be becuase the do-it (same as executing a .st) are
tracked in the changes file. Another possibility is to explicitly
disable the announcers, hoping that the changes writing happens via
announcements:
SystemAnnouncer uniqueInstance suspendAllWhile: [ self executeYourScript ]
Hope this helps.
On Tue, May 31, 2016 at 8:22 AM, Valentin Ryckewaert
<valentin.ryckewa...@gmail.com <mailto:valentin.ryckewa...@gmail.com>>
wrote:
Hello everyone,
I'm trying to execute a script from a .st file on a image whose
changes file isn't writable.
When i do this, I'm getting a bug with primSize... It looks like
get size of the file need write access ?
The exception :
Primitive failed: primitive #primsize: in MultiByteFileStream
Does someone have an idea of the reason of this problem please?
Valentin
--
Mariano
http://marianopeck.wordpress.com
