Community

Thank you for the timely fix!

Glad to see that a fix is coming soon (real soon, hopefully).

This has been annoying me for days and I didn't have time to prepare to post about it until now. Thanks for the timely report, @richardb!

kevinHealy, for some reason I didn't get a notice of your reply.

Anyway, it seems that these issues may have been silently fixed in version 9.1.0. I don't see them enough now to get irritated.

Thank you; I was not aware of that workaround. But note that we use alt codes to input other things besides accented characters. EG ¼, £, ⟺, etc. I've just come across a handy tool for inputting accented characters which I'll pass on. It's part of Microsoft's PowerToys collection which you can in ...

Thank you for pledging to fix this.

I use multiple workspaces and the feature was great in TextPad 8. But now several problems have cropped up in TextPad 9 and TextPad 9.0.1 Workspace menu shortcut loads the wrong workspace. Set-up/use several multifile workspaces. Start a new TextPad instance. Try to open the most recent workspace ...

IMO we should be pushing for a fix, and not needing to resort to workarounds. Yes, exactly! Especially since cut-and-pasting every single letter or character is an insane way to work. The alt-x sequence apparently only functions in Microsoft Office/365 -- which we don't use -- and I guess TextPad ...

I occasionally need to use windows alt codes and this worked in TextPad 8 and earlier. For example if I hold down Alt and type 0233 on the number pad, it inserts "é". (This works in all windows programs that support Unicode except TextPad 9.) In the latest TextPad, a box "" appears instead. Pasting ...

I want highlighting (color) but no box. I'm glad that that is once again possible, but the FB/BG stuff is counter-intuitive and non-standard -- hence the "misunderstanding". (Which is really a design/documentation/help error.) But at least this thread is here now, so other people will have an easier ...

No it did not fix the problem. The release notes said: "When the foreground and background colors were the same, the current line should not have been highlighted with a box." I updated TextPad and the problem was still there. Setting *BOTH* foreground and background to the highlight color worked ...

Yes, please prioritize removing the dashed outline. It's seriously cramping my work flow; very annoying.

And thanks, ak47wong. That workaround does help.

Got fresh text and verified the macro works from the menu.

Purging TextPad from memory and restarting it was the cure.

Okay, I shutdown and restarted TextPad and now the macro does appear to work, BUT I won't get some more of the critical text, to test, for a few more hours. Alas, I made two troubleshooting mistakes: I assumed that because TextPad normally seems stable for weeks at a time, that the memory instance ...

Yes and yes.

Also, from the macro editor, making a selection was not necessary when the macro was set to either "end of file" or "document", despite the parameter in the code.

The script always runs fine from the macro editor but not the menu.

I recorded a simple macro but it does not work. Then I finally found the macro editor (hidden in the preferences) and not only does the look correct, it validates and runs perfectly from the editor. Alas we cannot keep the macro editor open and still work in our document. And the macro still ...