| Summary: | [API] The MouseWheel Events are missing | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Markus Wolf <markus> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 1.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Wolf
(In reply to comment #0) > The MouseWheel Events API is missing. > It would be great to add support for this (unlike MouseMove this does not > generate that much events). It still does generate a very high amount of requests. I doubt that it is practical to implement mouse wheel events. > We would need this to suppress the MouseWheel usage on Combo Widgets which are > not expanded, since our users are confused by the default SWT/RWT behaviour. There is a misproportion between the gain of user experience and the high effort of implementing mouse wheel events. Mousewheel events is one of the few things that we still consider unfeasible in RAP. Your idea of suppressing mousewheel events would require server-side turnarounds for scrolling in widgets which would make scrolling very sluggish. If you think the current behavior on unexpanded Combo boxes is a usability issue, please open a separate bug for it. |