przemoc
Members-
Posts
32 -
Joined
-
Last visited
-
OKlab - OKlch color space
przemoc replied to smg's topic in Feedback for the Affinity V2 Suite of Products
For reference mentioning archived v1 thread. -
bures reacted to a post in a topic: [REQ] Use filename as the layer name when opening non-Affinity files
-
przemoc started following Latest Affinity V2 release versions on each platform by store
-
No. AFAICT behavior is still the same as I wrote earlier (assuming 60Hz screen): There are like 1-2 frames showing wrong position and zoom (centered and shown fully, but it's a bit bigger than zoom to fit) of the document before it is shown properly (i.e. like it was left before switching to other document). I hope the behavior is clearly visible on videos that I uploaded before. I used various document zoom levels among apps to make it more prominent.
-
przemoc reacted to a post in a topic: Account window does not show all of My add-ons (all Affinity apps)
-
Chris B reacted to a post in a topic: Account window does not show all of My add-ons (all Affinity apps)
-
Tom Lachecki reacted to a post in a topic: Account window does not show all of My add-ons (all Affinity apps)
-
Granddaddy reacted to a post in a topic: [REQ] Use filename as the layer name when opening non-Affinity files
-
When you switch between more than one document opened in the same window, there are often issues with displaying them properly. For a split second document is often placed differently than it should, i.e. different than how it was zoomed&panned last time. (It seems to be even more prevalent when rulers are shown, but I'm not sure I can write it definitely.) It happens in all Affinity programs. Observed on Windows 7 and Windows 11 (not tested on others). Bug is present in current latest v1 (1.10.6.1665) and v2 (2.0.4.1701). Was present in previous versions too, possibly all of them. It is extremely irritating. I would love to get it fixed. I attached videos from all apps showing this problem. There are like 1-2 frames showing wrong position and zoom (centered and shown fully, but it's a bit bigger than zoom to fit) of the document before it is shown properly (i.e. like it was left before switching to other document). Carried over from v1 feedback: wrong-placement-and-zoom-affinity-designer-1.10.6.1665.mp4 wrong-placement-and-zoom-affinity-designer-2.0.4.1701.mp4 wrong-placement-and-zoom-affinity-photo-1.10.6.1665.mp4 wrong-placement-and-zoom-affinity-photo-2.0.4.1701.mp4 wrong-placement-and-zoom-affinity-publisher-1.10.6.1665.mp4 wrong-placement-and-zoom-affinity-publisher-2.0.4.1701.mp4
-
I tend to have many documents opened, reorder them depending on what I focus on, and switch between them, e.g. 3 out of N. Next Window and Previous Window actions (Ctrl+Tab, Ctrl+Shift+Tab by default, can be set in Preferences > Keyboard Shortcuts > Miscellaneous) do not follow tab order I have. It looks like they follow order in which files were opened. It would be great to have Next Tab and Previous Tab action for navigating tabs in display order. I would assign them to Ctrl+PageDown, Ctrl+PageUp by default. Carried over from v1:
-
If you open non-Affinity file, e.g. JPEG, the default layer name is "Background", which is inconvenient if you want to keep track of what you work with. It would be great if filename would be used as the layer name, by default or as an option. It would be also more consistent with existing behavior of drag and drop on the document, as then new layer name is the filename. Carried over from v1:
-
przemoc reacted to a post in a topic: Feature Request: Crop to Selection
-
There are seemingly 2 issues. 1. Add-ons that require downloading through browser are not shown unless "Show incompatible packs" are selected. This is a regression since v1, where one didn't have to select this option to see them. 2. Some add-ons are not shown at all, e.g: - Publication Typefaces Collection - Wallington Pro – Typeface It seems it's the case also for v1. I uploaded screenshots from Photo v1 and v2 showing 1st issue. It's impossible to show 2nd one. Issue applies to all Affinity apps, not only Photo.
-
Wrong zoom and placement of the document for a split second when switching between documents happens in all Affinity programs. Observed on Windows 7 and Windows 11 (not tested on others). Bug is present in current latest v1 (1.10.6.1665) and v2 (2.0.4.1701). I attached videos from all apps showing this problem. wrong-placement-and-zoom-affinity-designer-1.10.6.1665.mp4 wrong-placement-and-zoom-affinity-designer-2.0.4.1701.mp4 wrong-placement-and-zoom-affinity-photo-1.10.6.1665.mp4 wrong-placement-and-zoom-affinity-photo-2.0.4.1701.mp4 wrong-placement-and-zoom-affinity-publisher-1.10.6.1665.mp4 wrong-placement-and-zoom-affinity-publisher-2.0.4.1701.mp4 Carried over to v2 bugs:
-
Snapseed reacted to a post in a topic: Support perceptual color spaces like Oklab
-
When you switch between more than one document opened in the same window, there are often issues with displaying them properly. For a split second document is often placed differently than it should, i.e. different than how it was zoomed&panned last time. (It seems to be even more prevalent when rulers are shown, but I'm not sure I can write it definitely.) It happens roughly 5 of 10 or more times when switching tabs. It is extremely irritating. I would love to get it fixed.
-
I tend to have many documents opened, reorder them depending on what I focus on, and switch between them, e.g. 3 out of N. Next Window and Previous Window actions (Ctrl+Tab, Ctrl+Shift+Tab by default, can be set in Preferences > Keyboard Shortcuts > Miscellaneous) do not follow tab order I have. It looks like they follow order in which files were opened. It would be great to have Next Tab and Previous Tab action for navigating tabs in display order. I would assign them to Ctrl+PageDown, Ctrl+PageUp by default.
-
If you open non-Affinity file, e.g. JPEG, the default layer name is "Background", which is inconvenient if you want to keep track of what you work with. It would be great if filename would be used as the layer name, by default or as an option. It would be also more consistent with existing behavior of drag and drop on the document, as then new layer name is the filename.
-
mws reacted to a post in a topic: Support perceptual color spaces like Oklab
-
kenmcd reacted to a post in a topic: Support perceptual color spaces like Oklab
-
It would be great if Affinity products started supporting perceptual color spaces for image processing, like Björn Ottosson's Oklab. Let me quote two sections from Björn's post: References: https://bottosson.github.io/posts/oklab/ https://news.ycombinator.com/item?id=25525726 https://raphlinus.github.io/color/2021/01/18/oklab-critique.html https://news.ycombinator.com/item?id=25830327
-
Tom Lachecki reacted to a post in a topic: Stocks-Tab: Unsplash not working
-
Mark Ingram reacted to a post in a topic: Stocks-Tab: Unsplash not working
-
@carl123 There is a difference between "REGEDIT4" and "Windows Registry Editor Version 5.00" .reg files. The first use single-byte Windows character encoding (typically Windows-1252), the latter use UTF-16 (characters represented using code points taking 16 bits or more). In notepad the first one is called ANSI (which is a terrible name, as it has nothing to do with ANSI), the second one - Unicode (which is not as precise as it could be, but well, Microsoft...). So I suspect that during saving you did not set Unicode, that's why it wasn't working properly for you, so you did the change yourself in regedit, exported and shared it afterwards in the thread.
-
Stocks-Tab: Unsplash not working
przemoc replied to LostInTranslation's topic in V1 Bugs found on Windows
On the mentioned "Transport Layer Security (TLS) best practices with the .NET Framework" we can also read: So I think AP should simply set TLS 1.2 if it detects it runs on Windows 7. I believe it's a pragmatic solution. -
Stocks-Tab: Unsplash not working
przemoc replied to LostInTranslation's topic in V1 Bugs found on Windows
Thanks, Mark. I also confirm that editing registry as suggested in link provided by carl123 workarounds the issue. Thanks! There is a useful tidbit there that I wasn't aware, which is worth quoting explicitly here. Basically adding following stuff in registry is sufficient to make Unsplash work in AP: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 I call it a workaround, because I think it should be fixed in AP without need for changing user's registry. Even if TLS 1.2 is disabled by default in Secure Channel (schannel) as configured in Windows 7 out-of-the-box, it remains supported, so it should be possible to enable it in programmatic way from any application that needs it.