I assumed that the OLE problems I've had with TM and SEE (Softmaker's Equation Editor) "in the past"* were due to peculiarities with SEE or TM's handling of SEE, not with OLE objects in general. I was therefore taken unawares when RFFlow documents inserted into TM documents as OLE objects turned out to have subtle defects.
Aside: RFFlow is flowcharting'ish quasi-CAD program whose unique features, very low price, liberal license, extensive OFFLINE help (like SMO used to have, hint), and all but obsequious customer service have allowed it to survive the decades (three or four) -- albeit little changed. Everyone should buy a license just to support a good cause, though most might regret the decision.
Back to the subject at hand.
The problems I've encountered/discovered so far are that TM initially doesn't load the correct Greek characters embedded in RFFlow OLE documents or doesn't load any characters for Greek characters. Clicking upon an RFFlow object and then exiting the RFFlow window that appears will result in the correct characters being shown in TM even if no manual changes were made to the RFFlow object. The resulting TM prints also don't match what was shown during editing, whether or not what was shown was correct. These issues are documented in the attached PDF, though the fact that the issues are inconsistent -- similar problems consistently occur, but not identically -- may have introduced minor errors.
Of course, TM may also be making other incorrect or failed character substitutions that I have yet to notice.
I have also had issues where there were artifacts around text (e.g., characters or text enclosed in a faint box that wasn't in the original RFFlow drawing), but I have no documentation to support these recollections.
Thoughts?
Cordially,
Richard
Windows 7 Pro, the last non-garbage version of Windows
* While it is my impression that most of SEE's issues are"in the past," i.e. do not occur in new documents, I recently received the formerly familiar can't-find/launch-SEE error while trying to edit an SEE object in an elderly document; if fixes were found and implemented, apparently they don't carry backwards. Or am I mistaken?
