BUG: UI - color page, stabilizer missing on screen controls

Color Page, Stabilizer
there are no backwards, pause, forwards control buttons visible. Only connected Mini Panel displays those controls.

S

Not a bug, it's the stabiliser that was introduced in v14. If you want the old stabiliser use the 3-dot menu. For more details read the manual.

Not a bug, it's the stabiliser that was introduced in v14. If you want the old stabiliser use the 3-dot menu. For more details read the manual.

when an app does not act in a reasonable and expected way, that qualifies as bug or bad design. everything is not read the manual for something so basic. I've really noticed there is this attitude here that when the UI fails or isn't clear, RTFM is the universal response. at over 1400 pages and growing, its simply not reasonable or practical to be expected to memorize the entire thing cover to cover. A good UI is about minimal manual reading and needing it for advanced operations, not basic ones like starting the tracker.

the controls simply should be present. is should not be change a mode, flip a swtich, then the magically appear. they should be present regardless of which mode the stabilzer is in and not be limited to only having a mini panel present. I've noticed the controls missing, but finally filed it as a bug because it is a bug / bad design that should be fixed because it looks, acts like a bug ergo it is.

RTFM is the most common response because it is the best answer most of the time. The manual is well written and very useful. I find it offers valuable insight that most manuals don't even try to offer.

Most modern apps/os's use some variation of the 3 dots to indicate an options menu. Common sense should tell one after clicking that options menu that an option referred to as "Classic" should bring back perceived missing items. Not really seeing the problem here.

Most PDF readers have this fantastic thing called a search tool, it works very well. Way better than a 1400 page paper manual.

The manual has kept me from making numerous posts.

The respondents are truly trying to help, and rather than rewrite the manual in a forum post, they cite the manual instead. Some even cite specific page numbers. Text on the screen is text on the screen no matter what, might as well use the stuff that's already there. Especially when it's already in the program and readily accessed from the help menu.

RTFM is the most common response because it is the best answer most of the time. The manual is well written and very useful. I find it offers valuable insight that most manuals don't even try to offer.

Most modern apps/os's use some variation of the 3 dots to indicate an options menu. Common sense should tell one after clicking that options menu that an option referred to as "Classic" should bring back perceived missing items. Not really seeing the problem here.

sigh. I've spent 15+ years being a part of UI design and development. You use software I've had input and influence on every day. NDA's, can't say more. Instead of defending UI problems, how about fixing them ? not workarounds but fixing them ? The Classic tracker uses the CPU. Its different. Its still not right that the UI is missing important UI elements, the mode doesn't matter. This isn't a RFTM situation, its a fix the design omission which isn't hard, which probably keeps getting pushed down the list as less critical fix because its not a crasher. When users bring attention to something like this, it will get fixed sooner rather than later, hopefully.

as for the dot menu, its not "common sense" and its not really discoverable. you simply happen to know its there, but most folks don't. other apps have the same "lets throw important things in this obscure place because we don't know where else to put it" problem too and no one knows they are there.

S