[etoys-dev] Etoys: GetText-Richo.3.mcz
korakurider at gmail.com
Tue May 25 01:35:24 EDT 2010
On Tue, May 25, 2010 at 2:15 PM, Ricardo Moran <richi.moran at gmail.com> wrote:
> Uhhh, that's really bad... I got the same problem when I update today
> another package but it seemed to be a problem with my image only. I even
> tested this commit and I thought it was clean. Anyway, I'll try to reproduce
> the error and see if I can fix it.
> Thanks for the report.
I hit same problem too.
And it seems your changes to GetTextExporter2 in GetText-Richo.3 is
wrong; By browsing the version, content of GetTextExporter shown in
MC is old GetTextExporter, not GetTextExporter2. Entire exporter
stuff would be lost with the change :-<
BTW I believe that this time the version should be committed to
etoysinbox, not etoys.
> On Tue, May 25, 2010 at 2:04 AM, David Corking <lists at dcorking.com> wrote:
>> For your info, my Etoys trunk image offered me an emergency evaluator
>> a few seconds after merging the GetText-Richo.3 snapshot with the
>> In more detail:
>> 1. Monticello raised a PreDebug Window with a "warning" exception
>> while doing a three way merge of GetText-Richo.3
>> 2. I elected to 'Proceed'
>> 3. The image froze for 20 or 30 seconds (I tried to bring up a world
>> menu but no response. No response to command-period.)
>> 4. Stack dump appeared offering an emergency evaluator (but I could
>> not read it as morphs redrew on top of it.) The top of the stack was:
>> ***System error handling failed***
>> Original error: MessageNotUnderstood: AnObsoleteTextDomainManager
>> I attach a debug log from the original exception (1 above), but I
>> don't know how to dump the stack from the final image (4).
>> Hope that helps,
>> etoys-dev mailing list
>> etoys-dev at squeakland.org
> etoys-dev mailing list
> etoys-dev at squeakland.org
More information about the etoys-dev