[ruby-core:44805] [ruby-trunk - Feature #1917] Curses::Window#keypad(true) fails for Curses::Key::ENTER ?

Issue #1917 has been updated by shyouhei (Shyouhei Urabe).

Tracker changed from Bug to Feature
Description updated
Category set to ext

Sorry for this quite late response...  I happened to realize that this is not 1.8.7 specific.
Moved to trunk, assigned to shugo.
----------------------------------------
Feature #1917: Curses::Window#keypad(true) fails for Curses::Key::ENTER ?
https://bugs.ruby-lang.org/issues/1917#change-26380

Author: robert (Robert Gleeson)
Status: Assigned
Priority: Normal
Assignee: shugo (Shugo Maeda)
Category: ext
Target version: 


=begin
 I am not too sure if this is a bug, my apologizes if it is not.
 After creating an instance of Curses::Window, setting keypad to true, it is possible to catch Curses::Key::UP/DOWN/LEFT/RIGHT, but when I try to catch Curses::Key::ENTER, it fails.
 On the pressing of enter, "10" char code is returned or "\n", but Curses::Key::ENTER is equal to "343".
 Here is an example case:
 
 require 'curses'
 
 Curses::init_screen
 w = Curses::Window.new 20,60,0,0
 w.box ?|, ?-
 w.keypad true
 chr = w.getch
 w.setpos 2,4
 w.addstr %q{Caught enter} if chr == Curses::Key::ENTER
 w.addstr %q{Caught "\n"} if chr.chr == "\n"
 w.refresh
 w.getch
 Curses::close_screen
 
 Again, apologizes if this is not a bug, I do not want to waste anyone's time, but it felt odd to me, that other keys, such as Curses::Key::UP/DOWN/LEFT/RIGHT could be caught but not ENTER.
=end



-- 
http://bugs.ruby-lang.org/