So What's New In This Release?
OK, I can hear you thinking I bet it's not going to be worth the time to get this new version
Probably true. However, on the off chance that you might actually like it when you get there, take a look below at the summary of changes from 0.07.002 and 1.00 to this new release.
Mostly, the changes are bug fixes; however the 32-Bit Edition has added the free-floating Control Station window, which you'll probably find useful if you edit large numbers of files simultaneously.
Changes in Version 1.01
- [PFE32] Fixed bug appearing in Windows 95 and Windows 98 where closing the Control Station by clicking on the "Close" system menu box would leave the window visible but inaccessible
- Fixed bug causing a GPF if a macro library containing bound macros could not be opened when PFE was started
Changes in Version 1.00
- [PFE32] Added the new Control Station facility, controlled by the "Control Station" item on the Options menu, that provides a floating remote control window, making managing large numbers of files and windows, and large MRU lists, much easier
- [PFE32] The Options Preferences "Associations" panel now rejects attempts to associate the ".lnk", ".bat" and ".exe" extension with PFE, as this would break the system's handling of shortcuts and programs
- Fixed bug causing the load progress indicator to draw incorrectly when loading files in excess of about 40 megabytes
- Fixed bug causing command substitutions %f, %n and %e to fail for files opened from the root directory of a drive or share
- Fixed bug causing files specified by UNCName not to be correctly identified as network files, and to suffer problems in checks for changes
- Fixed bug causing PFE erroneously to believe that network files have been altered by some other application when saving back to them
- The line number field in the status bar has been widened to cater for files with more than 1 million lines
- PFE no longer generates explicit beep sounds in message boxes; selection of sound on message classes is now left to the user via the Windows control panel
- The WindowIconizeAll and WindowRestoreAll commands now work correctly from within macros
- [PFE32] Fixed bug causing PFE32 to crash when editing a large file if it's changed by another application and PFE is told to reload it; the bug will also have caused some crashes editing smaller files after they have been reloaded
- The "*" change indicator in the caption of file windows is now removed if a file is edited, changed on disk by some other application, and then reloaded
- [PFE16] Fixed bug causing the toolbar undo button not to be lit as it should when switching between files
- PFE now checks the read-only attribute of disk files as well as the last-written time and size when determining if another application has changed them. The Options Preferences "File Change Checks" panel can be used to disable this if required
- Added a Window Previous command, mapped to Ctrl+Shift+F6 by default, that moves between windows in the opposite order to the Window Next command
- The Options Preferences "Window Control" panel can now specify that the Window Next and Window Previous commands should activate any iconic window that is next in the list, instead of operating only on non-iconic windows
- [PFE32] Fixed bug that caused the caret to disappear from an edit window and keys to be ignored when the IntelliMouse 2.2 driver was used in Universal Scrolling mode
- Fixed bug causing print dialog settings to be ignored when using PFE with the "/p" option for auto-printing
- Fixed incorrect alphabetical ordering of functions in the Options Key Mapping dialog
- Fixed bug causing PFE to hang in Edit Repeat Last Find or Edit Repeat Last Replace commands in some circumstances
- Fixed bug causing the printer font to be altered in the File Page Setup dialog even if Cancel is pressed in the selection dialog
- Fixed bug that allowed the Macro Play Recording command to be recorded directly into the active keyboard recording, causing subsequent inconsistencies
- Fixed bug causing the stack of replace strings stored in the Replace dialog to become corrupt when an empty replace string was specified
Impressive, or what? Hmmm, that's what I thought you'd say....
Return to the PFE Home Page