[AD] Contribution + exunicod.c + Kannada Greeting

[Harsha <nharsha@xxxxxxxxxx>]

Hi
 all

I have successfully added Allegro Kannada Greeting to exunicod.c I
need to submit my work, PLease provide me more information about how
to send My work when it will be approved etc..

Kannada is a Native Indian Language (People in Karnataka State of 
south India speak this language).

Eagerly waiting for the replies

Harshavardhana Reddy N. <harsha at linuxmail dot org >


On Sun, 27 Feb 2005 20:00:57 -0800,
alleg-developers-request@xxxxxxxxxx
<alleg-developers-request@xxxxxxxxxx> wrote:
> Send Alleg-developers mailing list submissions to
>        alleg-developers@xxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/alleg-developers
> or, via email, send a message with subject or body 'help' to
>        alleg-developers-request@xxxxxxxxxx
> 
> You can reach the person managing the list at
>        alleg-developers-admin@xxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Alleg-developers digest..."
> 
> Today's Topics:
> 
>   1. winXP ALT+key beep problem. (AJ)
>   2. Re: winXP ALT+key beep problem. (Evert Glebbeek)
>   3. Re: Add timeBeginPeriod(1) to wtimer.c (Evert Glebbeek)
>   4. Re: winXP ALT+key beep problem. (AJ)
>   5. Re: winXP ALT+key beep problem. (AJ)
> 
> --__--__--
> 
> Message: 1
> Date: Mon, 28 Feb 2005 00:05:01 +1100
> From: AJ <aj@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Subject: [AD] winXP ALT+key beep problem.
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> i offer a solution in:
> http://www.allegro.cc/forums/view_thread.php?_id=465241&#target
> 
> before i make a patch, can anyone comment on the need for the WS_SYSMENU
> flag in the CreateWindowEx() call.
> 
> aj.
> 
> --__--__--
> 
> Message: 2
> Date: Sun, 27 Feb 2005 20:45:19 +0100
> From: Evert Glebbeek <eglebbk@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] winXP ALT+key beep problem.
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> > i offer a solution in:
> > http://www.allegro.cc/forums/view_thread.php?_id=3D465241&#target
> >
> > before i make a patch, can anyone comment on the need for the WS_SYSMEN=
> U
> > flag in the CreateWindowEx() call.
> 
> Well, MSDN says the following:
> 
> WS_SYSMENU - Creates a window that has a Close (X) button in the non-clie=
> nt
> area.
> 
> So I guess that we need it if we want the close button. Can you confirm
> that this is the case?
> 
> Evert
> 
> --__--__--
> 
> Message: 3
> Date: Sun, 27 Feb 2005 20:57:00 +0100
> From: Evert Glebbeek <eglebbk@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] Add timeBeginPeriod(1) to wtimer.c
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> > Didn't think of 100...
> > More experiments: using 10 or more doesn't change the behavior. So
> > there's
> > an effect only when the requested precision is <10.
> 
> Ok. I suppose that need not be too surprising.
> 
> > > I agree. That'll make it post 4.2 material though.
> > So it seems. Sniff.
> 
> Don't worry. We want people to have a reason to upgrade, right? ;)
> 
> > When you begin to play around with my program (to be posted on the
> > forum)
> > then you might also see something of that sort: Having 3000 balls the
> > prog
> > needs about 10% cpu, 4000 balls result in about 50% cpu (on my 3GHz PC
> > at
> > work). That is with allegro unchanged.
> > No, adding timeBeginPeriod(1) to only the rest() function, 3000 balls
> > use
> > some 25-30%, but 4000 balls use hardly more than 30% also.
> > It's this kind of non-linear behavior which I find most irritating
> > here...
> 
> Yeah... it's also something I don't really understand. Maybe, if the
> granularity is lower, the processor load is more constant whereas if the
> load is lower it is more strongly peaked - but how that would tweak the
> measured load in the way you describe is beyond me. Depending on how the
> load is calculated and measured (this must involve some averaging as well=
> )
> the result may not be too accurate either. Just guessing though.
> 
> Evert
> 
> --__--__--
> 
> Message: 4
> Date: Mon, 28 Feb 2005 11:34:31 +1100
> From: AJ <aj@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] winXP ALT+key beep problem.
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> >>i offer a solution in:
> >>http://www.allegro.cc/forums/view_thread.php?_id=465241&#target
> >>
> >>before i make a patch, can anyone comment on the need for the WS_SYSMENU
> >>flag in the CreateWindowEx() call.
> >
> >
> > Well, MSDN says the following:
> >
> > WS_SYSMENU - Creates a window that has a Close (X) button in the non-client
> > area.
> >
> > So I guess that we need it if we want the close button. Can you confirm
> > that this is the case?
> 
> that is true.
> if you remove WS_SYSMENU from the CreateWindowEx()  you do not get the
> close button (and no minimize either).
> 
> lets put it back in.
> 
> i also found out that you can return a value in the win_msg_proc  that
> will prevent the beep.   its in the MSDN docs for the WM_?  msg that is
> sent when the user presses ALT+key.
> 
> (haven't time right now to check, got to go to work..)
> 
> aj.
> 
> --__--__--
> 
> Message: 5
> Date: Mon, 28 Feb 2005 14:43:18 +1100
> From: AJ <aj@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] winXP ALT+key beep problem.
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> the URL
> 
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/userinput/keyboardaccelerators/keyboardacceleratorreference/keyboardacceleratormessages/wm_menuchar.asp
> 
> documents the WM_MENUCHAR  allegro is sent when the user presses the
> ALT+key.
> 
> from the MSDN doc, it says if we return  MNC_CLOSE  in the hi word and
> the key in the lower word, it will not issue the beep.
> 
> i added this to the /allegro4.1.18/src/win/wwnd.c
> func  directx_wnd_proc()
> case WM_MENUCHAR :
>        return (MNC_CLOSE<<16)|(wparam&0xffff);
> 
> which prevents the beep.
> 
> aj.
> 
> AJ wrote:
> >>> i offer a solution in:
> >>> http://www.allegro.cc/forums/view_thread.php?_id=465241&#target
> >>>
> >>> before i make a patch, can anyone comment on the need for the WS_SYSMENU
> >>> flag in the CreateWindowEx() call.
> >>
> >>
> >>
> >> Well, MSDN says the following:
> >>
> >> WS_SYSMENU - Creates a window that has a Close (X) button in the
> >> non-client
> >> area.
> >>
> >> So I guess that we need it if we want the close button. Can you confirm
> >> that this is the case?
> >
> >
> > that is true.
> > if you remove WS_SYSMENU from the CreateWindowEx()  you do not get the
> > close button (and no minimize either).
> >
> > lets put it back in.
> >
> > i also found out that you can return a value in the win_msg_proc  that
> > will prevent the beep.   its in the MSDN docs for the WM_?  msg that is
> > sent when the user presses ALT+key.
> >
> > (haven't time right now to check, got to go to work..)
> >
> > aj.
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> 
> --__--__--
> 
> _______________________________________________
> Alleg-developers mailing list
> Alleg-developers@xxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
> 
> End of Alleg-developers Digest
>