Re: [AL] set_gfx_mode problem

[Clarence D. <mr...@m-...>]

Hello,

I reported the same problem.  Running debug I discovered that it was the 
keyboard shutdown routine causing the access violation.  It wouldn't crash 
all the time however, just occassionally.

Try running your test app without installing the keyboard just to see if 
that solves the termination problem.

I moved up to the lastest Allegro library, v4.1.0, and the issue no longer 
exists.  See if you can try that too.

Now, for the other issue I had, with the iconified application not going 
away on program termination until I click the icon, I discovered this was 
being caused by my using TweakUI's "Activation follows mouse (X-Mouse)".

Apparantly, the application loses focus when it's terminating because of 
the X-Mouse, and is set to the PAUSE state, even though I had set the 
BACKGROUND_AMNESIA state in my prog.

Now, no other applications I use on W2K have any trouble with X-Mouse, so 
I was wondering if the author could change the code so that the thread 
remains in a background running state as the application terminates?

Best Regards,
Clarence Donath
B1oodnose on EFNet #allegro


On Sun, 28 Jul 2002, Ulrich Doewich wrote:

> Problem: after having successfully set a graphics mode, and before
> accessing the graphics buffer, exiting the application causes an access
> violation.
> 
> My environment: Windows 2K with Allegro (CVS snapshot from the 27th)
> compiled for MingW32. The graphics mode I use is
> GFX_AUTODETECT_WINDOWED. I set the graphics mode in my app init code
> (part of the WinMain function), so the app window hasn't been displayed
> yet at this point. If I now force an exit (e.g. simulating a problem
> during init of my app), I get the said access violation.
> 
> Any ideas? Is the Allegro graphics code in an unstable condition at this
> point?
> 
> BTW: a set_gfx_mode call with the GFX_TEXT driver right after setting
> the GFX_AUTODETECT_WINDOWED mode has the same effect: access
> violation...
> 
> Regards,
> Ulrich.
>