Welcome, Guest. Please login or register.

Author Topic: openscreen problems!!!  (Read 5429 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: openscreen problems!!!
« on: March 22, 2004, 08:20:12 PM »
2 things I noticed:

1) you open Intuition.library by hand. Most compiler allready
provide a symbol IntuitionBase in the standard linklib.

So maybe you are closing the IBase, and than the link-lib-code
tries to do the same when the prog terminates.

Try to put some printf()s or similar in between Delay(),
CloseScreen(), CloseLibrary() and return to find out
where it actually hangs.

2) You use a ExtNewScreen-structure. Better only use tags.
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: openscreen problems!!!
« Reply #1 on: March 22, 2004, 09:31:46 PM »
O.k. got me there ....

a) use a scanf, this will put the prog to an halt till
you hit return in the shell-window.

b) put a delay(200) between CloseScreen and CloseLibrary()
to see where the problem lies. Closing a screen may be
delayed to the next vertical blank, enough time for your
code to hit that suspicious CloseLibrary().

c) remove CloseLibrary, and if that helps also remove OpenLibrary
and put extern in front of the IntuitioBase-definition.


Bout text on Screens:

There is IntuiText() for that, but you shouldn't use that
directly on a screen, but open a window (backdrop-wins are
praticly invisible), and it would be off little use since
we want to know what happens when you close that screen.

It would also be nice if you could tell us what compiler you
use and with which options.
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else