anto Posted January 26 Posted January 26 You can assign the same shortcuts to different items. The attention icon appears only when you switch to another person. 2025-01-26 10-31-18.mp4 Quote
Hangman Posted January 26 Posted January 26 3 hours ago, anto said: You can assign the same shortcuts to different items. The attention icon appears only when you switch to another person. This is not unique to the Beta it has always been the case, even in Version 1... AFAIK this is 'by design'... the first function the shortcut is applied to takes precedence over later instances so my assumption (rightly or wrongly) is that if you wish to assign or reassign a particular shortcut to a different function the warning triangle simply warns you it's already assigned and therefore won't override the existing shortcut application allowing you to reassign either the existing shortcut or informing you that you need to change this particular shortcut for something else... Where Windows and Mac differ is Windows physically shows the same shortcut in the menus for every function it has been applied to while Mac only shows it for the first function it has been applied to even when applied to multiple functions. Whether this is a bug or Windows behaviour I'm unsure... Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
anto Posted January 26 Author Posted January 26 3 minutes ago, Hangman said: This is not unique to the Beta it has always been the case, even in Version 1... AFAIK this is 'by design'... the first function the shortcut is applied to takes precedence over later instances so my assumption (rightly or wrongly) is that if you wish to assign or reassign a particular shortcut to a different function the warning triangle simply warns you it's already assigned and therefore won't override the existing shortcut application allowing you to reassign either the existing shortcut or informing you that you need to change this particular shortcut for something else... Where Windows and Mac differ is Windows physically shows the same shortcut in the menus for every function it has been applied to while Mac only shows it for the first function it has been applied to even when applied to multiple functions. Whether this is a bug or Windows behaviour I'm unsure... I'm saying that if the same key combination is assigned, there should be a warning, but there isn't. What are you talking about? And what does this have to do with the non-beta version? It's impossible to assign shortcuts at all because the program doesn't check and tell you whether the combination has already been assigned or not. Quote
walt.farrell Posted January 26 Posted January 26 5 minutes ago, anto said: And what does this have to do with the non-beta version? You reported this against the Beta, but it is not (as Hangman mentioned) a "new bug or issue" in the Beta. Thus it should have been reported in the normal Bugs forum. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
anto Posted January 26 Author Posted January 26 1 minute ago, walt.farrell said: You reported this against the Beta, but it is not (as Hangman mentioned) a "new bug or issue" in the Beta. Thus it should have been reported in the normal Bugs forum. But it doesn't matter if it's been around since version 1. It needs to be fixed! Quote
Hangman Posted January 26 Posted January 26 9 minutes ago, anto said: I'm saying that if the same key combination is assigned, there should be a warning, but there isn't. With you now, in which case, yes this is a Windows bug, only reported in the wrong forum. On Mac, the Warning triangle is correctly shown when switching Persona's... 1 minute ago, anto said: But it doesn't matter if it's been around since version 1. It needs to be fixed! That's not the point, the Beta forums are for reporting issues unique to the Beta's... Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
Staff Patrick Connor Posted January 26 Staff Posted January 26 2 minutes ago, anto said: But it doesn't matter if it's been around since version 1. Yes it does. Posting in the beta forums has rules which you need to follow, not ignore . Thread moved Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
anto Posted January 26 Author Posted January 26 6 minutes ago, Patrick Connor said: Yes it does. Posting in the beta forums has rules which you need to follow, not ignore But this does not solve the problem. I don't have version 1 and can't check in all versions. A moderator can move the topic to the right place. Why do ordinary users write about this and clog up the thread? Since version 1, how many beta versions have there been and they couldn't fix it? Quote
anto Posted January 26 Author Posted January 26 @Patrick Connor You have moved the topic to Q&A. This is not a question. It is a problem. Should I write to the bugs again? Quote
Staff Patrick Connor Posted January 26 Staff Posted January 26 Just now, anto said: You have moved the topic to Q&A My mistake anto 1 Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
Staff Patrick Connor Posted January 26 Staff Posted January 26 2 minutes ago, anto said: I don't have version 1 Do you have 2.5.7 release build. If it's affected then you don't post in the beta forums. But you know that, you just choose to ignore it Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
carl123 Posted January 26 Posted January 26 40 minutes ago, anto said: Since version 1, how many beta versions have there been and they couldn't fix it? For me... The bug is in V1, not in V2.5.7 but back in 2.6 beta Windows 11 (all apps are .exe versions) Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Staff Patrick Connor Posted January 26 Staff Posted January 26 1 minute ago, carl123 said: For me... The bug is in V1, not in V2.5.7 but back in 2.6 beta Windows (all apps are .exe versions) Well then I may owe Anto an apology. Will have it checked out tomorrow Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
anto Posted January 26 Author Posted January 26 1 minute ago, Patrick Connor said: Do you have 2.5.7 release build. If it's affected then you don't post in the beta forums. But you know that, you just choose to ignore it No, but I am now redefining the shortcuts as I see fit. And very often the shortcuts don't work. Quote
Hangman Posted January 26 Posted January 26 3 minutes ago, anto said: No, but I am now redefining the shortcuts as I see fit. And very often the shortcuts don't work. They will only work, as mentioned above, for the first instance the shortcut has been applied to. Clearly, the lack of the Warning Triangle on Windows is an issue because you're not being warned that the shortcut is already in use for a different function so applying an existing shortcut to another function won't work, you're just not being warned about it... Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
anto Posted January 26 Author Posted January 26 4 minutes ago, Hangman said: They will only work, as mentioned above, for the first instance the shortcut has been applied to. Clearly, the lack of the Warning Triangle on Windows is an issue because you're not being warned that the shortcut is already in use for a different function so applying an existing shortcut to another function won't work, you're just not being warned about it... This is exactly what I am talking about. But I don't think it's that hard to fix that it hasn't been fixed before now. Quote
carl123 Posted January 26 Posted January 26 11 minutes ago, Hangman said: I do see the issue in 2.5.7 (.exe version)... I don't, V2.5.7 correctly identifies the conflicting shortcuts Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Hangman Posted January 26 Posted January 26 36 minutes ago, anto said: This is exactly what I am talking about. But I don't think it's that hard to fix that it hasn't been fixed before now. Okay, so this is not a bug, the reason you're not seeing the Warning Triangles is because you don't have Apply to all checked. Apply to all—If checked, the shortcut applied to a UI element is shared across every Persona. If unchecked, you can uniquely assign a custom shortcut to work just within the currently selected Persona in the initial Persona pop-up menu. 33 minutes ago, carl123 said: I don't, V2.5.7 correctly identifies the conflicting shortcuts This is also why I was seeing the issue in 2.5.7 but you weren't, i.e., in 2.5.7 I don't have Apply to all selected... @anto to check, try the following... Ensure Ctrl N is only assigned to New... across all three apps. Check Apply to all and then apply Ctrl N to a different function in Publisher and you will see the Warning Triangle. Clear the duplicate, switch to the Designer or Photo Persona and apply Ctrl N to another function and you should now see the warning triangles are shown... anto 1 Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
anto Posted January 26 Author Posted January 26 2 hours ago, Hangman said: Okay, so this is not a bug, the reason you're not seeing the Warning Triangles is because you don't have Apply to all checked. Apply to all—If checked, the shortcut applied to a UI element is shared across every Persona. If unchecked, you can uniquely assign a custom shortcut to work just within the currently selected Persona in the initial Persona pop-up menu. This is also why I was seeing the issue in 2.5.7 but you weren't, i.e., in 2.5.7 I don't have Apply to all selected... @anto to check, try the following... Ensure Ctrl N is only assigned to New... across all three apps. Check Apply to all and then apply Ctrl N to a different function in Publisher and you will see the Warning Triangle. Clear the duplicate, switch to the Designer or Photo Persona and apply Ctrl N to another function and you should now see the warning triangles are shown... Thank you. One problem is solved, but there is one more. Watch the video 2025-01-26 17-38-05.mp4 Quote
Hangman Posted January 26 Posted January 26 3 minutes ago, anto said: Thank you. One problem is solved, but there is one more. That is the correct behaviour... You initially set Ctrl+Shift+3 in Publisher for New Book, a function only available in Publisher. No other function uses the shortcut in Publisher so no Warning Triangle... You switch to Designer with Apply to all selected and set Ctrl+Shift+3 for Exit which exists in all three Personas. This will automatically apply it to Exit in both Publisher and Photo so when you switch back to the Publisher Persona it's shown as a conflicting shortcut because you previously applied it to New Book so the Warning Triangle appears as it should... Switch back to the Designer Persona and there is no Warning Triangle because in Designer Ctrl+Shift+3 doesn't conflict with any other Designer shortcut unlike in Publisher where it does... If instead of initially applying Ctrl+Shift+3 to New Book in Publisher you apply it to Edit in Photo (or any other function that exists in all three Personas) then switch to the Designer Persona and apply Ctrl+Shift+3 to Exit you will see the correct Warning Triangles in both Designer and Publisher... Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
anto Posted January 26 Author Posted January 26 1 minute ago, Hangman said: You initially set Ctrl+Shift+3 in Publisher for New Book, a function only available in Publisher. No other function uses the shortcut in Publisher so no Warning Triangle... I think this is wrong because I assigned this combination to Publisher. When I entered it in Designer, a message should have popped up saying that this combination is already in use. In this case, you can assign many incorrect combinations, which Publisher will check only after the window is closed. It should check it instantly when you enter it. Quote
anto Posted January 26 Author Posted January 26 4 minutes ago, Hangman said: only available in Publisher but i have checked Apply to all. Quote
Hangman Posted January 26 Posted January 26 Just now, anto said: When I entered it in Designer, a message should have popped up saying that this combination is already in use. It's used in Publisher for a function that doesn't exist in Designer so there is no keyboard shortcut conflict in Designer... Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
Hangman Posted January 26 Posted January 26 Just now, anto said: but i have checked Apply to all How can it Apply a shortcut to a function that doesn't exist in Designer? Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
anto Posted January 26 Author Posted January 26 Just now, Hangman said: How can it Apply a shortcut to a function that doesn't exist in Designer? Publisher should not check functions, but the key combinations that are entered for functions Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.