CompuServe Messages

"why can't more than one TPM read from the translators?" The Symantec C++ and THINK C translators are both marked as "memory resident". This makes compiles faster, since they don't need to be read from disk every time you compile a file. However, due to the way that the TPM works, this also means that they have resource forks that must stay open. At this point, the open resource forks can't be shared. "is it really necessary to disable the entire Search menu, and disallow opening all project files with a double-click? How about dimming just the menu items that depend on the already-opened translator." All file operations (including Search) depend on the translator for the project's files being loaded. The TPM can't tell that a given file is a text file unless it's sucessfully mapped to a translator that it can find when it loads up. If it can't find the translator, it can't tell the difference between a text and binary file in the project. "I can also duplicate a translator and put the duplicated files in a new folder. That'll work, except on my PB 140. It has 450K free, but not 750K." Try making a copy of the TPM and the "none" translator. Rename none to be "THINK C" or "Symantec C++". This should let you browse the source files in the project, and won't take up that much disk space. You can also try turning off the memory resident switch for the translators. Open them up with ResEdit and modify the INFO resource using the template. This will let you put your two TPMs in one folder, but it will slow down compiles. We are looking into supporting multiple open projects in a future release. It is not a simple modification, however. -phil