Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'tabbing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 3 results

  1. Since I've already expanded a lot on the subject on my last post, I'll keep it short and to the point: Affinity apps almost completely disregard the macOS system-wide option “Full Keyboard Access: In windows and dialogues, press Tab to move keyboard focus between: All controls”, in the Keyboard prefpane. In fact, they don't even honour the alternative and default “Text boxes and lists only” on all places, which would include the very useful input fields on many different palettes. There are issues on important dialog boxes such as “New Document”, and the only palettes where fields are properly addressable via tabbing are, AFAIK, the Transform palette, and only partially so. Some allow for tabbing between one or two items, and all of them, regardless of the number of fields, drop the user into the “Tab to hide the Studio” behaviour, instead of cycling back to the first field like in Adobe CC. This behaviour is, for lack of a nicer term, undesirable and unintuitive, and I could also reproduce it in the Windows beta of Publisher; seeing how I can also reproduce it in the MAS versions of Photo and Designer, I'm willing to bet that it's also reproducible in the release-quality Windows versions of those as well. I also noticed input field and UI control ordering inconsistencies between the Mac and the Windows versions of Publisher. I am aware that fixing this would require an overhaul (or at least an internal review process) of six different codebases across two different OSes (though the fact that some palettes and dialogues are rather similar across apps, so there should at least be some economies of scale at work there), and introduce further overhead in your development process from now on (because it does indeed require a change in philosophy, as tabbing has up until now been added just as an afterthought and only in the places where we specifically asked for it, instead of everywhere, organically and by default, following a predictable scheme and behaviour), but this is yet another thing which I believe you also must do in order to be taken seriously by design professionals who actually use your apps for UI and UX work; you must lead by example, because many of your users will know a lot about that very subject. For the same reason, Adobe was the butt of all jokes for the better part of a decade on account of their lack of polish and consistency (there's even a Tumblr page called “Adobe Gripes” [formerly “Adobe UI Gripes”] dedicated to their misgivings: https://adobegripes.tumblr.com ), but even they got their act somewhat together as of late (there are still inconsistencies between different apps of their suite, but at least most of these nitty-gritty UX issues are pretty much solved by now). Seeing how you're still in the beginning of your expansion in the market, and only have 3 apps in two platforms to contend with, please take the opportunity to polish all of them before the arguably momentous 1.7 release, which will mark the completeness of the originally announced Affinity 1.x suite. All eyes will be, then and once more, on you, and some reviewers will possibly go through all those details (maybe even making brand-new reviews of the original first two apps), and call them all unpolished or unfinished. I know I would, because that's the way they feel, at least on this major point in particular.
  2. Hi guys, I know I'm probably in the minority here, but as a former longtime Windows PC user, all my Macs get the "tab between all elements” treatment (using the Ctrl+F7 shortcut), and I'm the master nitpicker when it comes to finding inconsistencies in the tabbing implementation because I happen to use the Tab key *a lot* (that's also what having two big screens and losing your mouse cursor a lot on a daily basis, even with El Capitan's “shake cursor to enlarge” function, does to you). This time, I realised two things: 1. When tabbing between fields and interface elements in the “New Document” window, I can never get to the four separators on the bottom half; 2. The little “Presets” button, with the four horizontal lines and the down arrow and to the right-hand side of the “Page Preset” drop-down menu, is never visually highlighted, though it is indeed selectable; also, when pressing the spacebar, the corresponding menu will not open adjacent to said button but underneath wherever the mouse cursor is; furthermore, this behaviour is reproducible in all Beta Affinity apps. So, yep, that's about it. If I can reproduce any of these behaviours elsewhere in Publisher, I'll let you know.
  3. Would like to see universal tabbing in the palettes.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.