evanem
Joined 4 years ago
Joined 4 years ago
I posted about version 2 a year and a half ago and thought I'd do a follow up since I've added a lot of features since then. I just added printing and PDF export capability, a popular request among my user base. I've also added pivot tables, JSON and XML importing and exporting, improved statistics, ASCII Separated Values parsing, aesthetic improvements, and a bunch of little things to improve the user experience.
It's enough to justify a major version upgrade, but I have some lofty plans for version 3 which is in the works. If you have any requests, I'd love to hear them!
- A preferences window for settings, keyboard shortcuts, and file extension options
- A Unique Values feature
- A File Metadata pane to easily set up things like header rows
- The command launcher width changes as the window width is changed.
A few were addressed in version 1:
- Persistent storage of settings set via command
- Headers rows frozen by default
Header columns work the same way as header rows, just vertically. I use consistent verbiage for clarity. If they appeared to do nothing for you, the reason is probably that the number of header columns is 0 by default. I haven't seen any confusion about it since adding the File Metadata pane.
There's a Minimum Number of Table Rows/Columns setting that's set to 50 by default. You can set it as low as 1. There's also a Number of Buffer Rows/Columns that will add rows and columns beyond the data. It's set to 2 by default.
I'll take a good look at scrolling on Mac. I haven't seen problems with my setup, so I'll work to reproduce what others are seeing.
2. That first bug is known and for reasons I don't recall, is much trickier than one would think. It's still on my to-do list. The thing with dragging and selecting everything sounds like it might be scrolling really fast.
3. I'll consider it. Perhaps a smart paste option where it attempts to determine the nature of the text (e.g. whether it's a database table or what kind of delimiter it uses) and pastes accordingly.
4. I'll give this some thought as well. I'm not sure that disabling the commands is the way to go if the user doesn't know why they're disabled.
5. If you have any more questions, feel free to ask. Also, if you do buy and change your mind, just let me know and I'll issue a refund right away.
I'll set up a similar file and see what I can do to improve this.
For now, one alternative is to filter OUT the data you want removed, then use the Remove All Filtered Out and Hidden Data command.