TextPad 5: DoubleClick does not open file

[aridolan]

When I double-click a .txt file (or any other file associated with TextPad), TextPad is opened without the file. The area where the text should be displayed is gray, and the cursor is an arrow cursor. DoubleClicking inside this gray area open an open file dialog.

The same file is opened properly from the Open With menu, but not by DoubleClicking.

All this refers to TextPad 5.

Any help?

Thanks,
Ariel

[Technocrat]

Ok I FINALLY FIXED this just now so I figured I would pass this along.

After reading every post on here and trying a lot of different things this is the only one that works 100% of the time.

What I am about to tell you is dangerous, so be careful and make a backup!!

Let's take .txt as an example of one you want to fix.

Open regedit

Got to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
Find the .txt key folder and delete it

Open TextPad
Go to Configure->Preferences->Associated Files

If you have an entry in there for the file type you want to associate delete it. In this case .txt. If you don't then do not worry about it.

Then put .txt in the new extension and Text in the description. Then click add. Now click apply and OK.

It should be working now, you should be able to open .txt files. You can now repeat these steps for any other type.

NOTE: From time to time TextPad might crash on you adding associations. If it does you need to search for every key folder with the name .xxx (ie .txt) and delete it. Then attempt to reassociate it.

[aridolan]

Thanks for the detailed reply.

Before I go into this complex and risky procedure (I have many extensions associated with TextPad), I would like to ask another question:

The problem began after upgrading to TextPad 5. There was no problem with TextPad 4.7. I noticed that a TextPad 4 folder still appears in my registry (although it does not appear in "Add or Remove Programs"). In my registry, under HKEY_CURRENT_USER\Software\Helios there are two folders: TextPad 4 and TextPad 5.

My questions:
Should I delete the TextPad 4 folder from the registry?
Should I have uninstalled version 4 first, before installing version 5, and if so, is this the cause of my problem?

Thanks,
Ariel

[Technocrat]

I had numerous problems after upgrading. What I did was uninstall 5, and made sure 4 was gone. Then searched the registery for textpad and deleted every key for it. Then reinstalled 5. That took care of everything except the open problem.

[aridolan]

Thanks, I shall do that.

[Technocrat]

Lovely now all of a sudden none of my document classes are working and all the pulldown menus have invalid characters everywhere like its having a character coding problem.

Sorry Helios but Textpad 5.0 is really bad. Maybe you should have done some beta testing first.

I am going back to 4!

[duckworth]

From time to time TextPad might crash on you adding associations. If it does you need to search for every key folder with the name .xxx (ie .txt) and delete it. Then attempt to reassociate it.

Can you elaborate on this part a bit, as I seem to be having this issue now

There was only one key folder named .txt? Where else should I be searching?

[capsalad]

After upgrading to TextPad 5.0, I invariably get a "TextPad.exe - Entry Point Not Found" error dialog on startup. The dialog text reads "The procedure entry point IsThreadDesktopComposited could not be located in the dynamic link library USER32.dll."

I appear to have identical copies of this DLL (577K, 2005-03-02) in C:\WINDOWS\system32 and C:\WINDOWS\system32\dllcache, inter alia. For what it's worth, after the error dialog is dismissed, TextPad opens the selected document in the normal way.

My platform is WinXP SP2. Any ideas?

[Technocrat]

Honestly all I can suggest is go back to 4.7.3 until they fix all the problems. 5 is just too buggy. It crashed on me so many times that I just gave up.

Being a programmer I know how hard it can be to develop and release a product. You can't foresee every problem. I am sorry but this is just embarrassing. Made worse by the fact that at least to me Helios hasn't address this problem, or really any of the problems being reported. He really needs to step up and do something, or at least say something about the problems. Silence isn't a good away to keep customers.