Re: [AD] Removing the default close button support

[Peter Wang <tjaden@xxxxxxxxxx>]

On 2002-10-29, Eric <ebotcazou@xxxxxxxxxx> wrote:
> As already explained many times, I think we should get rid of the default 
> behaviour of the close button, i.e shutting down the program without the 
> express consent of the primary thread.
> 
> This would imply that the close button is disabled until the user registers a 
> close button callback function,

Agreed, of course.

> so we don't need two functions anymore in order to handle it.

Not so sure about this.

> Therefore I propose to get rid of both set_window_close_button() (useless now) 
> and set_window_close_hook() (nasty name: Allegro uses callbacks, not hooks) 
> and add set_close_button_callback(). For backward compatibility, 
> set_window_close_button() would be a dummy function and 
> set_window_close_hook() redirected to set_close_button_callback().

Well, it's not the first time "hook" has been used instead of "callback"
so I think it should just be left as is.  (And IMHO Allegro usually
means "hook" where it has "callback".)

-- 
王浩禎