Gelphyn

Here is hoping that the A Team will beat the UK Energy Suppliers to the 'dosh' by releasing Publisher for iOS PDQ. Seriously my money WILL be waiting for the magic moment 😎

+ 1 for me please, advise reference the cost and I will pay now. It would also be great to hear an update on the most likely delivery date. Best wishes.

It would have been useful to learn if I had been doing things incorrectly, however as the workaround did just that it is water under the bridge. I have not found any problems with AfPub since the Full Release. Might help your case if you say what Version of Publisher you are using?

Hi Gabe I ditched having a Text Frame on the Master Page of the Template used for most of my PDFs and have not got around to reinstating at this time. It seems that the recent updates have resolved the problems experienced, in that I have produced several multi page documents without any Hyperlink problems. One incident did occur but that was after I had made several major changes to one document that required the 'insertion' of an additional Hyperlink, it is accepted that the changes were unusual an so 'bother' was expected. My MO is to Number each Hyperlink to maintain logical order throughout the document, so making an insertion required the remaining Hyperlinks to be renumbered. A few Hyperlinks adjacent to the one inserted refused to be reassigned their New Page Number and these were selected and replaced. However two Hyperlinks dully renumbered both with 'my' Hyperlink Number and the correct system Page Number failed to navigate any Page. This was traced to the fact that the selected Link Area, the whole of a Line on the Contents Page, had morphed into becoming two Highlighted/Selected Lines. Not much chance of any system being able to decide which route to take? Deleting these Hyperlinks and starting over resolved the situation. The decision purchase Affinity Publisher was made very early in my experience with the Beta Version, really looking forward to downloading the Full Release in a couple of days time. Brilliant job and Kudos to the Afpub Team. Very best wishes, Stan

Thanks for your reply. Your workaround is useful. Prior to the update to 337 the arrangement in place worked satisfactorily, and I hope the situation can be corrected. Cheers.

I have today, 25 May 2019, updated to 337. I opened an already well used Document that I use as a Template. This is similar to the attached Afbub File, the Links within this document all function as expected. When I attempted to add additional Hyperlinks: View > Studio > Hyperlinks Selected the Link [Text in this case] In the Pop Up this was assigned a Page Number The Selected Link displayed in Blue and was Underlined The Hyperlinks Panel did not display this addition. After many attempts a fresh start was made via: Text > Interactive > Insert Hyperlink Then the actions were performed as above with the same outcome, again tried many times. Then a similar New Document was created, using 337, and all the Hyperlinks performed satisfactorily. However after: Saving this Document Closing and reopening it Saving As - Giving it a New FileName As before the actions were performed as above with the same outcome, and again tried many times. The outcome still fails to accept New Hyperlinks. Due to 'brain fade' spirits were temporarily lifted when a Nw Link was added, unfortunately the said link was inadvertently added to the Master Page and not a solution. Thanks for all the great work you guys and gals are doing. Geez - Hyperlink Problem I.afpub

Having updated to AfPub 1.7.0.293 the difference in the Blue Colour persists. Attached are two AfPub Files, one being effectively my 'template' that presents preferred colours and the other opened as a New File. Please note that the Original File, from which the 'template' was derived, was created quite some time ago but I have no record of the Build/Release Number. Thanks in advance for any help you can offer. Geez Colour Settings.afpub New File Colour Settings.afpub

Very interesting video thank you. I am accessing Settings for Colour Change via the Colour Panel, at the top of the Righthand Studio, shown in my ScreenShots. My kit consists of Mac Pro 5.1 with modified Graphics Card and runs High Sierra 10.13.6. It is possible that older equipment may present some differences but I have no way to verify what those differences might be. I have not been able to find any other Colour Picker except via:  > Affinity Publisher Beta > View > Apple Colour Picker and assume that this is where alternative Colour Pickers would reside. The appearance of your display, as shown in the video has many differences compared to the display available to me. Are you using AfPub 1.7.2.292 running on a Mac? If you are using the same hardware + software please can you direct me how to navigate to the opening shot in your video? What I am saying about using the Colour Picker, i.e., seemingly the ONLY Colour Picker available to me, is that all the settings are the same on both of the Files being discussed. You can observe that the Slider Settings and choice of RBG are identical but that the New File Blue is not the same as the Original File Blue. This is the problem. If you activate the Menu Icon Dropdown, top and right most in the ScreenShots, the settings there are identical on both Files. Similarly activate the Options [Up/Down Arrow Heads] on the RGB Field and those settings are also identical. As far as I am aware at this point there are nil further options for these Settings.

Thanks for your input Mac_heibu. The settings for both 'seem' to be identical? I have not been able to access the same result on any New File by altering any of the settings, they all 'seem' to be affected, so I came up with workarounds.

Is this a Bug, something I am doing incorrectly or a feature that does not exist? The attached Pages document has been used to preserve the displayed Colours. In AfPub dependent on using either the Original File [brighter colour Blue] or a freshly opened New File [dull coloured Blue] the colours are dictated by the File chosen. I cannot find a way to migrate the Colour Settings from one File to another File, so my workaround has been to create a 'Standard Colour File', from the original File mentioned, and use it as a Template. I am just looking to have 'my' chosen colours available on Files being created. An alternative workaround would be to add the desired Colours to the Apple Colour Picker and use that instead of the AfPub facility? AfPub 1.7.0.292 - COLOUR TEST.pages

I had similar problems and needed to move away from Adobe Acrobat. I tried several possible alternatives none of which completely matched the abilities of AA. Eventually I settled on this: PDFpenPro Smile offer a Free Trial period so there is nothing to lose by giving it a whirl? Best regards, G

Hi. Regarding 'Using Shortcut combo Keys' Did you mean to say ⌘ +/⌘ - , rather than CTRL +/CTRL -? This is working for me as expected now.

Thanks for the Link Dybkjær. Your example is very good. I hope that this can be resolved also. Best wishes, G

I am upgrading my Mac, that is currently limited to running up to El Capitan, in the interim period it would be preferable if my current Affinity Applications [Designer; Photo; Publisher Beta:] remained operable on the existing Hardware. Does the Licence permit downloading and installing the Affinity Applications on the newer Hardware before they are removed from the older Hardware? I have no intention or desire to violate the Licence conditions and official input would be very welcome, thank you. Thanks for your time, best wishes, G

I have found a workaround [? solution] to the problem of Constraint Groups and the perimeter clipping that occurs. Although I still do not understand why apparently randomly some Groups result in becoming Constraint Groups whilst others, using similar Objects, remain simply as Groups. If a Constraint Group is 'Grouped' the latter displays as a simple Group, ungrouping the Constraint Group within the newly formed Group allows the latter to remain as a simple Group. Importantly the previously troublesome clipping does not occur. It would be nice to know if I am unwittingly creating a problem, if this behaviour is intentional or is a bug?