Mark Daniel

As it happens the TOC in the tutorial uses only one style which in that document are chapter headings but you can tick as many styles to include as you like and they can appear anywhere in the document. About 5 mins in to the tutorial it shows all the text styles generated for the TOC in the right hand Text styles panel. This part of the tutorial could certainly be expanded upon but if you create a TOC and start editing these styles you will see you can apply all the formatting you have shown above. The styles are hierarchical so you can affect the whole TOC, entries for a particular source style and numbers all together or separately.

When you have multiple spreads the pasteboard of one goes down to the pasteboard of the next and you can drag things up and down to move them from spread to spread but the answer to your question is no, the pasteboards doesn't extend beyond the top and bottom of the whole document and aren't shared between spreads.

You should be able to change the UI language in Preferences -> General -> Language. Italian is definitely included. Your choice of language would not have been carried over from the beta to the retail version so you'll have to select it again.

There are a few view options that affect this * If you have Preview mode on (View -> Preview Mode) then nothing will show in the bleed area. * If you have Clip to Canvas Off (View -> View Mode -> Clip to Canvas) and Show Bleed On (View -> Show Bleed) things will show right out into the pasteboard but a grey line will show where the bleed box is * If you have Clip to Canvas On then Show Bleed will toggle whether items that go off the edge are shown are clipped at the Trim Box (page) edge or the Bleed Box edge.

I don't think there is anything in your screen shot you can't do with Publisher. There is a tutorial here that should get you started.

In Preferences -> User Interface There is an option for 'Monochromatic iconography' which will make all the icons greyscale and less distracting for you.

You should just need to double click on the image, but if it's inside a picture frame you may need to double click twice. Once to enter the picture frame and once to start the edit. The picture should open in a new document tab.

I think in this case the afphoto file has been embedded as a document which allows it to be treated as a simply like an image. To edit the original with all the layers first double click on it then switch to the Photo persona.

As you might imagine, this isn't the most common of cases so there is no direct support for it in Publisher at the moment. Publisher does support horizontal and vertical facing page stacks but not in the same document. As it stands I would recommend not using facing pages but doing a single page document with manually resized spreads and masters. You can have spreads and masters that are different sizes in the same document. You can even free transform the masters to rotate them on the spread. You can also rotate the view to help with working on spreads with different orientations. Alternatively you might consider laying out all your pages in the conventional orientation in one document then placing each page as a rotated embedded images in the crazy layout version.

See @Patrick Connor's post. He has a few tips on how to get it working. The key thing is to have installed and run the latest versions (1.7.1) of the other two apps.

If your files have become associated with the wrong app then right click on any afphoto file in File Explorer, select 'Open With' then 'Chose another app'. Select Affinity Photo and tick 'Always use this app to open .afphoto files'. Then hit OK. This will make your afphoto files open with photo again in future.

You need to have installed and run the 1.7.1 Windows versions of Photo and Designer. Have you updated to the latest versions?

Thank you for quickly reporting the file issues highlighted by the changes for Linked and Embedded resources and bearing with us while we ironed those out. We are pleased to announce Build 337 which fixes the following issues in Builds 330 & 326 which were withdrawn. [337] - After modifying an embedded file you could no longer save the document - After replacing a linked resource the document could become corrupted and could not be re opened - Making multiple resources linked in the Resource manager could crash the application - The application could fail to save to a folder linked to OneDrive [330] - Converting an Embedded resource to Linked could delete the original resource - Replacing Image on a placed PDF could leave Resource Manager in an inconsistent state - Crash copying and pasting embedded document resources Status: Public Beta Purpose: Stability and General Testing Requirements: 64 Bit Win 7 SP1 / Win 8.1 / Win 10 (>=1607) We are pleased to announce Affinity Publisher build 337 is now available as a manual download from the link above. To be notified when there is a new beta please press follow on this announcement thread As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the product, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread. Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. Many thanks for your continued feedback. --- Fixes and Improvements A Note about Linked Images Backing data and hi-res previews are now discarded for linked images when the containing document is saved, resulting in a drop in Publication file size. Please note that unfortunately this will not apply for linked images in existing documents, they will have to be replaced in order to see an effect. When a document with linked images is opened you may now momentarily see a low-res preview before the full image is loaded and 'pops in'. This is expected behaviour. Other Fixes Menus / Studio (Win) Docking Pinning Panel to the left/right causes crash on next run up Deleting global colours could cause crash (Mac) OS accented colour set to Graphite now works correctly for font controls etc Fixes for Expression Parser Tools Fixed selection of Picture Frames from Masters Vector cropped object in Picture Frame now scales correctly Text / Tables Fixed noticeable text lag under some circumstances with Character Panel visible Fixed auto-correct crash e.g. typing (a) (MacOS) Ctrl+Alt+Tab in a table inserts a tab and switches document Prevented deletion of entire cell range with non contiguous selection On converting a shape to a text frame the context toolbar now shows the correct text tools Fix for Find / Replace All when found ranges were adjacent Resources Improved locating missing resources on file load Fix for Resource Manager incorrectly reporting resources as modified under some circumstances DocX improvements - fixes for lists, colours and paragraph run properties --- Earlier Release Notes Beta 312

Thank you for quickly reporting the file issues highlighted by the changes for Linked and Embedded resources and bearing with us while we ironed those out. We are pleased to announce Build 337 which fixes the following issues in Builds 330 & 326 which were withdrawn. [337] - After modifying an embedded file you could no longer save the document - After replacing a linked resource the document could become corrupted and could not be re opened. - Making multiple resources linked in the Resource manager could crash the application - The application could fail to save to folder linked to OneDrive [330] - Converting an Embedded resource to Linked could delete the original resource - Replacing Image on a placed PDF could leave Resource Manager in an inconsistent state - Crash copying and pasting embedded document resources Status: Public Beta Purpose: Stability and General Testing Requirements: Mac OS 10.9 or above Hi, We are pleased to announce that Affinity Publisher build 337 is now available as a manual download from the link above. To be notified when there is a new beta please press follow on this announcement thread. As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the product, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread. Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. Many thanks for your continued feedback. --- Fixes and Improvements A Note about Linked Images Backing data and hi-res previews are now discarded for linked images when the containing document is saved, resulting in a drop in Publication file size. Please note that unfortunately this will not apply for linked images in existing documents, they will have to be replaced in order to see an effect. When a document with linked images is opened you may now momentarily see a low-res preview before the full image is loaded and 'pops in'. This is expected behaviour. Other Fixes Menus / Studio (Win) Docking Pinning Panel to the left/right causes crash on next run up Deleting global colours could cause crash (Mac) OS accented colour set to Graphite now works correctly for font controls etc Fixes for Expression Parser Tools Fixed selection of Picture Frames from Masters Vector cropped object in Picture Frame now scales correctly Text / Tables Fixed noticeable text lag under some circumstances with Character Panel visible Fixed auto-correct crash e.g. typing (a) (MacOS) Ctrl+Alt+Tab in a table inserts a tab and switches document Prevented deletion of entire cell range with non contiguous selection On converting a shape to a text frame the context toolbar now shows the correct text tools Fix for Find / Replace All when found ranges were adjacent Resources Improved locating missing resources on file load Fix for Resource Manager incorrectly reporting resources as modified under some circumstances DocX improvements - fixes for lists, colours and paragraph run properties --- Earlier Release Notes Beta 312

I was hoping you might draw the correct result for me but the most important part of my question is where should the tree go?