> On 2022-01-10, at 8:57 AM, christoph.thiede at student.hpi.uni-potsdam.de wrote:
> 
> Hi Marcel, Tim, all,
> 
> with this preference enabled, I would have expected that I would be able to perform all common code management operations in an image that has no access to the changes file. However, here are some things that still fail under this circumstance:
> 
> * load/merge a Monticello version - MethodAddition>>#createCompiledMethod does not honor AcceptsLoggingOfCompilation, and neither does MCMethodDefinition>>#asMethodAddition.
> * re-classifying methods in a browser (or renaming a category)
> 
> See also all senders to #logMethodSource:forMethodWithNode:inCategory:withStamp:notifying:. I wonder whether this method should check AcceptsLoggingOfCompilation itself, or whether we need to make all senders aware of that preference. It would be really great to be able to open multiple instances of an image in parallel for throwaway experiments. :-)

Ah, I thought I had noticed sometihng like that. Would be nice to solve that before the release


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Hmm. That’s the second time today I’ve seen a Word doc eat a man’s soul. Time for a bug report...