ANSI characters are not functioning in TP 7.4 - Please help

General questions about using TextPad

Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard

Post Reply
User avatar
ineuw
Posts: 191
Joined: Sun Mar 18, 2007 3:23 pm

ANSI characters are not functioning in TP 7.4 - Please help

Post by ineuw »

ANSI characters are not functioning in TP 7.4 - Please help

Using TP 7.40, when editing today, I couldn't create extended ANSI characters for example: using the Alt+0151 on the Numpad which is the emdash — character, which always worked before. I tested this in Notepad and it works fine - just as it does in this post

Next, I got a message that my custom.bnd file is missing. So, I uninstalled everything and erased all traces of TP from Program Files and the Roaming Appdata completely, and reinstalled everything anew.

With the TP defaults untouched, the Alt+Numkey combinations worked immediately. Then, One by one, I recreated my preferences, which includes the following:

Changed folder paths to my data drive where I store the macros, syn, tcl, and custom spell files
Assigned keyboard shortcuts to the macros I use
Created 2 custom file extensions, both based on .txt but with different tab, background colors
Changed keystroke preference to Microsoft applications

And again, I lost the ability to type in ANSI or ASCII characters using the alt key and the numpad. I tried combinations of encoding, - always creating a new document to be sure that it's with the selected encoding, but this didn't make a difference. Document encoding combinations tried were: ANSI + PC, ANSI + UNIX, UTF-8 + PC, and UTF-8 + UNIX. Can anyone tell me what went wrong?
TextPad 8.16.0 64bit in English and TextPad 9.1.0 64bit in French, on two separate Windows installations
User avatar
ineuw
Posts: 191
Joined: Sun Mar 18, 2007 3:23 pm

Post by ineuw »

I use the Microsoft style key definitions and it seems that the custom.bnd gets corrupted after awhile. This "awhile" occurs after I assign the keyboard for my macros, but, I am not sure. Any guidance to track down the problem is much appreciated.
TextPad 8.16.0 64bit in English and TextPad 9.1.0 64bit in French, on two separate Windows installations
User avatar
ineuw
Posts: 191
Joined: Sun Mar 18, 2007 3:23 pm

Post by ineuw »

The problem is resolved. A cautionary tale of keyboard key assignments. It was caused by assigning macro keys to the Numpad 1,2,3,4.

My apologies for the unnecessary post.
TextPad 8.16.0 64bit in English and TextPad 9.1.0 64bit in French, on two separate Windows installations
Post Reply