Pšenda

Why don't you set a much more suitable and acceptable keyboard shortcut?

Does saving the document (Ctrl + S) not work for you when you rotate the view?

The question is - what would it actually be good for, and if it would really be an advantage. If a different thickness could be set for each segment, then why not the color? Why not different line type (nothing, solid, brush, dotted)? Why not different Appearances? Why not different fx? Etc. Having the ability to define "all" line parameters for entire curves or individual segments could be quite a bit of user chaos. And would it really be so convenient and beneficial than to use some alternative solution in some specific cases? Perhaps it would be useful if two different lines/nodes could be linked, so that when the node of one line moves, the node of the second line also moves, so that the impression of a single curve composed of segments with different parameters would be created.

But even Affinity "can" read its native files stored in OneDrive!!! That's what you see when you view previews in Recent files, or when you open this file. All the time, which is probably the information you still completely miss, the problem is that the Affinity files located in OneDrive cannot read (display their thumbnails) the Open dialog (FileExplorer) from Microsoft. So until Microsoft adds this support to the OS and OneDrive, nobody will do anything about it. P.S. like Affinity, any browser that can display *.af files can read files from OneDrive - but not Microsoft's FileExplorer/Open dialog, although it can in other folders! File in OneDrive: Same file in local (not controlled OneDrive) data folder: So it's obvious - that it's a problem on Microsoft's side (not Serif or anyone else), because FileExplorer doesn't "show" previews for *.af files located/controlled by OneDrive, even though it can show them!

Maybe I don't understand the request, but this is exactly how the Contour Tool works - the contour adapts to the object even after editing it.

Since it looks like you are opening work files directly on OneDrive, keep in mind that Serif has repeatedly recommended here on the forum (always in connection with the problem of damaged and lost files) to work on local drives, and to the cloud saves only for backup or file sharing.

I think any argument is futile here. I don't know if it's a language problem or a problem with understanding the meaning of the operating system dialogs, but unfortunately some of the information mentioned here many times remains completely unanswered, so the discussion keeps going round and round.

Your text (your layer description) is black, the gray is only the description/explanation of the layer type, which anyway disappears after entering your name/description. This is duplicate information about the layer icon and its hint/tooltip. Loss of contrast is unfortunately a "trend" in Affinity applications.

It is obvious that you do not understand the content of this post - see, but try to read it again, or try to ask someone who would explain it to you.

But you may have noticed that the explorer whose services Open dialog uses offers other services that Recent dialog does not. Whether it is the display of document properties, different preview sizes, etc. So, apart from the fact - that this is not the right step, because properly applications "should" use OS services to the maximum extent possible, so a lot of users will be very disappointed with this proposal of yours. You may have also noticed that Affinity will display a preview of a file located in the OneDrive folder, but always at the cost of downloading it locally from the cloud. So if someone uses the "Free up space" method, they will be very disappointed with your solution.

Because it's part of the Affinity app? - so it would be quite strange if the application couldn't read and display its own files. For the Open dialog, the standard dialog from the OS is used, in this case it is part of the Windows (Microsoft) operating system. So it is a matter of the OS (Microsoft) whether it understands the file format and therefore whether it provides their thumbnail. P.S. Although I don't have a problem with the file preview for locally located *.afsuite files, when opening from the OneDrive folder, the preview is not displayed - this function is not implemented in the OS (specifically in the OneDrive application), and it needs to be added/developed by Microsoft.

Set all Tools to single shortcut, for example "t"ools.

Any fx of the exported object? - for example an outer shadow?, outer glow?...

???

Thanks for the link - at least I "finally" know what the OP is talking about. So about exporting objects outside the document.

Select shape, Export, Selection Only or Selection Area

Export Persona, Layers Panel, Create Slice from selected layer, Export slice.

Unfortunately, the consequence of not respecting the rules of the forum is evident here, when duplicate threads with an identical topic are created unnecessarily, so that the information mentioned in another thread is then missing here.

It certainly does - if the Corner Tool is applied to a curve (for example, when a rectangle is converted to a curve), so this strange switch to the Node Tool don't occur.

It would suit me if, instead of this completely unusable list for me, Favourite items from the New Documents list or from my own templates were offered.

No. The correct procedure of course is that when you try to open this image, an Input box pops up with a message asking "The DPI value of the image is 0, which is incorrect. Please enter the correct value. DPI=?" But of course that means an "awful" lot of work, so we won't see it for about 5 years. So it's easiest to "fix" the value to 1 if the app is already doing this.

And why ask something that the app has been doing for a long time??? Already today, if you enter DPI=0, the application "invents" a value of 1. Therefore, if someone were to "requested" that the application reject this image (why not? it is indeed damaged - it contains a meaningless DPI value, but there is no problem opening it, and an incorrect value to fix), so the application should behave consistently, and the entry of 0 in the DPI value would have to refuse, not adjust to 1 (which the application does today).

??? Why do you think the application comes up with a wrong (probably incorrect) value when entering DPI=0? Simply 0 is nonsense, and the application must not work with it - the calculator also does not divide by zero!