MikeSB

Hey Mike, that is really amazing!!! Thank you so much! Michael (just tested it - great )

Hi there Here comes the test document for inspection. Perhaps it is only a problem with the Windows version of AFP? Thanks Michaelantipasti-hyphenation-test.afpub

Hi, when automatic hyphenation is enabled in a format, that contains tabs, there is an error, when hyphenation is applied. Have a look at topic 2. Michael

Hi Jon, I uploaded a ZIP. The Book-file is also included. Michael

Hello, 1. creating a book, containing 26 chapters, each of 2 to 5 pages. 2. Rearrangin the chapters. 3. Selecting all chapters by Ctrl+A. 4. Starting to synhronize: for a second or two the progress bar is shown, then Publisher crashes. The error is reproducible. And no chance to complete the book as intended by me. Updating the page numbers works. Just to let you know Michael

Hello Chris B thank you for your support. This morning I tried to reproduce the described behaviour in my post. And now it worked! So we can delete my Topic 4. and close the thread :). Michael

Hi, what I did: 1. Opening a RAW-File (CR3) 2. Not interesting in the pic, so click CTRL-W on Windows to close it. 3. Popup shows "Actual file is still developing" (translated from German version) 4. No more response of Photo Michael

First of all: The V2 apps are well done! 😀 Unfortunately, a feature I once asked for is still not included. I am publishing a book with several chapters. Each chapter starts with a number followed by the page number. Example: Chapter1 1-1 1-2 1-3 ... 1-n Chapter2 2-1 2-2 2-3 ... 2-n In the index you will then find: Something1 2-65 Something2 6-15 Something3 1-21 Since I only update and publish individual chapters, only the new pages have to be added and the index has to be recreated. This provides additional index entries for the added chapter, all other index references remain the same. Since I have used exactly this method in InDesign 6 so far, it is important for me that this is also possible in Publisher. (Or have I overlooked something?) Attached is a screenshot of how this is set in InDesign. Thanks for a reply Michael

Sry - now I cannot assist you. "Unfortunately" Photo crashes and does no longer hanging. So I miss the chance to generate a dmp-file. As I wrote earlier - I will do the clipping/rotation first then apply any other adjustment. And ... it is only the rotation which causes the crash. Thanks again for your patience! Michael

uploaded a ZIP-file.

Did it in English. No report found in [...]\reports but in folder [...]\Backtrace. There is alo a dmp file. Would you like to give me a Dropbox-link - so I can send you all files (including the json-ones)? Michael

Unfortuanetly there is no crash report. The last one was recorded on March. There is also an integrated graphics card (Intel UHD 630). For rendering I have selected in Affinity Photo the NVIDIA-card. For now I have a work around: First clip and rotate, then apply any adjustments. That works for me. Michael

Thanks, too. And - yes - these are the steps I am also doing in the same order. As cropping without rotation works perfectly the crash occurs when I start to rotate while cropping. The .NET-Repair-Tool applied shows no difference. One more observation, I found these minutes: Doing the same steps to a JPEG works. So it seems - IMHO - to be a hint, that it's something which happens processing TIFF-files. My workflow is mostly: Cpature One -> Export a TIFF to Photo and work on it there. Thanks for your patience and have a nice day. Michael

Hi, I uploaded a file. The Third Party Software I am using is just Capture One, without any problems until today. Michael

Hello Dan C thank you for your quick reply! Here are some ew infos: Changing to WARP lets Photo crash also. A new error msg is produced by .NET runtime (not sure if it is caused bei the WARP engine). See below for the stack trace. It happens with different TIFF files. I am using the lastest NVIDIA drivers, installed by NVIDIA updater. BUT: Cropping and rotating the mere background image before adjustments are applied does work! The error occurs after applying adjustments. Here is the record in the EventLog: Anwendung: Photo.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: System.AccessViolationException bei Serif.Interop.Persona.UserInterface.DocumentRenderControl.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei System.Windows.Interop.HwndHost.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) bei System.Windows.Application.RunDispatcher(System.Object) bei System.Windows.Application.RunInternal(System.Windows.Window) bei Photo.Application.Main(System.String[]) That's all for the moment Michael