Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338448

Summary:	Control.setTouchEventsEnabled(boolean)/isTouchEnabled() not consistent
Product:	[Eclipse Project] Platform	Reporter:	Silenio Quarti <Silenio_Quarti>
Component:	SWT	Assignee:	Silenio Quarti <Silenio_Quarti>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.7
Target Milestone:	3.7 M6
Hardware:	All
OS:	All
Whiteboard:

Description Silenio Quarti

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

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().