Welcome, Guest. Please login or register.

Author Topic: SOLVED_GfxLibrary madness.. stack overflow WTF ?!!  (Read 4270 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show only replies by Jose
Re: SOLVED_GfxLibrary madness.. stack overflow WTF ?!!
« Reply #14 from previous page: February 27, 2007, 06:15:32 PM »
"    int main (int argc, char **argv)
    { LONG RtVl;

    if (RtVl = OpenStuff())
    ProcErr(RtVl);
This part is completely broken"

Absolutely.... forgot to update that part after finishing the other routines ... :-o

"/* Preserve old view 2 restore it on exit */
    oldVw = GfxBase->ActiView;
Is this safe?"

I stop multitasking 1st. I wanted to present the smallest code possible that still reproduced the bug ...

"     if (RtVl = MkScrn ())
    ProcErr(RtVl);
    else
    { Delay (6 * TICKS_PER_SECOND);
    }
This too."

forbid /permit...

"END:
    LoadView(oldVw);
    WaitTOF();
    DestroyScrn();
    CloseStuff();
    exit(0);
    }
I would just use OpenScreen() or other not so low level gfx api function..."

I want to preserve as much chip ram as possible, I'm assuming this will allow me to do that better (will also have to kill other screens too).
But probably the additional space that intuition takes is not much bigger (or at least not in chip ram). Will have to look at this in more detail later...
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show only replies by itix
Re: SOLVED_GfxLibrary madness.. stack overflow WTF ?!!
« Reply #15 on: March 01, 2007, 01:24:32 AM »
Quote

I want to preserve as much chip ram as possible, I'm assuming this will allow me to do that better (will also have to kill other screens too).
But probably the additional space that intuition takes is not much bigger (or at least not in chip ram). Will have to look at this in more detail later...


Intuition screens take the same amount if chip ram. You could call CloseWorkbench() to get rid of Workbench screen but usually it is not desired and such techniques are usable only on floppy systems...

Or just kill the OS and bang HW directly :-)
My Amigas: A500, Mac Mini and PowerBook