Page 2 of 2

Re: Transport control between windows

Posted: Sun Sep 02, 2018 3:43 pm
by HalfNote5
steve wrote:
Sun Sep 02, 2018 1:58 pm
...From a software development point of view, I much prefer features that are designed to perform a function, than "accidental" features that just happen to work for some workflows but were never actually intended. In the former case, the feature can be properly documented and maintained. ;)
Believe you me, I'm on board with that! heheh. In addition to the studio, I've run an IT/programming company for a lot of years, (used to program a lot in VFP - mostly database stuff) and you would not BELIEVE the creative ways my clients came up with of using/subverting/destroying my programs! :lol:

It was a couple years before I got into the mindset of "well, if this is how they expect it to work, it'll be easier to change the program than to change them," but it was still always a balancing act.

Of course, as a programmer, I also realize you're absolutely correct - a nice convenience for *me* poses an unintended workflow risk for 99.9% of other users, and so it makes sense to keep within the main user's base.

If I wasn't so lazy I COULD compile a custom copy but...... that seems a bit extravagant, and a further unnecessary gotcha. "Special" versions of software floating randomly around are to be avoided at all costs, in my experience. You never know how they're going to behave in someone else's hands. :D

That said, a project manager might be the way to go. OR! I could whip up a universal transport control app. Have it grab the active one, and have it set to "always on top" so long as an Audacity window had window focus. Not a bad idea at all! Maybe add some other cool features like file access, library index, listing, browsing. ^_^

Now the problem is finding time to whip it up...