Den 09.12.2010 15:52, skrev Chip Nowacek:
To the matter: I don't understand why I can't accept a change to my comment in one of my classes. When I try to accept in the OB Package Browser, about a dozen calls in, #Utility is being sent #changeStamp and doesn't understand it. I am in the midst of sorting through the stack trying to figure out what happened. As you might imagine, it's a little discouraging for such a basic function to blow up. What makes it worse, I'm probably the cause of the problem - I just don't know what I screwed up. I am working in Pharo 1.1.1 and have loaded Magma and O2 per:
It seems the O2 tools have not been entirely updated to reflect 1.1 "deprecations" (in quotes since they were moved without leaving stubs pointing to their new location). Change Utilities changeStamp to Author changeStamp in the debugger that pops up, and hit proceed :) Cheers, Henry ps. in such cases, the simplest way to find a solution is usually to highlight the message (changeStamp in this instance), then either use alt-m shortcut or right click -> extended search -> implementors of it, and see which one fits what you attempt to do. Alternatively ask on the list if none seem to fit :)