Hello David, many thanks to you ;-)

Well, the section between marks seems not useful since "C" is already set:
         declare
            E : Keyboard_Event_Record :=
              Parse_Keyboard_Event (Message, Key_Press);
            C : Character :=
              Ada.Characters.Conversions.To_Character (E.Key_Char);
         begin
            Object.Fire_On_Key_Press (E);
            Object.Fire_On_Wide_Character (E.Key_Char);
<<<<<<< HEAD

            if E.Key_Code > 255 then
               C := Character'Val (0);
            else
               C := Character'Val (E.Key_Code);
            end if;

>>>>>>> END
            Object.Fire_On_Character (C);
         end;

Regards, Pascal.
http://blady.pagesperso-orange.fr


Le 2 juin 2015 à 21:41, Rabbi David Botton <da...@botton.com> a écrit :

> I have added to git your patch and added our key_code_list as 
> Gnoga.Types.Key_Codes.ads
> 
> Thanks!!
> David Botton
> 
> 
> On Thu, Apr 9, 2015 at 4:20 PM Pascal <blady-...@users.sf.net> wrote:
> Thanks, for your contributions.
> 
> Here is a modified package:
> 
> 
> More over, regarding browsers behaviors, I propose to split the Javascript 
> "which" code into "keyCode" and "charCode".
> Here is Firefox behavior:
> - a key                        -> keyEvent + keyCode + charCode + altKey 
> +ctrlKey + shiftKey + metaKey
> 2015-04-09 21:28:38.58 : KEY_DOWN, 65,NUL,FALSE,FALSE,FALSE,FALSE
> 2015-04-09 21:28:38.58 : KEY_PRESS, 0,'a',FALSE,FALSE,FALSE,FALSE
> 2015-04-09 21:28:38.67 : KEY_UP, 65,NUL,FALSE,FALSE,FALSE,FALSE
> 
> - F1  key                        -> keyEvent + keyCode + charCode + altKey 
> +ctrlKey + shiftKey + metaKey
> 2015-04-09 21:38:25.44 : KEY_DOWN, 112,NUL,FALSE,FALSE,FALSE,FALSE
> 2015-04-09 21:38:25.44 : KEY_PRESS, 112,NUL,FALSE,FALSE,FALSE,FALSE
> 2015-04-09 21:38:25.51 : KEY_UP, 112,NUL,FALSE,FALSE,FALSE,FALSE
> 
> KEY_DOWN and KEY_UP set always keyCode to javascript code and charCode to 
> null.
> KEY_PRESS set keyCode to null and charCode to Unicode character (i.e. 
> Wide_Character) for a common character and set keyCode to javascript code and 
> charCode to null for a special key.
> Thus it is easier to find out common characters and special keys.
> 
> Here is a GNOGA patch proposal:
> 
> 
> And modified test code:
> 
> 
> What is your feedback?
> 
> Regards, Pascal.
> http://blady.pagesperso-orange.fr
> 
> 
> Le 9 avr. 2015 à 05:33, Jeremiah Breeden <jeremiah.bree...@gmail.com> a écrit 
> :
> 
> > As a followup, Key_press seems to follow the ASCII table (where the key has 
> > an ASCII rep), at least for some of the browsers.  Worth looking into 
> > probably.
> >
> > On Wed, Apr 8, 2015 at 11:21 PM, Jeremiah Breeden 
> > <jeremiah.bree...@gmail.com> wrote:
> > I didn't find a Key_press table, but for key_down and key_up, 
> > javascripter.net suggests:
> > http://www.javascripter.net/faq/keycodes.htm
> >
> > I don't have a way to verify all of those, but come cursory checks versus 
> > what you posted here seem to match.
> >
> > On Tue, Apr 7, 2015 at 5:45 PM, Jeffrey R. Carter <jrcar...@acm.org> wrote:
> > On 04/07/2015 01:02 PM, Pascal wrote:
> > > So I went deeper in Javascript particularity particularly with the help 
> > > of:
> > > http://javascript.info/tutorial/keyboard-events
> > >
> > > Thus Key_up and Key_Down occur for each key press and release then key 
> > > code is apparently not so standardized across browsers.
> > > See http://unixpapa.com/js/key.html.
> > >
> > > Nevertheless I provide a package Key_Code_List with the correspondance 
> > > between key and code as I found it on my Mac, Safari and French keyboard.
> > > Other OS and browsers and keyboard may give other couples.
> > > Please come back to me with the couples or add them directly in the 
> > > package.
> > With my US keyboard and Firefox, Insert gives
> >
> > 2015-04-07 14:36:34.43 : KEY_DOWN, 45,FALSE,FALSE,FALSE,FALSE
> > 2015-04-07 14:36:34.43 : KEY_PRESS, 0,FALSE,FALSE,FALSE,FALSE
> > 2015-04-07 14:36:34.48 : KEY_UP, 45,FALSE,FALSE,FALSE,FALSE
> >
> <...>
> > HTH
> >
> > --
> > Jeff Carter
> > "Ada has made you lazy and careless. You can write programs in C that
> > are just as safe by the simple application of super-human diligence."
> > E. Robert Tisdale
> > 72
> >
> 
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> Gnoga-list mailing list
> Gnoga-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gnoga-list
> ------------------------------------------------------------------------------
> _______________________________________________
> Gnoga-list mailing list
> Gnoga-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gnoga-list


------------------------------------------------------------------------------
_______________________________________________
Gnoga-list mailing list
Gnoga-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnoga-list

Reply via email to