Jump to content

iaing

Members
  • Content count

    125
  • Joined

  • Last visited

About iaing

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    UK

Recent Profile Visitors

452 profile views
  1. +1 - glad I searched forum before posting the same thing
  2. Have a look in your Character panel - as well as Paragraph leading, Affinity apps have Character Leading Override: Leading Override—applies local override to selected text to increase the leading with regard to the paragraph’s leading you might have accidentally set that really low?
  3. Hi Gabe - try this: 1. Create a new 'device' document - your artboard will automatically be at X:0 Y:0 2. Make sure you have snapping and force pixel-alignment enabled 3. Now option-drag a copy of the artboard, keeping option held down as you drag, release the artboard - it WILL end on a sub-pixel, because option-dragging overrides all snapping 4. Delete that artboard and again option-drag your first one, this time release option key before releasing the artboard - this time it will snap to whole pixels. By the way, can we rename 'artboards' as 'dartboards' - would save me correcting auto-correct
  4. Are you option-dragging to create your duplicate? That's what I would do, and it took me ages to work this out: Affinity makes option-dragging override constraints, so it allows you to place the artboard on a sub-pixel, causing the extra pixel at export. They added command-dragging as a duplicate that honours snapping. Personally I think it was a weird decision, to change the default behaviour of the most common shortcut of all graphics apps on the Mac ever! There is a solution though, without having to remember to use command instead of option: start option-dragging as normal, but then release the option key without releasing the object , you'll still duplicate and snapping comes back on.
  5. I just tested this and didn't even need to attempt pasting, just 'select all' in a text frame and 'copy' caused instant crash. The was from a previous Beta version document though, so I tried a) a fresh document > copied text from indesign > paste > Select all > copied > instant crash. b) paste from Indesign without formatting - Select all > copied > OK, no crash. Did the same test with text copied from Word, same result.
  6. Just tried again with a fresh document and overflowing text warning works fine, might just have been I was testing a document from earlier beta build.
  7. Yes that's what I meant, and I did say 'I remembered it happening previously in beta' - @thomaso is right though - just tested and it is only coming up if the overflowing text is from a linked text frame - a single text frame that's overflowing doesn't produce the warning. True, but I'm thinking more of times when the original isn't available because someone hasn't sent it to me rather than that I've moved the resource myself - in that instance I'd often keep working on the job, knowing that someone's been notified to send it to me. However being a goldfish, I'm likely to have forgotten that a few hours later and go ahead and export a pdf with a font missing. This is particularly an issue until pdf passthrough is implemented. I could just open Font Manager & Resource Manager and check, which makes the warning box nice, rather than essential An alternative to the warning dialog would be Sketch's approach with a persistent flag in the toolbar That one's for plugins, but it does the same for fonts (different colour)
  8. In a table cell, the tab key rightly moves you to the next cell. ctrl + tab key is the default Mac shortcut to cycle through your document tabs, which also works as expected. ctrl + alt + Tab key inserts a text tab in your current cell, but also cycles through your document tabs. I think it's a bug that this shortcut is cycling document tabs - applies to all suite betas.
  9. iaing

    Font auto activation??

    Same issue here in Designer and still in the Beta too, also in Publisher Beta. It seems to work OK for just one font, but if there's a few fonts to auto-activate Designer doesn't recognise them all - they are all correctly activated by Rightfont but Designer just shows a default font. Closing and re-opening the file fixes the display. It's only Affinity apps that have this problem, every other app I have works fine with auto-activation. By the way @postmadesign I've been using Rightfont for a few months now and love it - I'd been battling away with Font Xplorer for years, Rightfont's way better. And yes, I had this same issue while using Font Xplorer too.
  10. I'm sure that earlier in the Beta process there was a warning if you tried to export a pdf while you had overset text (might be wishful thinking, either way, it isn't there now ). A dialog alert would be good if you try to export and there's: 1. overset text 2. missing images 3. substituted fonts Also there's a visual marker on the text frame itself for overset text, it would also be good of there was a similar red dot on an image which is missing. I know preflight is in consideration for further down the line, but these major oops's could save some blushes for now!
  11. iaing

    ESC to deselect

    I agree with @>|< - Deselect means pixels - if you look in the Select menu, Deselect is near the top and has cmd-D as shortcut, further down the Select menu is Deselect Layers - this is what you're after - since Esc also works as a shortcut for Deselect (Pixels), maybe you could reassign Cmd-D to Deselect Layers? It might be helpful if the Deselect in Select menu was renamed Deselect Pixels to save this confusion.
  12. Hi Sean, agreed, seems to be sorted in 1.7.0.7 - thank you!
  13. I love the new pop-over for image size in latest Designer Beta - really hoping that makes its way across to Publisher too - especially love the 1:1 button
×