Jump to content
You must now use your email address to sign in [click for more info] ×

thomaso

Members
  • Posts

    11,201
  • Joined

  • Last visited

Everything posted by thomaso

  1. Yes, but these cropping marks always crop at paper size (= netto document page size). Means, the crop marks never tell if or where bleed is respected or added unwanted. The bleed area should be white if bleed is set to 0. Compare the expected bleed = 0 on page 1 towards pg 2 and 3 in these pdfs. Only the print to pdf version shows bleed = 0 for all pages. v408_2 inner bleed 1.pdf v408_2 inner bleed 2 with marks.pdf v408_2 inner bleed 3 - print - scale 90percent.pdf
  2. Thank you Old Bruce! – Hm, since the behavior of tabbing between fields is ... the same in macOS 10.11. and 10.14. ... but different on 2 macs with 10.12. I wonder even more what does influence the tabbing behavior difference between computers. Hopefully the Serif Affinity team can shed some light on this. In this screencast (10.12.6 macBookPro 8,2) the reverse (shift-)tabbing starts at 0:25 min. I can't see the icon get highlighted any more but, strange, between H and R is a break, i was looking for the highlight and had to tab twice for that step (in both directions). tabbing order in transform panel.mov
  3. So the printed content exceeds the red area? I see a red rectangle in macOS if the print object is larger than the paper format. It is a warning in case of a size issue. – For instance: To print an A4 document on A4 paper with bleed I must scale the print size to avoid the red rectangle (and maybe a cropped print):
  4. Hm? – I might misunderstand the topic but to me it appears that I only should not use the default application palettes but need to create my own swatches instead for use in CMYK workflow. Sample 1.7 PDF with black text in both 100 K and RGB: v408_2 text 100 K black.pdf
  5. I am not shure what you mean with "a cut out or part of an image". Can show a screenshot of what you get momentarily? Perhaps you might want to edit the wrapping shape different from its visible graphic? >> >>
  6. Cosmetic supplement: Since AfPublisher's retail version (v.408) the default palette "Colours" show its swatches in a new sort-by-colour order. Whereas in beta versions these swatches got sorted by Saturation first, now they are grouped by saturation and mixed with Hue in between. That way now for instance Reds and Yellows appear mixed. Is there a way for me to reset this sort-by-color order back to the "old style"? "Colours" sorted by color: Beta versus final release:
  7. The default color palettes "Greys" and "Colors" show different CMYK values, depending on the panel you look at. It appears with click on such a predefined swatch the Swatches panel value look more as wanted than synchronously shown in the Color panel. For instance, the default "Greys", named "Black xx%", are shown in swatches as CMYK 1-color Black only – whereas its value in color panel is shown as 4-color Black. Unfortunately not the expected value from the swatches panel gets exported but the unwanted and unexpected color panel value instead ! Black 50% : – swatches p: 0 0 0 50 – color panel: 55 42 42 9 Yellow HSL 42 90 50: – swatches p: 0 28 95 5 – color panel: 1 34 92 2 How can or should the default palettes be used in a CMYK-.afpub? - Just ignore a wrong value? But then, how can I use the standard shades of grey, which are only apparently tints of 100 K, and export them as a single color channel instead of 4-color in CMYK print?
  8. Not for me: I haven't copied any preference file from the beta folders. (I only exported/imported palettes and assets.) [ Oh, I always forgot their values ... specially if distinguished by additions: wasn't their even "Snow Lion Mountain High" ? ]
  9. Ah, good to know. - But then, should the button not be greyed out when assigned to a non-rasterized object?
  10. Der weiße Text des PDFs ist in seinem Ausdruck schwarz. Henry, das kann kaum ein Fehler oder Problem innerhalb von Publisher sein, da das PDF vermutlich das gewünschte Ergebnis zeigt, oder? Acrobat erkennt im PDF nur dort Schwarz wo du es auch haben möchtest: Ich weiß keine Lösung, vermutlich ist das ein Drucker- oder Drucker-Treiber-Problem. Versuche mal ein PDF/X-1. Wenn das nicht hilft: Vielleicht mag der Drucker keine CMYK-Daten sondern möchte ein RGB-PDF? EDIT: oder druckst du aus AfPublisher? Dann hilft es evtl. den Dokument-Farbraum zu wechseln. (ich drucke Farbiges grundsätzlich nur als PDF, weil ich dabei besser steuern kann, was der Drucker bekommt.)
  11. +1, Agree! At least nothing with a same intuitive UI, indeed. For the time being you might take a look at 'Darktable' or 'DxO Optics Pro'.
  12. Yes, that short, with a new doc with 1 page, no master, no content. Affinity Publisher_2019-06-26-122950_mbp1.crash new empty doc crash on save as.afpub
  13. Yes, I experience this issue, too. In detail: Export to PDF: Only the first single page of facing pages exports as expected with inner bleed = 0. The following pages do show inner bleed in width of the three other edges. Print > Save as PDF: Scale: on all pages inner bleed = 0 Shrink: No bleed appears at all. For export & print the results are regardless whether any marks are activated. So it is a weird bug that inner bleed = 0 gets ignored on export only, not on print. (whereas a scaled print can't be used as workaround)
  14. Yes. (since final retail release only) Whereas I can do a Save As... + replace without crash if the open file is NOT the same which I do replace, means it works only, if I replace a copy with same name but in different file path (for instance a folder inside the folder).
  15. I don't get the quicklook offer in the 'Open With' list. QuickLook does not work for Affinity documents in my Sierra 10.12.6. Though there is a .qlgenerator file within the application package (.../Contents/Library/QuickLook/QuickLook.qlgenerator)
  16. That is weird. My tab order is horizontal first, then vertical at line end: X > W > Y > H > icon > R > S (> X ...) and works like that in both directions. Both in English and German app and/or keyboard languages. I do recall the tab order and the shift-use was the same to me in since previous betas. Also I can't think macOS initiates that difference, especially since that behaviour is for you in 10.9. and 10.14 identical. Do you still have the .dmg of your AfPub installer? I had read in the forum about version 404 in posts after final release – whereas my filename is "affinity-publisher-1.7.1.408.dmg". It would be nice to hear how the tab order and shift-tab work for @Old Bruce in transform panel. (As far I remember from a beta he had an UI difference in Canada vs. me in German, and he could compare 10.12. and 10.14.)
  17. Unfortunately this layer property color, used on a master page, seems to get lost on document pages: there it gets reset to default Blue. And, indeed, unfortunately object layers do not have that property option at all. Colorful side effect and feature for a moment: When I apply such a layer property color then immediately it gets applied to ALL pages – until I activate any object or different page.
  18. If I do a Save as... with same .afpub name then the app crashes in most situations. I am able to repeat this with only a new document opened, too. (p.s.: didn't act like that in previous betas)
  19. Shift-Tab Key work for me like a charm through all entries within the transform panel. Its contour color is just not a brilliant color. Especially in dark UI mode it is almost invisible. Also, I'd appreciate a different running order. to get both X & Y and W & H accessible with 1 tab only instead the need of 2 tabs. You may alter the shortcut key according to your desires in the application preferences. If you activate any panel item with a click before you use the tab key then it prevents unwanted UI toggle and jumps between panel items as expected.
  20. Ah, yes, a UI preview mode "curves only" would be helpful in AfPub, too. Two Workarounds: 1. Since the visibility of these UI curves does depend on the object fill color you would have to toggle different UI curve colors for different fill colors. So, as a compromise, why not toggling temporarily the fill visibility, either its color or layer/group opacity or blend mode? 2. If you have AfDesigner besides AfPublisher then you can switch to the "Designer Persona" and activate "Outline Mode" (Cmd-Y). Then all content appears in black contours with no fill, regardless whether an object got converted to curves. Back in Publisher Persona the outline mode remains active until you toggle it again as Designer Persona.
  21. What makes you think that deleting a .propcol did nothing? Did you have, after deleting the .propcol, still even your custom installed brushes available? Have you closed the app before deleting the pref? What makes you think they have NOT been removed?
  22. Also with a pinned object I don't get your issue. But I experienced dimension issues related to document resolution, also there was a thread in the beta forum about size issues with assets, where a stroke width always scaled with an object scale. I think you should not try to fix the issue for your initially case but rather do tests with fresh, virgin objects, which aren't copied or imported as editable from other files.
  23. Nothing strange. Just enlarge the frame height by 0,01 mm and the number will have enough space to jump to the next line. (actually I need to type in transform panel only a 5 behind the 2 in your 135,82 mm, means 0,005 mm) Try to avoid to make the frame height so close to the grid line.
  24. What reason do you suspect? Can you show it with special characters activated? Or just upload that page? It seems to work here:
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.