PSPad unicode 5.5.3 (855) English

Download links, 32b version is suggested:
pspad.poradna.net
sourceforge.net
PSPad 64 bit version is EXPERIMENTAL. It doesn't contains scripting. In case of any problem use 32bb version.
pspad.poradna.net

SHA1 hash: d9782cb1c4584b0711918b407f54ebf42b0a15b9 pspad553b855.zip 9746e7956c702b029a59104a1c01327dccd3c7fd pspad553b855x64.zip

This archive contains modified files only. The correct way how to get full functionality:
1. Download and install latest full version first!
2. Replace existing files with content of archive

Changes to 5.5.2 (852)

News:
INNO Setup highlighter - added missing words
Stability changes
Speed up file opening - removing redundant I/O operations
Speed up PSPad start - localization optimalization

Removed:
Sending statistics using MATOMO to PSPad server

Fixes:
External program execution in case when LOG file was fill in
Program settings / KeyMap - overlapping section list with shortcuts
Minimize to Tray icon
Load project - file tabs
64b version - fixing dialog exceptions
Other fixes reported by users

Hi, build 855 (and 843 and 845) does not automaticly switch to the correct tab on compile-error, build 833 did work correct.

I use PSPad to compile my project by calling an external compiler (batch). Normally (build 833), when an error is found, PSPad would log the error in the Log window and switch to the tab (file) where the error is (with a red line on error-line).
Build 855 shows the error in the Log window but:

- when the tab (file) with the error is already active, PSPad correctly goes to the line with the error. This is correct.

- when the tab (file) with the error is not active (another tab is active), PSPad's tab-overview (above the editor) correctly switches to the tab with the error, but the editor-content stays open in the current active tab. So the tab-overview/index does not match the correct editor. This problem alse happens when double-clicking on the error in the Log window.

For now I have to go back to build 833.

If you can few minutes, I will publish build 857, which should fix it

Thanks! Works correct again in build 857.