Community

Hi,

Given the reported issues with 4.5 loosing text from files (Sophos or Unix file related I understand) I need to go back to an earlier version - 4.4. On the ftp site there are 2 English versions - 4.4.2 and 4.4.2a. Now I am assuming that 4.4.2a is the latest 4.4 release and the one I should use, but does anyone know for certain before I go ahead?

Thanks,

Martin

You must be referring to this thread:<br>
http://www.textpad.com/forum/read.php?f=1&i=1644&t=1635

Which antivirus are you using?

Roy

Sophos Anti-Virus 3.57

We have also experienced these problems when not running Sophos but editing Unix file types on PC using TextPad ... Others here are using 4.4.1 as a work around - I was looking at 4.4.2 as it should be newer ...

That said, given that it is 10 months since the original bug report, i'd have hoped for a fix by now ...

Martin

The bigest problem for textpad, I think, is the lack of support. It seems Helios doesn't care about this at all. I think, most of other sharewares/freewares in the earth are much better than textpad in this point.

John

Just a thought -- in V4.5:

1) Do these files use the same line terminators throughout?

2) Does the error occur with syntax highting turned off?

3) Does the error occur if document not associated with TextPad or with any of the document classes?

4) Are the files Unicode/UTF-8/DCBS either before or after the error happens?

The reason I ask is that when looking over the What's New for v4.5, I thought maybe this error was introduced by one of these fixes:

o Saving a Unicode or UTF-8 file as ANSI saved it as OEM/DOS.

o When saving to certain non-Windows network drives, "Another application has updated the file" was erroneously reported.

o The Save As command did not preserve original line endings for files with mixed ones.

o The last line of a file is no longer automatically terminated, for files with non-standard end of line characters.

Hi Roy,

> 1) Do these files use the same line terminators throughout?

Yes - I think so, though it may have been open in DOS, save as UNIX.

> 2) Does the error occur with syntax highting turned off?

The file had no extension so there was no syntax highlighting.

> 3) Does the error occur if document not associated with TextPad
> or with any of the document classes?

Again, no file extension so no association.

> 4) Are the files Unicode/UTF-8/DCBS either before or after the error happens?

Could be - not sure, just a plain text file.

All that said, I have been in touch with Stephen MacDonald from Helios and apparently the latest 4.5.0 from the web site fixed the bug. I have downloaded that version and been unable to reproduce the error (not that I ever saw it in the first place - a colleague did and advised me against 4.5) so I think all is well.

Thanks for the help,

Martin