Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#153 closed bug (wontfix)

Can't scroll the main area of MUI (with the keyboard)

Reported by: Samir Hawamdeh Owned by:
Priority: normal Milestone: 4.0-2015R1
Component: Settingsgroup.mui Version: 4.0-2014R5
Severity: minor Keywords:
Cc: OS Platform: AmigaOS4
Blocked By: Blocking:
Release Notes:

Description

Summary

In case the main area containing the content (the main column at the right) exceeds the available space a scrollbar appear, that's fine.

However actually on that area we can't use the keyboard to scroll, because even if you you have selected the main area the focus still into the column on the left, so in case you try to use the keyboard (for example the arrows to scroll up/down) the page will be changed instead

An example: if you are into the "Keyboard" section and you press the arrow-down key nothing happen (because Keyboard is the last option in the list) while conversely if you press the arrow-up, MUI will select the "Help" area above

Of course it's correct to be able to scroll the various MUI option with the keyboard, however if the main area is selected and a scrollbar still there would be nice to have the possibility to scroll just this selected area instead

Attachments (1)

no_scroll.png (114.1 KB) - added by Samir Hawamdeh 5 years ago.

Download all attachments as: .zip

Change History (3)

Changed 5 years ago by Samir Hawamdeh

Attachment: no_scroll.png added

comment:1 Changed 5 years ago by Thore Böckelmann

Component: undefinedSettingsgroup.mui
Milestone: MUI 4.0-2015R1
Priority: undecidednormal
Resolution: wontfix
Status: newclosed

Scrolling as you expect is not going to work. The reason is that the page list on the left side is the active object by default and hence will "eat" all vertical keyboard movements.

The virtual group on the right side which contain the current page content never becomes the active object and hence cannot react on the key presses if any other object sees the key presses first and is allowed to react on them.

However, what is possible is to skip setting the page list as the window's default object. This is something different than the active object. But even then it is still necessary to deactivate the window's active object (i.e. by pressing CTRL+Tab). Then the virtual group will be the object to handle the key presses first.

In general this is not a very obvious approach and hardly anybody will do the necessary actions just to be able to scroll the virtual group by keyboard.

To sum it up: although it would be possible in this single and very specific case I doubt it is worth the effort, because the automatism you desire requires additional work by yourself. The change I did was ok for the Aboutwindow class, but you cannot expect every virtual group to react accordingly if the application does not explicitly support this behaviour.

comment:2 Changed 5 years ago by Thore Böckelmann

Milestone: MUI 4.0-2015R14.0-2015R1

Milestone renamed

Note: See TracTickets for help on using tickets.