Re: [AL] XFree86 3.3.x and Allegro 3.9.36WIP

[Rudolf P. <rp...@du...>]

On Thu, Jun 28, 2001 at 11:23:55AM +0200, Santiago Romero wrote:
> El Miércoles, 27 Junio 2001, usted escribió:
> 
> >> The problem occurs when using a DGA driver. But
> >> Allegro 3.9.36 (contrary
> >> to *.34) contains an X fullscreen driver.
> >
> >This may sound silly, but what is the point of having
> >a full screen X driver? Why not just compile the
> >program for the console instead?
> 
>  Now my friend has a new problem with allegro programs...
> after running some of them, when exiting, the keyboard
> remains captured and he has to kill X to recover keyboard...

Did you call allegro_exit()? Does it also occur with the
included examples?
>From <all...@ca...> Thu Jun 28 22:16:28 2001
Received: from mx2.alphalink.com.au [202.161.124.199] by canvaslink.com with ESMTP
  (SMTPD32-6.00) id A4FA15E0296; Thu, 28 Jun 2001 22:16:26 -0400
Received: from desky.localdomain (d08-ds9-mel.alphalink.com.au [202.161.101.136])
	by mx2.alphalink.com.au (8.11.4/8.9.3) with ESMTP id f5T2DbE29956
	for <al...@ca...>; Fri, 29 Jun 2001 12:13:37 +1000
Received: (from tjaden@localhost)
	by desky.localdomain (8.11.1/8.9.3) id f5T2HbB32390
	for al...@ca...; Fri, 29 Jun 2001 12:17:37 +1000
Date: Fri, 29 Jun 2001 12:17:37 +1000
From: Peter Wang <tj...@al...>
To: al...@ca...
Message-ID: <200...@al...>
Mail-Followup-To: al...@ca...
References: <4.3...@ma...> <3B3...@ho...> <00a201c0ff4c$4e84d760$6b8324d5@zephyr> <3B3...@ho...> <4.3...@ma...>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <4.3...@ma...>; from np...@st... on Wed, Jun 27, 2001 at 11:28:35PM +0200
Subject: Re: [AL] Slow MIDI in newest WIP?
Precedence: bulk
Sender: all...@ca...
Reply-To: al...@ca...
X-UIDL: 294172769
Status: O
Content-Length: 587
Lines: 11

On 27 Jun 2001, Niklas Pettersson <np...@st...> wrote:
> A lot of posts now about mid.. =)
> But what has changed since 3.12 then (concerning the midplayer)?

I couldn't find anything definite.  If you have time, please try
some older WIP versions (3.9.32 would be a good point to start).  It
would help to know at which release the problem started to occur.

-- 
tj...@us... - http://www.alphalink.com.au/~tjaden/
SLOOPAGE (SLU paj), n.  The tendency of hot dogs, hamburgers, and sandwich
contents to slip from between their covers.  -- Rich Hall, "Sniglets"
>From <all...@ca...> Fri Jun 29 05:58:09 2001
Received: from mail.libertysurf.net [213.36.80.91] by canvaslink.com with ESMTP
  (SMTPD32-6.00) id A1311D380194; Fri, 29 Jun 2001 05:58:09 -0400
Received: from zephyr (213.36.130.217) by mail.libertysurf.net (5.1.053)
        id 3B3BE14A0000CEB8 for al...@ca...; Fri, 29 Jun 2001 11:56:41 +0200
Message-ID: <00d101c10081$e4a0a900$d98224d5@zephyr>
From: "Eric Botcazou" <ebo...@li...>
To: "Allegro mailing list" <al...@ca...>
References: <4.3...@ma...> <3B3...@ho...> <00a201c0ff4c$4e84d760$6b8324d5@zephyr> <3B3...@ho...> <4.3...@ma...> <200...@al...>
Date: Fri, 29 Jun 2001 11:57:07 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Subject: Re: [AL] Slow MIDI in newest WIP?
Precedence: bulk
Sender: all...@ca...
Reply-To: al...@ca...
X-UIDL: 294172766
Status: O
Content-Length: 1551
Lines: 37

> I couldn't find anything definite.  If you have time, please try
> some older WIP versions (3.9.32 would be a good point to start).  It
> would help to know at which release the problem started to occur.

I've found the problem.

Do you remember when I modified some time ago the platform-independent timer
code because there was a bug related to the reinstallation of timers ?
This bug might actually have been a feature ;-) and the core MIDI player,
that extensively uses timer reinstallation, seems to be relying on it.

[Before my patch, when you reinstalled a timer, the new delay started from
the last tick and not from the current time. This proves totally unusable
when you switch from a large period to a small one. Therefore my patch made
the new delay start from the current time].

I now realize that I changed the semantics of install_int() when the timer
is already installed, but the docs are not very clear: "Adds a function to
the list of user timer handlers, or if it is already installed, adjusts its
speed".

Shawn, could you confirm that ?

If so, the safest solution would be to revert to the old semantics and make
it explicit in the docs. However, this would break the new keyboard driver,
so that:
- either we also revert to the old keyboard driver, but this means we
  definitely throw away the MT timer driver under Windows because of
  the Win2k bug,
- or we add a new API call that makes the timer restart:
       int restart_int_ex(void (*proc)(), int speed);

That's all ;-)

--
Eric Botcazou
ebo...@mu...