Not sure why not working but binding window will work.

David Botton
On Sun, Mar 29, 2015 at 10:57 AM Pascal <blady-...@users.sf.net> wrote:

> Hello David,
>
> It seems that On_Key_Press_Handler does not work with
> gnoga.gui.View.Console.Console_View_Type.
> Thus my handles are bound to window:
>       Gnoga.Application.Singleton.Initialize (IntWindow);
>       IntWindow.On_Key_Press_Handler (On_Key_Press_Event'Access);
>       IntWindow.On_Key_Up_Handler (On_Key_Press_Event'Access);
>       IntWindow.On_Key_Down_Handler (On_Key_Press_Event'Access);
>       IntWindow.On_Character_Handler (On_Key_Char_Event'Access);
>
> Is it correct?
>
> Regards, Pascal.
> http://blady.pagesperso-orange.fr
>
>
> Le 23 mars 2015 à 03:07, Rabbi David Botton <da...@botton.com> a écrit :
>
> > If you place the handler on the window, do you find the event is
> received there even if not at the view?
> >
> > On Sun, Mar 22, 2015 at 9:32 AM Rabbi David Botton <da...@botton.com>
> wrote:
> > It seems events are consumed by the browser itself, for example page
> down is consumed by the browser on a view with a scroll bar.
> >
> > David Botton
> >
> >
> > On Sat, Feb 28, 2015 at 8:18 PM, Rabbi David Botton <da...@botton.com>
> wrote:
> > I will give a try tomorrow and get to your other requests by tomorrow.
> Last week worked hard on hardening the connections. Still have a few back
> and forths going in with Dmitry but nailed down a number of issues.
> >
> > David Botton
> >
> >
> > On Saturday, February 28, 2015, Pascal <blady-...@users.sf.net> wrote:
> > Hello David,
> >
> > It seems that On_Key_Press_Handler works only bind to
> Gnoga.Gui.Window.Window_Type but not bind to gnoga.gui.View.Console.
> Console_View_Type.
> >
> > Can you confirm?
> >
> > The different key handlers behave strangely regarding the key stroke:
> >
> > a:
> > KEY_DOWN, 65
> > KEY_PRESS, 97
> > On_Key_Char_Event,a
> > KEY_UP, 65
> > --> key down and up have upper case code of character a!
> >
> > A:
> > KEY_DOWN, 16
> > KEY_DOWN, 65
> > KEY_PRESS, 65
> > On_Key_Char_Event,A
> > KEY_UP, 65
> > KEY_UP, 16
> > --> ok same code of character a in upper case
> >
> > tab:
> > KEY_DOWN, 9
> > KEY_UP, 9
> > --> no key press nor character event!
> >
> > <shift>:
> > KEY_DOWN, 16
> > KEY_UP, 16
> > --> no key press event!
> > --> what is the coding of key down and up?
> >
> > =:
> > KEY_DOWN, 187
> > KEY_PRESS, 61
> > On_Key_Char_Event,=
> > KEY_UP, 187
> > --> what is the coding of key down and up?
> >
> > 5:
> > KEY_DOWN, 101
> > KEY_PRESS, 53
> > On_Key_Char_Event,5
> > KEY_UP, 101
> > --> what is the coding of key down and up?
> >
> > <page-down>:
> > KEY_DOWN, 34
> > KEY_UP, 34
> > --> no key press event!
> > --> what is the coding of key down and up?
> >
> > Is it the same on your side?
> >
> > Thanks, Pascal.
> > http://blady.pagesperso-orange.fr
> >
>
>
> ------------------------------------------------------------
> ------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Gnoga-list mailing list
> Gnoga-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gnoga-list
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Gnoga-list mailing list
Gnoga-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnoga-list

Reply via email to