Bug #3085
Mis à jour par Serge Heiden il y a plus de 4 ans
All commands for which the result is susceptible to be waited for some time, must provide a work progression feedback.
Some work progression feedback widgets are already implemented, but generally in views that are not visible by default.
The result is that there is still no work progression feedback, which can bring about a bad UX for users using low ressourced computers.
h3. Solution
At TXM start-up (in ApplicationWorkbenchAdvisor.initializeUI()), force the Eclipse Preferences "General > Run in background" (IPreferenceConstants.RUN_IN_BACKGROUND) to false.
Thus all TXM jobs will prompt the progress dialog
Some work progression feedback widgets are already implemented, but generally in views that are not visible by default.
The result is that there is still no work progression feedback, which can bring about a bad UX for users using low ressourced computers.
h3. Solution
At TXM start-up (in ApplicationWorkbenchAdvisor.initializeUI()), force the Eclipse Preferences "General > Run in background" (IPreferenceConstants.RUN_IN_BACKGROUND) to false.
Thus all TXM jobs will prompt the progress dialog