Re: [AD] TODO List for Allegro

[guilt <karthikkumar@xxxxxxxxxx>]

hi,

OK, I got the error :P As such the problem isn't with the Accelerator
table... Two options are available to fix it.

1. It may that we may need a custom EdAccelProc to work "with" Allegro's input. 

2. Let Allegro's own input handler do the job ... In the 4.1.15 WIP
only VK_F! works.. the VK_ADD+CONTROL doesn't work for me at all :P
Only when I click on the menu.. it increases the speed.

On Fri, 16 Jul 2004 10:45:54 +0200, Eric Botcazou
<ebotcazou@xxxxxxxxxx> wrote:
> > 1. What "is" the dxwindow test error exactly? What is the expected
> > behaviour and what is the current/observed behaviour? I did run it. I
> > didn't find any problems IMO.. and modifying WndProc does make the
> > acceleration go smoother.
> 
> IIRC the Allegro keyboard (i.e. the 'B') doesn't respond anymore after a
> Win32 menu was navigated with the keyboard, or the other way around.
> 
> > 2. Regards the HBITMAP, i would suggest that its better to preserve
> > the 8-bit originality than use makecol8 approximations. The current
> > version forces conversion of the 8 bit HBITMAPs into 24 bit. And.. it
> > would also be nice if there were a function called get_gdi_palette();
> > <-- for people wanting to use he 8 bit HBITMAPs.
> 
> I don't have a strong opinion on this one.  It can probably be removed from
> the list.
> 
> --
> Eric Botcazou
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
> 


-- 
V Karthik Kumar