stefano.cecere

i've been working on a several hundred pages project (no, it wasn't a book, but a complex project with dozens of different chapters) in Publisher, and i really missed the possibility to name pages and sections. woudl also be nice to see sections in the page list

absolutely. WepB is today a standard in many projects.

thank you @MikeTO indeed i checked other macos Ventura apps and the arrows are now filled triangles, very like as in the keyboard...

the menu commands work, but the shorcuts no. i struggled hours, then discovered this: the shorcut is Cmd+PageUp / PageDown. but the menu shows a simple arrow, and i think it's the cursor arrow. if i set the shorcut to the keyaboard arrow, i get a full triangle.. see the screenshot: the UP is the default "Page Up" key (that new macbook pro don't have, btw) the DOWN is the "Arrow down" key. i think this think should be explained somewhere

absolutely not so "visible". we are talking about the size of an image: the first and second place where i look is in the transformer panel, and then contextual menu Transform NB: i use computer and multimedia software since 1989.. i never struggled so much with software UI/UX as with Affinity suite.. I am sorry to say it.

this information / command is quite hidden.

i remem i remember the "old" roadmap... quite very detailed... too much i know, people love to complain.. anyway.. new betas should be released in the 2.x cycle.. so maybe we'll be half-way

now that v2 is here, with many new features, but many pros still needs some to really be comfortable with the Suite... could we please have a minimal roadmap on what you are working on? even something really generic like this Trello roadmap (for the Obsidian app). we know, and you know, that we don't have many other options today.. or Adobe, or Affinity, unless we want to use separate apps for specific works..).. we want to support you, but we need to be kept engagend, and know where you are going! for example: if you aren't goind to support ePub or external texts in Publish.. we aren't goind to use it for next books. if you aren't supporting RTL before 3/5 years, we accept it and use something else from today. if you plan automation in 2 years, we could use a temporary solution... thank you!

hi to the complete WebP export in v2.0

for me, just for the complete WebP export, it is worth to upgrade to v2.0

i've abandoned Affinity Photo for PixelmatorPro, just for WebP export feature. it's sad because it's an easy feature, now a standard for all current and next web dev (images are 50% smaller than jpg and png!) and it wouldn't cost too much to say: sure it'll come with 1.11 be patient!

one day on another some DTP will have these features.. and i'll use it

dear Serif i don't know your problem with WebP, but i just moved Affinity Photo in the archive and started using Pixelmator Pro, please don't let me get used to it ;)

same. i got angry and solved by Pixelmator Pro. the manual said nothing so searched the forum because i couldnpt think to be the only one in the world with this huge problem.. which is being discussed since 2016! NB: i have the Affinity suite, but too often i think there are still some big UX problems ciao

hi Mark.. we already can write complex book with Markdown -> export perfect PDF with Latex, without using big apps like Publisher see for example my workflow: https://github.com/StefanoCecere/markdown_pandoc_book_template