Re: Exotica & crash
Talvitie wrote:
>
> Todd wrote:
> >Doh, I think I do have a clue... mabie your drawing pixels outside
> >the surface(screen).
> No I'm not. Well I might been in the file I send you, but I fixed it and it
> still crashes.
> Am I writing into vars(in DoThe3D) that are used by exotica?
Unless you are using a global variable that is defined either in
ewin32lib.ew or exoitca_api.ew inside DoThe3D(), I wouldn't imagine
that would be the case. I skimmed through DoThe3D() code and didn't
see any Exotica routines, right?
> >Currently, Exotica doesn't like that sort of
> >thing. I'll slap Exotica around and make it like it in the next version.
>
> This will make the routine slower so I have a suggestion:
> include global integer into your .ew file which will choose from safe and
> unsafe modes.
> Safe (default?) = you can't crash
> Unsafe = Fast routines.
> User could then use Safe to test and Unsafe after this when having need for
> speed
That is a good idea. But the slow down will only occur if the you draw
outside the screen area, just like what I have now with the RECT_BLIT
routines that I'm currently working on.
But since I'm wanting to make some CLIPPING routines some time down
the road, I can go ahead a make a single Exotica routine
that the user can set if they want clipping activated or not
which would effect all Exotica functions that uses clipping.
> Thanks for trying to help :)
No problem. If you have any other question about this , please ask.
I will try to look at your proggy again sometime this weekend to
try to see what's up.
> --Talvitie
|
Not Categorized, Please Help
|
|
