Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Scrollable Popup Menu Keyboard Navigation Date: Sun, 10 Apr 2016 11:20:57 +0200 Lines: 25 Message-ID: References: <12b619c7-c6ba-4eb6-a064-e0b992b0c785@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net ajyAjJOOCyQ/ah00207zqwOgZ3/UlMKsVeWtYIlBxE68e109o= Cancel-Lock: sha1:saCAa7TcHkO9WHbW/JXgz6Dt11A= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:34102 On 08.04.2016 17:52, Eric Douglas wrote: > I'm asking why that popup menu can navigate by default using > up and down arrow keys I didn't write anything special for, but I > have to write key map code to manually tell it what to do if I want > page-up and page-down to work. I assume it is because there is no universal concept of "page scrolling". If you look closer scrolling page wise is a much more complex topic than scrolling individual items. For example, some applications will not show anything that has been shown before a "page down" while others will show some amount of the last content (e.g. to improve reading experience). Then, do you measure "page" in terms of fixed size units or fixed entries? With the former you might get half shown entries at the top if the window height is not an exact multiple of the item height while with the latter you always start at an item boundary. Regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/