Community

In the meantime i figured out that nobody can help unless there will be a small enhancement. So if you are interested in this topic see http://textpad.com/forum/viewtopic.php?t=4998 and join.
HHRü
P.S. ... it should be locking, not kocking

To 'insist' in my OP: Compile this, use TP's configuration menu to bind it as a tool and let it work with any txt- and bin files opened. You soon will agree, than bin-file-kocking is more than annoying. HHRü #include<stdio.h> #include<stdlib.h> int main(int argc, char *argv[]) { FILE *fp; long i,j,...

TP makes a difference in locking txt- and hex-files against write access. A permanent write-protection on hex-files is obsolet. There should be at least a switch "disable hex-file write-protection" or a rearangement of the "keep files locked.." - option into "keep background...

The reload function only affects ascii files. Files opened in hex-mode are obviously write protected. This is an unnecessary restriction. People who use TextPad (rather than wordpad) know what they are doing.
HHR

I'd like to see this feature too. To get a quick workaround I made a small tool to inject characters to a special position in the 'background" instance of the file I want to hex-edit. Now I found that this is not possible. I have to close the file first. May be I use a wrong set of options but ...

I've made a little prog to handle the misfit that in hex-mode opend files cannot be manipulated. The prog is designed to reside in the toolbox, to insert a string to a specific hex adress. If I try to write to a opend/focused file with this prog, i always get an i/o error. It seems to me that the op...