[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Ahh... thanks Eric. Sorry for all these newb' questions, but all my
experience with Allegro before now was with Watcom and djgpp. ^_^;;
When your suggested additions were put into my program it responded the
same, so the OSX version does need this functionality implemented
before the next release.
- Charles
--- Eric Botcazou <ebotcazou@xxxxxxxxxx> wrote:
> > Also, something I noticed about OSX command line allegro tools --
> as
> > soon as allegro_init() or install_allegro are called the icon for
> the
> > program pops up on the dock and the component manager errors appear
> in
> > the terminal. Is there a way to supress this behaviour for console
> > apps?
>
> The standard way is to define ALLEGRO_USE_CONSOLE before including
> allegro.h
> (but I don't know if it has any effect for the MacOS X port) and to
> call
>
> install_allegro(SYSTEM_NONE, &errno, atexit);
>
> instead of allegro_init(), assuming your code uses only files
> manipulation
> and images manipulation routines from the library.
>
> --
> Eric Botcazou
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers