Author: adietish Date: 2011-01-21 16:51:37 -0500 (Fri, 21 Jan 2011) New Revision: 28492 Modified: trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/internal/deltacloud/ui/utils/WizardUtils.java Log: [JBIDE-8186] Modified: trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/internal/deltacloud/ui/utils/WizardUtils.java =================================================================== --- trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/internal/deltacloud/ui/utils/WizardUtils.java 2011-01-21 21:51:15 UTC (rev 28491) +++ trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/internal/deltacloud/ui/utils/WizardUtils.java 2011-01-21 21:51:37 UTC (rev 28492) @@ -74,12 +74,11 @@ * <p> * Furhtermore it updates the models and targets of the given data binding * context. This might be necessary if the given job will change widget - * enablements in the calling wizard page. The reason for this being needed - * is that the runner saves the widget enablement state when before it - * executes the given runnable. It the restores those states of all widgets - * in the calling page once he finished the given runnable. It may therefore - * restore incorrect states since the job changed those enablements while - * the runner was executing the job. + * enablements in the calling wizard page. The reason for is that the runner + * saves the widget enablement states when it's up to execute the runnable. + * It then restores those states once he finished executing the runnable. It + * may therefore restore incorrect states since the job changed the + * enablements when it was run. * * @param job * the job