AmigoJack wrote:The problem is: who still has such an installation to be able to reproduce your issue? Even the developers might be unable to have those anymore, let alone would release a new version of such an old branch. I know this dilemma from both perspectives: user and developer.
I was hoping that it might be a known issue.
AmigoJack wrote:While that is surely true I would miss Unicode support nowadays a lot, and I don't got that with any version older than 8, let alone its regular expression support.
I don't really have a need for Unicode support. I only ever really edit plain text files in English.
AmigoJack wrote:If it's the computer in whole you would have experienced issues elsewhere, too. However, running a RAM checker wouldn't be in vain.
It seems that the problem with the macros is confined to the copy, cut and paste operations. I just tried in vain for about 20 minutes to create a macro that copied a line, and then used paste to create a series of commands for a batch file and sometimes the paste would work and insert the contents of the buffer and sometimes it wouldn't. There was no pattern to when it would work and when it wouldn't. I had about 25 lines that I needed to do this to and it might work on the first three, then skip five, work on one, skip four, work on two, etc. Just random.
I didn't want to reboot right now, so I decided to make a macro without using copy and paste. I manually copied the whole list and pasted in two additional copies, then I sorted the list so that all three copies of each line were grouped together. Then I created a macro that simply used the existing copies and inserted the required commands around them. That worked perfectly. Unfortunately, that's not a solution because I had to do the copy and paste manually to ensure that it worked properly, which kind of negates the convenience of using macros.
That's another thing, cut copy and paste always work properly outside of macros. They always work fine when recording a macro. It's only when they're executed as part of a macro that they fail.
Even a test macro that does something as simple as copying a line and then pasting a second copy of it, didn't work reliably.
As you say, I'm not experiencing any other issues with it, or with the computer in general, it's only the macro execution in TextPad that's affected.
In desperation, I tried a couple other programs including Notepad++, but found their macro capabilities to be sorely lacking. In particular, Notepad++ doesn't have conditional execution of the macro. You can record search as part of the macro, but whatever comes after the search will execute regardless of whether the search found anything or not. If you run the macro to the end of the file and the last occurrence of the search term is on the second line, it will just continue blindly making changes to the rest of the file. When I pointed this out, one of the contributors vigorously defended this and said that's how it should work, even though it makes the inclusion of the search function useless inside macros.
That doesn't seem to be what's happening here. I can open TextPad from scratch, create a macro and it may or may not function correctly.
AmigoJack wrote:You have to choose between letting the system run for days being an issue or not. If yes, then it is predictable.
But even that isn't predictable. A while back, my system had been on for days and the macros all worked fine. Tonight I tried to create a macro from scratch and it failed. BTW, once this starts happening, all the macros using cut & paste become unreliable until I reboot. It's not as if some work and some don't.
AmigoJack wrote:This sounds like you didn't try out yourself that many options. Does it affect all macros or have you experienced it only on specific ones? Why not moving all your macro files except the first to another folder, so TextPad only has one macro left? Then try it with a "complex situation". And so on.
I just tried that and the results were inconclusive. I left a semi-complex macro, moved all the others and then tried using that Macro about ten times in a row. It worked about 90% of the time, but it did fail once.
And now I have to rebuild my macros menu since it moved them all to the inactive menu, placing them in alphabetical order, which is a problem since TextPad assigns hotkeys to menu items, not specific macros. Meaning that all the hotkeys are now assigned to the wrong macros. ARGH!