Issue
The spell checker keeps finding numbers, example 12.25, when checking a document. This wasn't the case in PowerCADD v6
Affects
PowerCADD v7.00, v7.0.1
Description
When spell checking a document in PowerCADD v7, numbers such as 12.25 are always checked. In PowerCADD v6 those types of numbers were ignored which made more sense.
To See the Condition
In PowerCADD v6, do this:
- Create a New Untitled document
- type one piece of text, example 12.25
- deselect the text block
- choose Text menu > Spelling...
- the spell check completes without finding 12.25 as a spelling error
- This is correct behavior
In PowerCADD v7, do this:
- Create a New Untitled document
- type one piece of text, example 12.25
- deselect the text block
- choose Text menu > Spelling...
- the spell check considers the text 12.25 a spelling error
- This is incorrect behavior
Work Arounds
Unfortunately, there isn't an elegant work around. Choosing Ignore All in the spell checker dialog only ignores that specific number instance for that pass of the spell checker. Choosing Add, to add the number to the dictionary, is time consuming and is required for every possible number combination that might be in a technical drawing and isn't a practical long term solution.
The issue has been reported to Engineered Software for action.
We hope that helps
caddpower.com
------
If you found this article or the website in general to be helpful, educational or a time and money saver you can show your support. Thank you ~ Brian (huc) Huculak
Comments
FIXED in PowerCADD 7.0.3
This condition is fixed with PowerCADD 7.0.3 which is a free update from Engineered Software
in the United States or your local PowerCADD Distributor for International Users 
correction
it's still busted in 7.03 but it may be due to a recent Mac OS? X update
I may have also added a bunch of numbers to my dictionary to fix the problem with some specific drawings
sorry for the confusion -- we've fired off another note to EngSW for both the shipping version to be fixed and to address the issue in the current beta version.
problem still exists in 7.02
our current testing indicated the update to PowerCADD 7.02 does not fix this issue
if we have any additional information we'll post a comment
if you have any additional insights or information please feel free to post a comment here.
We received confirmation
We received confirmation today from Engineered Software that this item is confirmed and on their to do list.