@Snuffy
So it seems it works correctly on EUAE, just slow, but I guess that holds for all software.
The bouncing ball demos however can be tweaked to be much faster (using selective refresh), but the way it is implemented is to satisfy GFX cards running at their real speed. It runns fine on e.g. 68060 with Cybervision 64 3D. The demos are not suppoosed to run under lower specs. For lower specs => use BlitzBasic2 instructions.
Quote:
4. Output Pass-0 compile window; Output Pass-1 window
5. GrimReaper: Amiblitz3 (Crashed)
hm... would need further investigation.
Quote:
12. A small 'request' window was in the middle of PED output window:
"This action is not allowed while executing a program.
Should PED do a PANIC program kill?"
Doing a PANIC kill is not the right thing to do. Amiblitz3 asks you this if you try to edit something in PED while the program is still running. This is because the program could be stuck in a deadlock and you even can't save your work. But during regular usage, this should be no option, only if you are in PANIC!
I corrected the other thing in sourcecode.
(it's damn hard to keep all the 1000th of files up to date!)
> It seems different source programs have different results.
Well, that's what different source programs are supposed to do...
Actually I see only one bug, the Grim Reaper on some progs.
When asking for the libs, I wanted to see the libs in LIBS:, because they are preferred over the local ones .
Copying them accross to LIBS: might help.
It is correct that the simple demo give a reaper hit, while the 100Hz demo runns smoothly without any trouble?
That would give us a hint what might be wrong, since the two progs are almost identical.
Edited by Wanderer on 2009/5/10 22:39:51