orangefizz
Members-
Posts
118 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
PaulEC reacted to a post in a topic: Text boxes all have a background colour
-
GarryP reacted to a post in a topic: Text boxes all have a background colour
-
mopperle reacted to a post in a topic: Text boxes all have a background colour
-
hokic reacted to a post in a topic: Hand/move tool is not consistent
-
Brian_J reacted to a post in a topic: Feature request: save layers position state when opening other tabs/re-opening a doc
-
Dev question: why do we have to use a tool to see a PDF *as it was exported*? If I exported a PDF with crop marks and bleed, why are you loading that same PDF displaying neither?
- 6 replies
-
- how to
- bleed issue
-
(and 1 more)
Tagged with:
-
Catshill reacted to a post in a topic: Odd behavior in paragraph leading
-
And, as I found in that and other related posts here, the "explanations" only address the app's functionality, not the aim of a *photo editing* app or a *photo editor's* needs. Really, I'm just on here trying to improve the app from the POV of a user, not to be a PITA. This stuff matters. It's a photo editing app. Unless I *place* an image—that is, with the intention to ensure non-destructive editing—I would expect direct, destructive control of the image's pixels without the need for additional steps, monkey business, or lengthy explanations on the developer's forum. See the screen recording. THIS makes no sense to me. Why even give me a marquee tool? You have the image, you have the coordinates, what exactly is the problem here? Make it work. I am really now so talked out on this, friend. Happy trails. Screen Recording 2023-05-17 at 7.21.25 AM.mov
-
orangefizz reacted to a post in a topic: Odd behavior in paragraph leading
-
@thomaso you got me excited! I didn't know there was a percentage modifier and immediately went to check if I had somehow selected that. Nope, it's set to "default". What's concerning is that the "Space After Paragraph" number was also changing; one time it was 12pt, the next time I checked it was 50pt..? Is it possible that a corrupt font is causing this? Just a theory... Hmm I seem to encounter pushback on this a lot here. In Google search results the app is listed as "Affinity Photo – award-winning photo editing software". A photo editing app is not a layout design app—like Designer and Publisher, for example. And nobody is under any illusion that AP is an Illustrator alternative; it's a Photoshop alternative—that is, photo editing with some text, vector, and print features to make it useful/competitive. Why I feel like I'm in the minority on this I have no idea. 🤷♂️
-
orangefizz reacted to a post in a topic: Score marks for PDF print
-
thomaso reacted to a post in a topic: Why are pasted pixels not automatically rasterized?
-
Multiple users have explained how the pixel data (and vector data, and type data, etc etc) is part of what AP sees as the image object/layer. I'm not interested in the *object* here, I just want to edit the *pixels* directly, not the whole object. In Photoshop, if you had placed a Smart Object, yes, you would first have to render the object before you could directly edit its pixels. And this is exactly why Affinity dreamed up the Assistant: as soon as you click a filter, it does the rasterizing for you (a separate subject)—but CRUCIALLY, NOT when you use the marquee to copy/Cmd-J something WITHIN the image. Then suddenly it can only see the object. And this is particularly annoying when you're just pasting a copied image—in other words, not placing it—for quick editing. I cannot be the only person seeing this.
-
Not all in one document necessarily but repeatedly when comping—pasting images from other sources. Weird! When I open images and use the marquee to select an area to copy or Cmd-J, it works as expected...it sees pixels. But if I drag an image onto the canvas it's seen as a different object, same when I paste an image from the clipboard. (I also swear the new beta update is working differently than it was yesterday but maybe that's just my brain) Also surprising; evidently the decision was made to treat one case as pixels and the other as an image object. My issue here I guess is that pasting some random jpeg from the clipboard should not be considered placing. If I want something placed—for non-destructive editing—I'll use the place option. Good info tx
-
I can right-click and rasterize also, it's just the necessary added step (as with many added steps in AP). When you're dealing with dozens and dozens of images in a session, that tends to slow things down. Guess I'll post a feature request for a prefs option that automatically rasterizes pasted/dragged images and leaves placed images un-rasterized. Thanks all.