Re: PSPad unicode 4.5.4 (2349) English

jan.sedivy:

Hi Jan,
It's really great work you did. I had started using it recently and I am fighting some old habits...
Would it be possible to modify the selectionMode function to return the current mode, if called with no parameter ?
It allow me (and other users ) to build a simple toggleSelMode script executed by a singe HotKey.
And second, the Search and Replace dialogs remember the Direction last selected by the user, but its lost, when the replace dialog is called with block of text selected.
As there is no difference in block replace with Direction Forward and Entire Scope, would it be possible to preserve the Direction option when called on selected text ?

Thanx,
Jan

PSPad will return 'N' for normal mode, 'C' for column, 'L' for line mode if you call function without parameters

kiendlm:

I accidentally found a little issue in pspad regarding the file encoding (I'm using build 2349 on Windows XP SP3):

* Create a new file of any type
* Go to the Format menu and select "UTF-16 LE" to convert it to unicode
* now open any ANSI file, e.g. the pspad.ini or create a new file using the "File/New" menu item in order to use an existing template.

PSPad will treat the lastly opened or newly created ANSI file as if it was a utf-16 encoded file and only show a pile of asian characters (funny, but a little bit difficult to read when you in fact want to work on a C++ source file... ). The only way to get it back to normal behaviour is to select "ANSI" in the Format menu and to reopen the second file. Now this is really not a big problem since pspad does not crash and can be easily reset to normal behaviour, but I would consider it more intuitive if PSPad always defaults to ANSI encoding when it can't figure out the real encoding of a file being opened or when creating a new one instead of using the last encoding selected in the Format menu, which seems to be the current behaviour. It would be fine if you could think of changing this with the next build.

P.S.: Thanks for this great piece of software which I and my colleagues use daily, Jan, and keep up the good work!

If you switch to UTF-16 encoding in Format menu, PSPad will create new files with this encoding. But PSpad will not open existing ANSI files as UTF-16.

clanman:

There is a minor VBScript key word recognition issue.

When splitting a line across two lines and you put a space then underscore ( _) after the last key word then all works fine.

However, if you are doing something like anIfclause and the condition has multipleor, and, not(and so on) junctions and there is no space left between the underscore and the junction, PSPad does not recognise the key word.

This example works
If strCode = "A" or _
strCode = "B" Then
bolDeleteFile = false
End If

This code is still valid however theoris not recognised as a key word
If strCode = "A" or_
strCode = "B" Then
bolDeleteFile = false
End If

Fix will be available in the next build