Bug 169997 [CellEditors] TableViewer doesn't activate TextCellEditor consistently
A TextCellEditor is not activated consistently in a TableViewer if the cell clicked is not in the currently selected row. Running the sample application in a debugger, the bounds reported for the table item appears to be incorrect for the column when the row is not selected. This behaviour can be observed by setting a breakpoint at TableEditorImpl.java line 135 (the if statement doesn't return true unless the row is selected due to the bounds being incorrect): if (bounds.contains(event.x, event.y)) {
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ColumnViewer.java
}
		}
	}
	/**
	 * Checks if this viewer is currently busy, logging a warning and returning
	 * <code>true</code> if it is busy. A column viewer is busy when it is
	 * processing a refresh, add, remove, insert, replace, setItemCount,
	 * expandToLevel, update, setExpandedElements, or similar method that may
	 * make calls to client code. Column viewers are not designed to handle
	 * reentrant calls while they are busy. The method returns <code>true</code>
	 * if the viewer is busy. It is recommended that this method be used by
	 * subclasses to determine whether the viewer is busy to return early from
	 * state-changing methods.
	 * 
	 * <p>
	 * This method is not intended to be overridden by subclasses.
	 * </p>
	 * 
	 * @return <code>true</code> if the viewer is busy.
	 * 
	 * @since 3.4
	 */
	protected boolean checkBusy() {
		if (isBusy()) {
			if (logWhenBusy) {
				String message = "Ignored reentrant call while viewer is busy."; 
				if (!InternalPolicy.DEBUG_LOG_REENTRANT_VIEWER_CALLS) {
					
					logWhenBusy = false;
					message += " This is only logged once per viewer instance," +