Jump to content

Hangman

Members
  • Content count

    100
  • Joined

  • Last visited

About Hangman

  • Rank
    Advanced Member

Recent Profile Visitors

428 profile views
  1. I guess it could be a system issue perhaps rather than an AP problem, but I don't know. It's super quick for me... :-) Page Scroll in Affinity Publisher.mov
  2. See what you mean, though it just looks like an issue with the page borders/boundaries not scaling... Screen_Recording_2018-10-18_at_16_54_19.mov
  3. Hi Chris, I've just tried Crtl Running APub and cleared 'All' user data, but I am still experiencing the same issue. Machine specs are in my signature in case this is specific to Mojave. Cheers
  4. Hi Old Bruce, Strangely after a re-boot of A-Pub, the 2nd problem has now gone away for both the spacing and justification settings, i.e. the arrow keys do now work to change values although you do have to continually click the arrow keys to increase/decrease those values, unlike with character size where you can just keep the arrow keys held down and it will increase/decrease without the need for constant clicks. I've uploaded a video of the first problem as I'm experiencing it...
  5. I'm currently unable to 'select' any of the justification sliders under the paragraph panel. Clicking the drop down arrows shows the respective sliders but clicking on any of them hides the slider so you are unable to actually select and adjust the slider values. Highlighting any value and attempting to use the arrow keys to increase/decrease values only allows increments of one before becoming deselcted. I'm unsure if values here and under the spacing panel should function in a similar fashion to clicking in the character size window where using the arrow keys increases/decreases the font size or the transform window where the arrow keys increase decrease the x, y co-ordinates/w, h values. APub 1.7.0.145 Beta is starting to feel more rounded though still quite a few odd UI issues which I'm sure will be ironed out in future beta's Screen Recording 2018-10-14 at 00.34.43.mov
  6. Sadly not currently it would seem. If you add Pantone colours to a file in AD then it does add these colours to the AD document palette, however it labels them Global Colour 1, Global Colour 2 and so on rather than by the Pantone name which isn't very helpful. Saving the file out to a .eps and placing the .eps in APub doesn't currently add anything to the APub document colour palette. I'd like to see the colours added to the document palette using the correct name, otherwise it is a little unhelpful and likewise as you say, adding an .eps file that to APub should add the colours used to the document palette and name them correctly whether CMYK or Pantone. Not sure if this has been added to the list of feature requests?
  7. This seems to be a long standing bug relating to Exif data when placing jpg's created in Photoshop into any of the Affinity apps and is also mentioned in this thread too. The issue doesn't seem to manifest itself when the jpg's are created using Affinity Photo...
  8. Hi Pauls, Crash report attached... see signature for system specs. Affinity Publisher Crash Report.pdf
  9. This question is really for Matt or Chris or the Moderation Team... Is there any practical reason why master page items in the layers panel for individual pages are global rather than local? I haven't yet seen the logic of this. It would be great if you can create your master page with all items used throughout the document but have the ability to selectively uncheck individual items on a page by page basis without it impacting all the other pages in the file, e.g. page numbers or certain graphics which you may not want to appear on specific pages, without the need to use a separate master page. It just seems very logical to me because you have access to each master page item from each individual page, what is the benefit of these items being global on individual pages, i.e. why does unchecking the page number on an individual page hide it on all other pages as well, is this by design and if so what is the logic?
  10. I can replicate this on OSX. Simply create a table and add content to a cell. If the cursor is after the conent within a cell cmd-delete correctly deletes the entire cell content, however if the cursor is before the cell conent or the cell has no content then using cmd-delete crashes A-Pub.
  11. It appears that after creating a new Document palette in APub it can't be deleted. You get the dialogue asking if you want to delete the palette, but accepting it doesn't actually delete it. It only seems to affect Document Palettes, System and Application palettes can be deleted as expected, assuming this is a bug?
  12. Hi dominik, That was exactly my point, you end up 'having' to use multiple masters which just seems a little wasteful because each page has the elements contained on the master page in its layers panel so my suggestion was why not make these elements local rather than global at page level so that you could simply use a single master and say for example uncheck the page number or a graphic if it wasn't required for that particular page by unchecking it for that page only. At the moment if you uncheck a page number in the 'master elements' layers for an individual page it hides the page numbers on all the pages. I'm not really sure I follow the logic of that. If hiding an element on an individual page only affected that page then it would be quite a powerful option...
  13. You can select from a variety of colour palette formats, e.g. the colour sliders can display CMYK, RGB, RGB HEX, HSL, LAB and Greyscale, the colour wheel and boxes options use HSL, regardless of your document colour format... and depending on which you have selected, this determines how a colour added to a swatch will appear in list view so for example if you select the CMYK sliders as your colour palette option then colours added to a swatch library will appear in CMYK, if you have the HSL sliders selected, added colours appear as HSL in list view and so on... But I agree, I think the colour palettes need a big overhaul as they are less than intuitive and there are so many things that could be improved... There is an option to make a colour palette from the colours used within the document itself, so this sort of gives you what you want, though after the event rather than dragging colours from say the pantone swatches to their own colour palette which you might want to do if following certain brand guidelines. But if you want to delete colours from a colour palette you have to laboriously do that one by one and accept each... there ideally needs to be the option to ctrl click multiple colours or a delete all colours option. Having said that for some weird reason whether you have CMYK or Pantone colours within a document using the create palette from document option displays the colours in the newly created palette using LAB so no logic there... Clearly if you've used say specific Pantone colours and you then use the create palette from document you want the colours to be shown as their respective Pantone colours in your new palette otherwise it makes no sense. There also seems to be a bug in APub which means that you can't delete colour palettes once created. Anyway, I'm hoping for a big overhaul of colour management when the V2's start appearing, though it would be nice to see some improvements before then...
  14. Agree, it would be 'useful' if the master page items that appear in the layers panel for each page/spread were local rather than global so that when an item is unchecked, e.g. a page number from a particular page is unchecked in the layers panel for that page it only affects than one page. At the moment unchecking a master item from the layers panel of individual pages hides it from all pages using that master and dragging the item out of the master items folder doesn't change this behaviour. So for example you may have your master page set up to include say page numbers on each page and a graphic of some sort, say a horizontal line above the page number which may suit the overall design, however if you then have a full page photo on a particular page where you don't want either the page number and graphic to appear it would be nice if you could simply uncheck those items from that pages master items without it affecting all the other pages... At the moment the only practical way round this is to use a seperate master page without said page number and graphic and apply that master to the page in question. Seems a bit long winded and uneccessary. Is there any practical reason why master page items in the layers panel for individual pages couldn't be local rather than global, so a single master could be used and master items selectively hidden if required on a page by page basis? I'm not sure I see the benefit of these being global in each pages layers panel...
×