Jump to content
You must now use your email address to sign in [click for more info] ×

Publisher/Studio Link: Photo Personna Crop Tool Not Working


Recommended Posts

13 minutes ago, MCFC_4Heatons said:

When in Publisher and using Studio Link, the crop tool in Photo Personna does not work as expected or as it does in Affinity Photo

This is kind of a continuation from this discussioin where I made a small error in one statement:

Correction of my earlier comment:

  • You always have the vector crop tool when:
       a. You have a document with Pages or Artboards: or
       b. You are in Designer, or the Publisher or Designer Personas of Publisher.
  • You have the raster crop tool when:
       a. You are in Photo, or the Photo Persona of Publisher, and you have a document with a Canvas (not one with Pages or Artboards).

This is intentional, I believe, because it doesn't make any sense to try to crop an actual page or artboard using a raster crop.

 

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

I think Walt is correct with his explanation.

My reasoning for it not being a bug; It's by design. In other words, Serif intentionally designed it work this way. Just because someone does not like the way it works, it does not behave as they think it should, does not automatically make it a bug.

Affinity Photo 2.4..; Affinity Designer 2.4..; Affinity Publisher 2.4..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

Also, an experiment you can try: 

1. In Designer, create a document with an Artboard. Then File > Edit in Photo. See what kind of Crop Tool you have. 

2. In Publisher, create a document with Pages (1 Master, 1 or more document pages). Then File > Edit in Photo. See what kind of Crop Tool you have. 

In both cases it should be the vector crop.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

  • Staff

I can see why this can be a bit confusing for the user: a file with an artboard created in Designer and passed to Photo disables the Crop Tool in Photo (greyed out) unless we delete the artboard(s) layer(s) which may not be always possible, whereas one created originally in Publisher makes the Crop Tool in Photo work as a vector crop tool (not sure how to revert/fix this one yet even for a Publisher document with a single page). Finally in Photo itself, the Crop Tool works as expected that is, as a raster crop tool (this on macOS, not checked if Windows is consistent with this behaviour yet). Three different behaviours for the same Tool in the same program (Photo), depending on what program the file was originally created in.

I'm not considering instances where users may receive or start a doc in one of the apps, end up changing/editing it in another app saving it there as a new file (with the "new" default extension of the second app) to later forget or get confused (in case of a received file) why the tool isn't working as it should/as they expect there.
I will raise this with the dev team but I'm afraid it is by design.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.