Megnusin

Hi @Megnusin,
Many thanks for providing the sample document. Using your file, i've identified the issue relates to multi-level nested group structures when using the 'Convert to Curves' function. I've re-produced the issue from a new document using a basic curve nested within a group that's nested within a group. Converting to curves on the top level group causes the object to delete itself and in some cases (such as your sample doc) this cannot be undone via history and can trigger an app crash when undoing.
Upon review this appears to be a known issue currently logged with the developers, I've updated the existing issue and bumped it with your report.

On desktop, no.
on iPad, yes.
there is no logic behind what pixel based functionality is available in designer (vs. photo).
It is so crippled that I would be glad if Affinity removes all pixel based UI completely to avoid all this uncertainty what is available (on desktop or iPad, in V1 or V2)

The issue is with the size of the various executable files inside the app package and not with the overall size of the app container. I believe the total size of Affinity's executables is greater than Photoshop.
Somebody explained it to me once that it's like an exponential curve - an app might be only 10% larger than another but be much slower to launch.
Fortunately, Apple has made app launching faster with the M4 series. I encountered the slow launch today but only had a moment to realize that that it was slower than normal before the app finished loaded. I know upgrading isn't a solution for everybody but this will be a less of an issue with time.

Bump. Constantly resetting values for corner radii after scaling the object. Current workflow is:
- duplicate object
- bake corners on duplicate
- scale original and duplicate
- match corner radii on the original to the duplicate
- delete duplicate.
Painful.

I don't think it's broken or a bug "Shape Corners" refers to Shapes using one of the Shape Tools. Once you use the Corner Tool on a Shape it is no longer a Shape, it is now a Curve. That option does not apply to curves
What you probably should be advocating for is a feature request for the Corner Tool to have an option for the corners to "scale with object" and not having to bake them to get that effect (But I believe that may have already been requested)

Also, your video may be flawed. For the Shape Override options to have any effect you have to switch on Scale Override, your video is unclear if you have done that as I would expect the scale override button to be a lot darker when on, as it is on Windows. But I guess that could be due to differences on a Mac versus Windows or a contrast setting somewhere. (I don't have a Mac to test this but someone with a Mac may be able to clarify it, one way or the other)
If the above is unclear, please refer to the Help file to understand how that option works to see if you have actually activated it 
 

To see this still not implemented 7 years later when it is a feature of other programs like Figma is so frustrating. Pleeeease add it 🙏! I have a series of character designs that i want to make model sheets for. This involves scaling the characters down to different sizes on different pages, but still being able to tweak them when/if needed as they're still a work in progress. Right now this is a nightmare without proportional scaled corners 😭

Infinite scalability and non-destructive operations are core principles. It should not be necessary to bake rounded (or shaped) corners to be able to scale them proportionately with an object. Non-destructive rounding is half the point of having a corner tool.
Please fix the broken "shape corners -> scale with object" option Add a "lock" option in the corner tool to opt individual rounded/shaped corners out of scaling

In the latest version of AD there's this Scale Override option in the Transform panel: https://affinity.help/designer2/en-US.lproj/index.html?page=pages/ObjectControl/transform.html&title=Transforming objects
In the dropdown there's an option called Shape Corners which I think should resize the corner radius proportionally but it's not. So I'm not really sure what this option does but it's really absurd that we don't have an option to proportionally resize corner radius values. 

Guys, honestly, this shouldn't be an issue still in 2020.
 

Agreed with this thread. We need the equivalent of Stroke "Scale with Object" for Corners. Ran into the problem today.

This is absurd. The goal of cropping is to remove non necessary areas of the image to work with the remaining. What use is there if the cropped images selection area is the original image's one? What's the use of cropping if I can't set measures to the cropped image because the measures applies to the original image?
And yes, i can convert it to image frame, but that result in a image frame containing the cropped image with the same issues, and being even harder to manage size.
It is an useless nuisance, and just now I have a catalog with already thousands of cropped images that I cant resize properly because the cropping does not work. I can't conceive a single other software with image cropping that make this, and I've used a lot of them.
You know it is wrong when even the f$%&nkg Word and Powerpoint does it right and your app NOT.

Well, I have to agree that this is the single most useless change I have ever had the misfortune to see implemented.
Why on earth would anyone want to see where the bounds of the area they have already cropped were?
OK, I can use "." to cycle through the what I want to see ... the borders of the actual cropped area, fine ... but is there a way to set things so that the actual cropped area is the default selection?
If there is, it isn't obvious ... and if there isn't it should be made the default selection!
Phil

Is there a way to revert selection/move behavior to the way i was in 2.5?
The inability to make selection permanent, having to toggle through the cycle selection menu for every single object movement makes this software basically unusable.  
Affinity, PLEASE revert this. 

No, this isn't possible at the moment unless you go to the trouble of making a gradient texture to use in a vector brush... We have much grander plans when it comes to gradients and I'm not prepared to mention what it is right now because it won't be as much fun when we do the big reveal in the future if you already knew what was coming! ;)

Hallo guys! I have the exact same problem (the cursor stuck to the View tool, the hand), and I accidentally hit the space bar and it returned the cursor back to the black arrow tool. I hope this works for you too. 

Interesting theory. However if that was the case, it would affect all apps and any text I write; and relaunching Designer wouldn’t by itself un-stuck it. So I’m doubtful.

Worked for me, amazing, thank you so much!!!

Are there any plans to implement the inverse of this?

Sorry, I don't use Designer so don't know. I used Photo

With only the white letters and background visible, do Layer/ Merge Visible
Then use a copy of the white letters as a mask on the new pixel layer and rasterise that

White text in blend mode 'Negate' -> grouped with HSL adjustment:

Thanks for the tip @loukash🤙 I ended up just using the crop/rotate/pan/tilt feature on my iPhone 🤷‍♂️ Way more intuitive🫢

@Megnusin, you're two years too late.  
Pixel persona Layer → New Live Filter Layer Voilà. You're welcome.

What utter nonsense.
Fix you apps Affinity.

This has been a problem for SO many years and I feel like Affinity are the only apps that are launching this slowly. It effected v1 and now v2 of the apps. It might not seem like a huge problem but it repetitively makes me hesitant to launch an Affinity app unless I need to. And if I'm in a hurry, it makes me want to use something else.