JAWS Quicken Release Notes
- In some cases the say line wasn't working. Change the position for cursor movement to the active field instead of the left side of the window before using the GetLine() function.
- Cleaned up the key mappings to remove scripts that don't work.
- Added Ctrl+Shift+ arrow keys to the Navigate functions which are already mapped to JAWSKey+Alt+ arrow key. This was done because Quicken 2017 stealing and getting stuck on Alt keys. Ctrl and Shift seem to be a bit better in this regard.
- Fixed a minor problem where if the bottom region (Downloaded Transactions tab) isn't there, you couldn't navigate going down from the middle/register to the top region.
- Navigation between the three "regions" of the register. In general most parts of Quicken have three "regions". There is a top region where there are some controls, and the middle will have the "view"/register, and then there will be some controls below that, which I'm calling the bottom region. Now you can use JAWSKey + Alt + up/down arrow to move between these regions. And for the top region only you can use JAWSKey + Alt + left/right to move between the controls in that region. This currently only supported in the registers. The reason for only supporting the left and right functions in the top region and not in the bottom region is because the top region tab stops in the register are messed up and need this. For the bottom region the tabbing works for the most part.
- Working in both the regular and investment account registers is much more solid then it was before with the old scripts. The old scripts wouldn't say the transaction properly when you gave the Say Line command (JAWSKey + up arrow), and they didn't work in two line mode. And they would say more than one transaction when only one should have been said. Note that the investment accounts still have a lot of loss of focus problems. You can usually use Alt + Tab to go away from Quicken and back, and it will usually get the focus back. Also there are a few investment transaction types that have no editable fields on them. For instance RevinstDiv and MiscExp. If you arrow key into one of these transactions, the whole transaction will be read. Also note while in the registers, to be able to silence all the built in messages that are not saying the right information, the current scripts will put JAWS in echo none mode if you are in echo hightlighted or echo all mode. What is said can be controlled with the JAWS Quick Settings.
- The pop menus for the payee, category, and tag, now properly read the items as you use your arrows to go up and down in the menu.
- Various settings are user configurable by using the JAWS Quick Settings, which you access by JAWSKey + v. The new settings are at the top, under Quicken. For instance whether to say the field headers or not, or what to say when you used the arrow keys to go to the next/prior line.
- A workaround for the Preferences dialog. You can now use JAWSKey + Alt + up/down arrows to go up and down the tree of preference types.
- Another workaround is for the Edit Paycheck dialog. When in one of the amount fields you can press Ctrl + e to bring up the edit box for it. Pressing Ctrl + d can be used to delete that field. Note Quicken doesn't prompt you to be sure you want it deleted, but if you make a mistake you can exit out of the paycheck dialog without saving.
- The say balances functions have been rewritten to be much more generic and maintainable. The old scripts had a function for every window/dialog, now there is just one main one. I noticed that in some cases it would repeat a balance, and at other times not say given balance. The new scripts fix these problems and make it easier to extend to other windows/dialogs.
- The say balances command (JAWSKey + Delete) in the reconcile window will not only tell you the "standard" balances, it will also report the number and amount of transactions for both credits and debits.
- Modified the existing scripts for a few problems, and provided to a very limited amount of people.
- I decided later that starting from scratch was a better approach given the current condition of the code. That is Beta 2, and after.