Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338448 - Control.setTouchEventsEnabled(boolean)/isTouchEnabled() not consistent
Summary: Control.setTouchEventsEnabled(boolean)/isTouchEnabled() not consistent
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.7 M6   Edit
Assignee: Silenio Quarti CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-28 13:55 EST by Silenio Quarti CLA
Modified: 2011-03-11 11:01 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Silenio Quarti CLA 2011-02-28 13:55:13 EST 
In the new API in Control.java to enabled touch events, the setter name is not consistent with the getter (TouchEvents instead of Touch). Also, traditionally if an API starts with is* in Control.java, it means that the state of the widget parent is checked. This is not the case for this API, so it should be getTouchEnabled() instead of isTouchEnabled().
Comment 1 Silenio Quarti CLA 2011-02-28 14:47:58 EST 
Fixed > 20110228.

We renamed:

Control.isTouchEnabled()  to  Control.getTouchEnabled().
Control.setTouchEventsEnabled() to Control.setTouchEnabled().
Display.isTouchEnabled()  to  Display.getTouchEnabled().