| Summary: | [Control] addMouseMoveListener is missing | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Beirti O'Nunain <beirti.x.onunain> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | rsternberg |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Beirti O'Nunain
Due to client-server nature of RAP we could not implement mouseMove listener properly without sending too many requests and make the performance worse. With every request from the client we sent the current cursor position (Display#getCursorLocation()). Depends on your use case, you could try to use Display#getCursorLocation() instead. (In reply to comment #0) > Also, sorry for clogging up bugzilla with this question. Is there a mailing > list that would be better served for such queries? Entering an enhancement request for missing features is generally fine. If you're unsure if something is actually a bug or if you're looking for a workaround, the RAP forum is the place to discuss those questions: http://www.eclipse.org/forums/eclipse.technology.rap . *** This bug has been marked as a duplicate of bug 331287 *** |