Chris Messina Posted December 4, 2021 Share Posted December 4, 2021 It turns out that you can have conflicting Hotkey Combos, even if a Workflow is disabled. It seems like disabled Workflows shouldn't be considered when looking for conflicts. deanishe 1 Link to comment Share on other sites More sharing options...
Andrew Posted December 5, 2021 Share Posted December 5, 2021 I'm moving this to closed as this isn't a "conflict", it's just a highlight to show you that there is another workflow using that combo. This doesn't stop the hotkey from working, and seeing that the combo is shared with a disabled workflow is still useful as this notifies of any potential future "conflict". I've added more details in your other thread. Chris Messina 1 Link to comment Share on other sites More sharing options...
Chris Messina Posted December 6, 2021 Author Share Posted December 6, 2021 Yep, the information in the other thread invalidates this report, although I added some additional suggestions for clarifying the behavior of shared hotkey triggers! Link to comment Share on other sites More sharing options...
Andrew Posted January 4, 2022 Share Posted January 4, 2022 The behaviour has now been rectified in the 4.6.2 b1276 pre-release, so you shouldn't see odd situations where you can't set a combo used in a disabled workflow. Chris Messina 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now