Community

kengrubb wrote:What is the name of your Workspace?

Ken, thanks for following up. The issues I have appear to be independent of the workspace filename, as it's occurred with at least the following names:

When you close a file, the presumption is that you wanted to remove that file from the Workspace, so you are not prompted to update the Workspace. Sorry, but that's not my experience with TextPad 7.0.9. Closing a single file (or multiple files), does not automatically remove the file(s) from the ...

kengrubb wrote:Your question has been addressed in the first thread. Starting a second thread asking the same question doesn't really accomplish anything.

This is filed under 'Enhancement Suggestions', which is different than the bug I filed under 'General'.

Performing [File] > [Close] on every file does not remove the closed files from the workspace. Highlighting all the files in the Document Selector and right-clicking and selecting [Close Document(s)], does not remove the closed files from the workspace. But selecting [File] > [Close All] silently ...

Note that performing File > Close on every file does not remove the closed files from the workspace. Also note that highlighting all the files in the Document Selector and right-clicking and selecting [Close Document(s)], does not remove the closed files from the workspace. What *DOES* silently ...

I've updated to support TextPad 6.1

Details are at http://smithii.com/textpad_installer

Check it out!

I finally got around to updating my TextPad Installer to use 5.42 and selectively install all the add-ons.

Details are at http://smithii.com/textpad_installer

FYI, http://www.siteadvisor.com/sites/smithii.com rates my site as safe.

For the last 2 weeks or so, TextPad 4.73 on Windows XP SP2 + all hotfixes, has started to randomly lock up after I do a File / Save. One of the edited files that is saved, will having nothing but NUL bytes in it. As a result, I have to rename the .bak file, which is fine, and rename it to the ...

IMHO, the functionality you are describing is counter intuitive. If the workspace "auto-saves" then why does TExtPad imply they aren't auto-saved by asking "do you want to save changes to the workspace?" I would strongly suggest that TextPad ask you before blindly removing files from a workspace. Or ...

I do the following: 1. File/Workspace/Save 2. File/CloseAll 3. File/Workspace/Open the workspace saved in 1. above The workspace is empty. This makes no sense at all. How is it possible that the above sequence of commands could possibly *empty* the workspace of all it's files? IMHO, it's shouldn't ...

Using Wine, I have never been able to install any version of TextPad. The installer would fail with mysterious errors. Someone does claim to have installed 4.7.2, though: http://appdb.winehq.org/appview.php?appId=85&versionId=650 I would strongly suggest you first get TextPad working under Wine ...

I don't think we need another configuration option.

I would just like to see TextPad save the file automatically by the next available file name.

How about Document1, Document2, etc.

If the name is already used, it just tried the next one.

When I have timed backups turned on, and I create a new document, and before I've saved it to a file, TextPad annoys me by stealing the focus to insist I name the new document.

I would suggest it either save the document internally under a temporary name, or not try to autosave new documents.