![]() ![]() It is so bad we have to have FAQ for people on it to explain how to workaround it when needed. If in the Mac world you can't count on the right mouse button being there then something like holding down the Command key could do the same.īTW the usability of move in Quicken Windows stinks, and no matter how long people have been complaining about it they have yet to change it. In the Windows world if I drag and drop with a right click when I release it, it will give me a menu of move/copy/cancel (the default is decided by the context of the move). What I do these days is just edit the next instance of the paycheck reminder so the next date is today, and then enter that changing as needed.Īnd yes just so you know I do like the idea of drag an drop for moving transactions to other accounts, I just think it should also have copy. I think at one time I did try copy and past, but found that to be very cumbersome. When my wife gets a bonus I have to enter another paycheck that has the same fields and such. I do have one use case I do very often where it might better that what I do now. In fact duplicate would be that "different operation/menu" I mentioned. I wasn't criticizing it, just found it "interesting" coming from the Windows side. If duplicate is something that is common in the Mac world then I think it fits, and I agree that it should be the current date. Once users understand transactions - a single one or any grouping of them - can be moved by simply selecting and dropping onto another account, I think everyone appreciates the simplicity I haven't seen any complaints about moving transactions. ![]() The only downside is that it's not inherently intuitive to users old older Quicken software, who often look for a menu command to move a transaction. ![]() What am I pasting into? Command-D for Duplicate is nearly as universal in Mac applications and cut/copy/paste.Īs for moving between accounts, I can't think of an easier way to do it than Quicken Mac's drag and drop. I think duplicating a transaction makes more sense than copying and pasting a transaction. But when I do so now, I'm creating and tweaking a QuickFill rule for the Payee, so I won't need to go back to find an old transaction for that Payee again. But some users find QuickFill rules complicate, or don't have the patience to curate them to fit their needs, or don't want them most of the time - and those users probably make use of Duplicate much more often. I use this at times to make sure I'm consistently using the same category, and consistently recording things in the same way in the memo field. I set up all my bills, but I many times end up paying the bill earlier, and when I mark a scheduled transaction in the register as paid, I now have to change the date to today.Ĭurrently to change to today's date requires two clicks on the date field, then type T followed by ENTER/RETURN to save the Duplicating a transaction is helpful if there's no QuickFill rule for the Payee go back and find an old transaction, duplicate it, put the current date on it and otherwise modify if needed. Here is another reason that today's date makes much more sense for most of the time. I feel when I duplicate a transaction, it should default to today's date while still allow you to edit the date if needed. Having today's date automatically entered places the transaction on the top of the register. Many times the need to duplicate a transaction, is an older one, where I have to scroll down the register to find it. Yes, I am familiar with the shortcut T, but now I have to click into the date field, and press T. Quicken is not really very responsive, I find it rather slow, compared to Moneydance what I used before (I have a Mac mini 2018 Core i7 with 64GB of RAM). When it comes to data entry efficiency, every additional click is just slowing me down. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |