Search the Community
Showing results for tags '64 bit'.
I use a ANSI (qwerty) keyboard, but type in multiple languages, most of which are european, so I use the EURkey keyboard layout by Steffen Brüntjen to type the language specific letters occasionally needed. As an example to type the german Umlauts (ä,ü,ö) you would use the keybind "CTRL+ALT+A/U/O" or "AltGr + A/U/O". In Affinity Publisher 2, when typing in a Text Frame or Artistic Text Frame, the same keybinds with "CTRL+ALT" do not produce the desired characters, instead no input is read by the program. Using "AltGr" does produce the desired characters in the Text Frames. Interestingly if I go to Edit -> Preferences -> Auto-Correct and type in the "Replace" or "With" input fields, the program behaves as expected with both input methods, meaning that it can read the inputs normally. The problem can repeatedly be reproduced on new files. Technical details: Windows 10 Home 64 bit, Version 21H1 OS build 19043.1526 Ryzen 5 5600X processor 16 GB RAM Radeon RX 6800 XT Graphics card Issue persists with and without hardware acceleration enabled No relevant background software that may intercept the keystrokes other than the OS Recipe: Have ANSI (qwerty) Keyboard (Issue supposedly appears on other keyboards too) Have EURkey keyboard layout installed and selected Open Affinity Publisher 2 Create new Project Create a text or artistitc text frame Type in it Try to insert special characters with the CTRL+ALT+Character binding Unverified personal assumtions regarding the issue: The only other program where I have seen similar behavior in the past was in Joplin, a notetaking software. In there the issue existed because the keybindings were already preoccupied by the program, and had to be unbound in the settings. After unbinding it worked as intended. Since in Affinity Publisher 2 only one of the relevant keybindings seems to be preoccupied with another keybind ( CTRL+ALT+SHIFT+S for export), this solution does not work here. However my assumption is that the program somehow blocks the keybind because it reads some of the input. Since using AltGr keybinds works, my assumption is that the issue is the using of the CTRL key on the keyboard to switch into the mode in which you can see the distances of text fields to their surroundings (for lack of a more specific term). A "fix" could consist of either making it so that the keybinds work on EURKey again (evaluating how realistic that is is beyond my technical skills), or giving us the option to bind this control mode in the settings to some other key, which might also work. I'm of course willing to elaborate should further information help on my part. I know this is a bit of a nieche issue, but it seems like unwanted behavior and as such it should qualify as a bug. I asked about possible ways to fix it in the Support & Questions part of the forums and was advised to specify it as a bugreport. Thank you for your time.
Hello Affinity, just tried to install Affinity Photo on a PC with an AMD Opteron 180 CPU. This CPU is a 64 Bit CPU, nevertheless I can't install Affinity Photo because "no 64 Bit CPU was detected" Is there a known limitation with AMD processors? In the Q&A I could not find a hint... Thanks for your answer Regards, Holger