Tab Key in Crop tool (and others) broken

[ronnyb]

1. Select Custom Ratio

2. Input a number, any number of your choosing....

3. Press Tab key to jump to next input field

4. Interface disappears.

5. WHEN ARE YOU GOING TO FIX THIS? IT'S BEEN REPORTED YEARS AGO!! FIX THE UI AND STOP WASTING TIME WITH STUPID AI FEATURES?!

[Hangman]

Hi @ronnyb,

Unless Keyboard Navigation is a major part of your workflow turning it off under the Mac's Keyboard Settings and removing the Toggle UI keyboard shortcut in Affinity Photo (which uses the tab key) should alleviate the frustration until the bug is fixed...

[Affinity Info Bot]

An issue raised in this thread ("Crop Tool - tabbing does not highlight next input box with Keyboard Navigation or Full Keyboard Access enabled ") has now been reported to the developers by the testing team (Ref: AF-1821). Thank you very much for reporting this issue to us.

[ronnyb]

3 hours ago, Hangman said:

Hi @ronnyb,

Unless Keyboard Navigation is a major part of your workflow turning it off under the Mac's Keyboard Settings and removing the Toggle UI keyboard shortcut in Affinity Photo (which uses the tab key) should alleviate the frustration until the bug is fixed...

Thanks @Hangmanbut that’s not an option. 

This bug is numbered 1829, and the “new” bugs are already numbered beyond 5200, it gives you an idea of how many bug reports before the current ones this one was “logged with developers.”

At least it’s been confirmed where the logs get put: obviously they get printed on the developers’ rolls of toilet paper for their review while in the bathroom, for wiping their a$$ with, it seems….

I’m sure it will get fixed after Affinity introduce the new, upcoming, super duper AI (Affinity Intelligence?) Auto-delete Cloud, Network, and External Drive Files™  

Oh wait, that feature has been working for years! We might not have to wait much longer for Affinity (UI Guru Godot?) to fix this…..

Guess who’s not holding his breath? 

[Alfred]

5 hours ago, ronnyb said:

This bug is numbered 1829, and the “new” bugs are already numbered beyond 5200, it gives you an idea of how many bug reports before the current ones this one was “logged with developers.”

This issue is labelled AF-1821 (not 1829, for what it’s worth). That’s a Jira ‘issue’ number, not a ‘bug’ number: other issues in the AF project will belong to the same numerical sequence, but the majority of them will may not be bugs. Of those issues that actually are bugs, many of them will be trivial (e.g. a spelling error or a cosmetic flaw in the UI) and many others will be minor (easy to work around). The bugs that really matter are the ones that have a major impact (because there’s no easy workaround) or are critical because they result in program crashes and/or data loss.

[ronnyb]

19 hours ago, Alfred said:

This issue is labelled AF-1821 (not 1829, for what it’s worth). That’s a Jira ‘issue’ number, not a ‘bug’ number: other issues in the AF project will belong to the same numerical sequence, but the majority of them will may not be bugs. Of those issues that actually are bugs, many of them will be trivial (e.g. a spelling error or a cosmetic flaw in the UI) and many others will be minor (easy to work around). The bugs that really matter are the ones that have a major impact (because there’s no easy workaround) or are critical because they result in program crashes and/or data loss.

Like saving reliably to cloud drives, external USB drives, or Network drives? BC that “issue” has been around for YEARS and is still not fixed! Is that what you’re referring to?

I’ve been around the forums for nearly a decade to know what’s what; I've reported literally several hundred “issues” bugs etc. and they’re still plaguing us, but the NEW AI AUTOSELECT IS HERE!!! 😂

There are STILL issues with rendering FX, blend modes, and reliable exporting, on top of UI issues!

Really @Alfred we all had great hopes and intentions, but its time to stop being Affinity Apologists and open our eyes! Its been YEARS of Affinity ignoring bugs and plowing ahead building on top of a shaky foundation.  
i absolutely HATE writing this, i had tremendous hopes for Affinity but there’s a fundamental problem with the way development progresses and is managed.