
M1000
Members-
Posts
50 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
M1000 started following the black color is always CMYK process , Histogram is not working / not active / not reloading , Hide Fonts and 6 others
-
Histogram is not working / not active / not reloading
M1000 replied to Paulchen2000's topic in V2 Bugs found on macOS
Got exactly the same problem on Windows. Histogram arbitrarily stops working. -
M1000 reacted to a post in a topic: Has V2 fixed Affinity's biggest issues?
-
Since it's a very old problem on Mac and Windows with foreign language fonts cluttering the font list as mentioned in many threads like these: https://forum.affinity.serif.com/index.php?/topic/105413-hide-foreign-language-fonts/#comment-568576 https://forum.affinity.serif.com/index.php?/topic/176769-hide-windows-fonts-that-are-set-to-hidden/#comment-1017054 https://forum.affinity.serif.com/index.php?/topic/72704-would-like-an-option-to-hide-system-fonts/#comment-378131 https://forum.affinity.serif.com/index.php?/topic/123803-want-to-remove-noto-fonts-split/page/3/#comment-1017261 https://forum.affinity.serif.com/index.php?/topic/98225-can-you-remove-junk-fonts-from-publisher/page/2/ Why not add a hide fonts tab like this: Of course one could add all non foreign language fonts to the Favourites tab, but every time you add new fonts for another project, you have to add them to the Favourites again. With hidden fonts, you just hide the unwanted fonts once. This seems to me like a simple approach to this problem.
-
M1000 reacted to a post in a topic: Print Production needs Overprint, and Color (Ink) Separation
-
PaulEC reacted to a post in a topic: Affinity changes filetype ... again
-
If you set any file to always open with Affinity Apps in the Windows File Explorer, Affinity Apps change the filetype for that image file format to "Affinity Designer/Photo/Publisher File", making it impossible to sort files by type in the Windows File Explorer. Other programs don't do that. (old thread) I was happy to see this was changed in Version 2 (I had installed the MSIX Version). But now with 2.1 (MSI Version) this was changed back again to the old behaviour. Is this different between the MSIX and MSI Versions? I'd prefer to use the MSI Version though, because of some quirks the MSIX Version has (can't drag files on the Affinity Apps on the taskbar to open etc.).
-
M1000 reacted to a post in a topic: Blend tool in Designer
-
lepr reacted to a post in a topic: Suggestion: a global angle for layer effects
-
RNKLN reacted to a post in a topic: Suggestion: a global angle for layer effects
-
Hilltop reacted to a post in a topic: Suggestion: a global angle for layer effects
-
deeds reacted to a post in a topic: Suggestion: a global angle for layer effects
-
Since it's now possible to have multiple instances of layer effects, wouldn't it be nice to have a checkbox for a global angle for those multiple effects? And wouldn't it be even nicer to have an independent offset value to change the angle based on that global angle? Currently it's quite annoying to change the angle for multiple effects on a complex layer effect. Here's a mockup:
-
mschwerer reacted to a post in a topic: Layout with more than 2 spreads
-
Layout with more than 2 spreads
M1000 replied to mschwerer's topic in Feedback for the Affinity V2 Suite of Products
I guess what mschwerer meant was having more than two pages side by side (by side) in the pages panel. Like a roll fold for example. more in this thread -
Show pixel layer DPI in transform panel
M1000 replied to NotMyFault's topic in Feedback for the Affinity V2 Suite of Products
A double-click on one of the four diagonal handle points to reset DPI to document DPI would be nice too. -
Frequent Lagging experienced in Affinity Desinger V2
M1000 replied to mara.cernoch's topic in V2 Bugs found on Windows
Got exactly the same problem, lag after a while. And when i quit Designer then it keeps running in the background, still using the CPU like Hephaestus described in this thread. -
LostInTranslation reacted to a post in a topic: Interactive Colour Chords
-
adcze reacted to a post in a topic: Interactive Colour Chords
-
M1000 reacted to a post in a topic: Display Brush Names
-
dcarvalho84 reacted to a post in a topic: Interactive Colour Chords
-
Murfee reacted to a post in a topic: Interactive Colour Chords
-
-
In the Fields panel the text is cut off at the beginning
M1000 replied to M1000's topic in V2 Bugs found on Windows
-
M1000 reacted to a post in a topic: In the Fields panel the text is cut off at the beginning
-
I appreciate your efforts, but I don't need any help with neither the Windows Filesystem nor with Affinity Photo. That's why I posted this in the Bugs section. I'm just stating the fact that the Type column always shows "Affinity Photo File" for all different image formats, if you set them to always open with Affinity Photo. Other programs don't because it's pointless. It's not a Windows decision, it's because of the entries Affinity wrote in the Windows Registry during installation. I can see from your screen grab how it should be. Developers should either leave the Type as it is or use their own description in the Windows Registry as Irfan View does: Irfan View PNG File Irfan View JPEG File or VLC Player: MP3 Audio File (VLC) WAV Audio File (VLC) But changing all image formats to the exact same Type is – sorry to repeat myself – pointless.
-
When a Affinity Photo is installed it is up to the program what happens when you associate a filetype to the program via "open with". Because Affinity puts entries in the Windows Registry during installation which determine that the Type is set to Affinity Photo for all the image formats. So Affinity indirectly changes the Type. It is not common practice to set the same Type for different extensions because it results in a bad user experience. Just have a look at the examples of the other programs. Clip Studio for example just doesn't put these entries in the Registry so the types stay the same. There's just no sense in making it like Affinity does. I'm fully aware of that and never wrote that the extensions changed. It's about the Type column. This is a workaround which should not be necessary.