Community

I apologize if I have been snarky about this topic, but I guess it has become somewhat of an emotional issue for me. I have been using TextPad for a few years now and have maintained a paid license for the product. I develop software professionally, and I am expected to support my customers in ...

TextPad is useful. TextPad is efficient. Unfortunately, TextPad's author doesn't make enough money from TextPad license sales (so it seems) to justify the hiring and maintenance of a team of developers to evolve the product. Perhaps TextPad's author does, but has decided not to mess with a good ...

Hmm...interesting...you suggest simply providing an API of sorts then letting the community go to town? Lovely idea! How about the macro capability then? The programmer of an API-based "plugin" must have access to the keyboard I/O stream, of course. Helios could provide a COM API, perhaps. The API ...

I tend use Eclipse or Visual Studio for most development tasks, but use TextPad for finessing large amount of text (e.g., sorting, reformatting) and for its quick-view ability for any text (quick-to-execute from the command line). Its syntax highlight ability for so many file types is also a very ...

HerNameWasTextPad, I understand your point, and it's a good one. I am not suggesting however that Helios prioritize the development of editable macros above all else. My point was that your response was dismissive and condescending. This is not a way to run a railroad! I suggest that Helios at least ...

Dear HerNameWasTextPad, I am sorry, but that was a very unsatisfactory answer. Notate the keystrokes by hand? That wouldn't be bad if TextPad could then import my notation and make a new macro out of it (or overwrite an existing one). Besides, that is a lot of unnecessary work! Here is my suggestion ...