nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Make some Quicken functions run in the background

dodgecity

While performing a download for numerous accounts or accepting a large batch of downloaded transactions, that Quicken process dominates the app and I can't use any other parts of the tool. If quicken could make these processes run in the background, I could use the rest of the app while the download does its thing.

Find more posts tagged with

Reviewed

Status: Reviewed

Comments

Chris_QPW

There is a fundamental reason this isn't done. And I know this because it has been tried in the past. This also comes up with the request to abort One Step Update.

One Step Update doesn't just download things in some separate area and then update the rest of the GUI. One Step Update is actively interacting with the GUI.

So, if the developers let you go around changing things it would be like having two people trying to use your keyboard and mouse at the same time. There isn't anything that separates "the user" from "backend code" when trying to change things in the GUI.

Like I said they did try this at one point, but it was shortly reverted because of the problems it caused.

And the way this relates to aborting One Step Update is that One Step Update might be in the middle of doing such things and if it is interrupted it might leave things in a bad state. Determining when it is safe to abort when that was never in the design is extremely difficult.