The Help tab in the right column explains the rule and the quick fix to be applied.
在右列中的Help选项卡解释了应用的规则和快速修复方案。
Update each classpath value with a prefix, such as /opt/IBM/db2v8.2/SQLLIB/, and use the quick fix for each error.
用一个前缀更改这样的classpath值，例如/opt/IBM/db2v8.2/SQLLIB/，并为每一个错误使用快速修复 。
The left half of that panel shows the code if the quick fix were applied and the right half shows the original code without applying the fix.
如果应用快速修复方案，面板左半边就显示代码，右半边就显示未应用修复方案的原始代码。
Then why are so many people taking the quick fix more and more? Reflecting back on it now, I see there are many factors that have come into play.
那为什么那么多人解决起问题来越来越贪求权宜之计呢？现在回想一下，我明白这是很多因素造成的。
The quick fix might change the file directly or it might present the steps necessary to fix it.
快速修复方案也许会直接改变文件，或者它会显示完成修改所需的步骤。
The Quick Fix pane now offers variation previews for every adjustment option.
快速修复窗格现在提供每个选项的变化调整预览。
The project template for code refactoring doesn't include a usable demo, but the same techniques shown in the Quick Fix walkthrough can be used here.
为代码重构所提供的项目模板中并没有包含可用的演示程序，但是在此我们可以使用快速修正教程中所展示的相同技术。
The support for Code Refactoring looks a lot like the "quick fix" support correction for Code Issues, but it is applied at the text level.
对代码重构的支持看起来和修正代码问题的“快速修正”功能很类似，但是它应用于文本级别。
The support for Code Refactoring looks a lot like the "quick fix" support correction for Code Issues, but it is applied at the text level.
对代码重构的支持看起来和修正代码问题的“快速修正”功能很类似，但是它应用于文本级别。
应用推荐