Open GoogleCodeExporter opened 8 years ago
does this happen with the default or experimental interpreter?
Original comment by corbi...@gmail.com
on 23 Apr 2012 at 6:07
This happened with the default interpreter. Enabling experimental interpreter
does not work: After the "Preparing Interpreter" screen has finished addi
crashes every time after entering the first command.
Original comment by dennis.r...@googlemail.com
on 23 Apr 2012 at 7:59
Interesting, what is your first command?
Original comment by corbi...@gmail.com
on 24 Apr 2012 at 3:57
Doesn't matter. "for i=[1:3]", "a=7" or even a blank line...addi crashes all
the time.
Original comment by dennis.r...@googlemail.com
on 24 Apr 2012 at 5:19
Does the "Preparing Interpreter" show up every time you go to try to use the
experimental interpreter? Or did it only show up the first time you tried to
use it?
Original comment by corbi...@gmail.com
on 24 Apr 2012 at 11:49
The message shows up every time for a couple of minutes and disappears then. On
the next command addi crashes.
Original comment by dennis.r...@googlemail.com
on 25 Apr 2012 at 7:39
Ah, that means unpacking all the files Addi experimental interpreter is
dependant on failed. I don't yet have a good error message for this. This
will be fixed. Do you have Addi installed internally or on the SD card. Are
you very low on space for new apps? Could you try uninstalling, making sure
there is a couple 100 MB free internally and install again. Regardless, more
debugging of the interpereter is coming and it does solve the issues you have
listed.
Original comment by corbi...@gmail.com
on 27 Apr 2012 at 3:50
On sd card, 4.7GB free. Uninstalling and reinstalling addi made the
experimental interpreter work. Described problem does not occur with
experimental interpreter.
Original comment by dennis.r...@googlemail.com
on 30 Apr 2012 at 9:23
I will make it so I can better detect installation problems in the future and
hopefully make it so they are less likely to occur. I am glad the experimental
interpreter fixes this issue!
Original comment by corbi...@gmail.com
on 30 Apr 2012 at 5:06
Original issue reported on code.google.com by
dennis.r...@googlemail.com
on 21 Apr 2012 at 10:41