thomaso
-
Posts
11,201 -
Joined
-
Last visited
Posts posted by thomaso
-
-
3 hours ago, PaulEC said:
I don't really understand why you need to be able to select a page that you're not working on anyway!
Sounds funny. The page I work on I do see in the main window. I need the pages panel mainly to show all other pages, all those, I am currently NOT working on. Just to be able, to simply select one of them to make it become a page I am working on
Also, be aware, you can select more than 1 page, for instance to move them to a different position in the document. Besides the 7 things mentioned by Walt already.
-
Weird. Would you mind to upload that .afpub?
-
On 6/28/2019 at 12:05 PM, Dom159 said:
gradient fill, white to transparent with the starting opacity of the white at about 80%.
(...)
I was just surprised that a gradient fill would be an "unsupported element".
The point is your "transparency" as a gradient "color", because you don't want it to be a fill or color actually.
A color always has values of 0 or above, and on screen it always results in a pixel between white and black – whereas transparency is not in the color spectrum.
Therefore you need to use a PDF version that supports transparency (v1.4 or higher) – or else you need to flatten/rasterize, to make the color underneath get charged with one above. -
Thank you for the link to the help URL at serif.com. I haven't been aware it's also there.
Also, I have not noticed before Walt's hint that the lock indeed influences the color selector type.
I was confused by not locking color spaces and, even worse, regardless of lock on or off, I often get different, contradictory color values for a swatch. – For instance:CMYK .afpub: If I double-click on a swatch of the default predefined ...
A.) Application palette "Greys", then I see 2-3 different indicators in:
1. the swatches name & tool tip: Black xx %
1.1. the popping up color selector: CMYK with K-only
2. the Color Panel: RGB slidersIf I now toggle in the color panel to the CMYK sliders then there it shows 4-c values, synchronously but contradictory to the K-only of 1.1.
If I export an object with such a "Grey" then it results in 4-c, not K-only, regardless what selector type is set in color panel before export.B.) Application palette "Colors":
1. the swatches name & tool tip: HSL
1.1. the popping up color selector: CMYK
2. the Color panel: HSLIf I now toggle in the color panel to the CMYK slider then there it shows 4-c values which are different and contradictory to those in swatches panel:
color panel: cmyk 0 93 93 5
swatches p: cmyk 0 82 100 0Again, an export results in the values from the color panel slider. What value do the swatches panel slider show?
C.) System palette "Web Safe Colors": do a search in swatches panel for "003":
1. with No document open: with double-click of any resulting swatch I get in the pop-up swatches panel RGB sliders the value 14 for the swatch name part 33.
2. with a document (Adobe RGB profile) opened: same as in 1. plus a 20 in Colors panel.So I get 3 different values for 1 channel of a color swatch: 14, 20, 33 – How can I detect, with what value the swatch was saved?
Can one of you confirm such contradictory values?
Can one of you explain the differences within each of A., B. C.? Are they possibly related to different rendering intents (perceptual, relative, absolute, saturation) ?
-
Can you detect where the wiggly lines of your screenshot belong to? Is it to words in the same frame (how far away?) or to another frame or to no fitting words at all actually?
-
11 hours ago, user1984 said:
When I change the document setting from "pixel" to "mm" with 300 dpi all images appear sharp and crisp. Then I copy the document to my other Mac and ... pixelatet! So I change the doc on my other Mac from "mm" to something else > safe > reopen again, everything looks fine!
@user1984,
if your macs cache would be related then I would not see your preset unit "pixel" on my computer when opening your doc.
On the other hand I don't see in your doc any change of visual sharpness, regardless of the selected unit. – So I'd like to know what makes the difference indeed.1. When you wrote how you solved the issue then you say first "from pixel to mm" and second "from mm to something else". Does it mean, you can see the image in expected resolution in every unit but must switch the unit first?
2. And, if you changed the unit, don't you see the new unit in the ruler immediately – without the need to save and reopen ?
3. And, possibly, see the better quality immediately as soon you select a blurry image frame – before save and reopen the .afpub ?
4. Can you reproduce this different image quality between your macs with others .afpubs ?
-
1 hour ago, user1984 said:
Then I copy the document to my other Mac and ... pixelatet! So I change the doc on my other Mac from "mm" to something else > safe > reopen again, everything looks fine!
That is strange because my mac opened your .afpub in pixels, means in the unit you had saved it.
So I wonder why your other mac did not see that setting in the .afpub.? -
another, historical approach:
in early computers all fonts were pixels, no vectors. The letter O was not a round circle but a collection of squares arranged in the look of a circle. If you printed such an O in huge size (= with high print resolution = high DPI = a lot of pixels/dots on paper) then the O did not become rounder but its steps became larger and more visible, more obvious.
The misunderstanding might come from two different usages of the term resolution: a.) the input = content / b.) the output = result.
Of cause one can print a low res a) with a high res b) – and that way your mathematics is correct: the printer does more work and puts more and tinier dots.Resampling (or upscaling) does not reduce the amount of visible stair steps of the letter O from above. It simply shows the squares more detailed, usually by a softer edge (compare: Antialiasing).
-
56 minutes ago, walt.farrell said:
Do you have a demonstration or proof that the dpi claimed in the Resource Manager is not correct?
This thread is one. It appears the low output resolution got fixed by switching the document unit.
Here is another one:
1. Create an image with 10 x 10 px. and save with 72 dpi. (<– a tiny icon for instance)
2. Place it in Afpub: 72 DPI, unit pixels.
3. Print (fill the sheet).
4. Increase the documents DPI up to 1200.
5. Print again.Do you really expect the 2nd print will show the image in higher resolution (= sharper) than the 1st print?
Whereas the amount of printed 'dots' (='pixels') get increased by increasing the documents DPI – still the image (10 x 10 px) remains the same and never will become better by upscaling.
THAT is why vector is preferred. -
If indents and background fill color are assigned to ...
A.) ... the Frame object then you can't save it as a text style. But you can save it as an Object Style:
Right-Click the frame or Menu Edit > "Create Style". Then you will find it as an object in the Styles Panel.B.) ... the text as paragraph decoration then you can save it as custom Decoration in a pulldown list AND can save it as Text Style.
indents and bg color are more flexible if assigned to text, but also more complex, of cause: -
12 minutes ago, user1984 said:
It is true, the document is in pixel without dpi.
No, it's even worse. In document unit pixels a resources resolution depends on document resolution. But actually it just pretends to ...
2 hours ago, walt.farrell said:it's tricky to understand when looking at px values.
I see and understand what happens if set to pixels: Then a resources resolution appears to increase with an increase of document resolution.
Or: if your resource is shown with too low placed DPI then you simply increase the document resolution and Resource Manager wants to make you believe the resources resolution is fine now. – A Horrible issue. Because:
That way you never know what the true resources resolution will be on output. [ Except: documents DPI = resources original DPI. ]
Don't you agree that will result in a lot of confusion and complaints? I definitely name this a bug.
(In AfPub beta it used to be the same for mm, inch etc. but got fixed. Guess why?) -
1 hour ago, nwhit said:
Also just added note to above instructions that you can't use the top Contextual tool bar Fill button. MUST use the main Swatches/Color panel in order to have access to modifiers.
Ah, that's the point! Very good, thank you!
I still forget too often about the various capabilities of fill tool (have it in mind as gradient tool only).Looking at your samples I get one more place in mind to define a fill behind text: in Paragraph Panel > Decoration:
You can include negative inset, save individual variations in a pulldown menu, and assign them to text styles.
-
I don't think yet that it is something which needs to get fixed. Maybe you find hints in the help or in a tutorial about the use of such a layer (or adjustment or filter) with "hourglass icon" (which probably has a name by Affinity to search for).
-
Ah. Do you get the opacity value? Can you show a screenshot?
To me the color options here is the same as in text frame panel. – No opacity value/number given:
-
@ Walt, when I opened the user1984's .afpub it had unit pixels in document setup. Therefore in Resource Manager the original and the placed size are both in pixels. And obviously (see screenshot) the original values for both dpi AND size are smaller than those of the placed. These "AND" can't be true, because the placed DPI does not increase together with the placed size.
-
@ criu, both the hsl and curve adjustments are exported, even in your "example.pdf" they occur to me. Just compare before/after side by side.
The used gaussian blur (with "hourglass icon") does not exist as an adjustment in AfDesigner and AfPublisher, and, sorry, I don't have AfPhoto, so I can't really check this layer.
Yes, when I export as PDF the gaussian blur does not appear – but it does appear on export as JPG for instance. It also appears on PDF export if I rasterize the image layer before export. Maybe that gaussian adjustment from AfPhoto can't be used in AfPub natively?
Possibly someone who knows this filter from AfPhoto will post a hint. I remember there was a thread about it in the days after the final release and it sounded to be tricky with correct layer positions. Unfortunately I can't find it in the forums search.
As a workaround you could replace it in AfPub with a gaussian effect (FX). -
It is hard to judge because the placed image is quite pixelated by its design.
But the values of placed DPI in Resource Manager appear strange: for instance the item in the bottom right corner:
original: ca. 2000 px, 72 dpi
placed: ca. 4000 px, "144 dpi" ?
That can't be true.If the placed image has twice the size of the original, so its DPI can not be doubled but must be the halved, means placed DPI is 35 dpi - instead 144.
I know such a behavior of increased placed DPI from an earlier beta (I guess up to v293) but it got fixed before final release.
Also weird in your doc on my mac:
When I increase its document resolution (300 > 600) the placed image DPI increases, too (144 > 288). Which can't be true for the same reason mentioned above.
When I change the document units from pixels to millimeters > close window > change back to pixels then it is rather confusing: the former spread size of ca. 7000 px is now ca. 3500 px. Hm. The half. – Possibly you had switched document DPI and/or unit while creating the layout and confused the application that way?If you can reproduce that weirdness: As a workaround I would copy all content and place it in a new document with the unit and DPI you really want.
-
Interesting. Could one tell please in what chapter the lock is mentioned? I had read the help text about Selection of Colour / Work with the Panel Colour – but the lock is not mentioned in my German help text, I get German help only, even with English app language.
Unfortunately the help menu search doesn't show any help text results to me (only menu items).
-
Since the retail version of Publisher (v408) the Help Search appears not to work for me any more, neither in the Help menu nor in the separate Help window.
A help menu search results menu items only, no help text articles.
In the help window I get only a blank page for any search result.I am on a German macOS, I tried in English and German application language and with both English and German search language – but don't get help text search results.
While the help search functioned charmingly during the beta versions of the publisher, I was even able to search in English & German, without the need to switch the application language. Depending of the language of the help menu result the according help window language opened. – Now, in v408, I only get the German help window.
3 Samples of search for Colour + Farbe:
(in Eng + German app language)
3 samples from the help window: -
I don't understand "screened". Whatever, if you need it often then you possibly might save as styles or assets.
-
4 hours ago, nwhit said:
how in the world do we set consistent opacity on color fills for tables and text frames? I have yet to find any alternative where we can enter the opacity %
Until it gets fixed I would not use those frame fills but rather separate shapes as color background. These allow to set opacity in the color, the swatches and the layers panels. – Or, if it's a must to colorize the text frame: assign a gradient with two identical colors and opacities.
-
Are you more successful with another PDF version? How about PDF/X-3 ?
If you like upload your file for a check. Don't forget to embed an image. -
PatC, the Wrap Style "Edge" is supposed to do what you see inside and outside of your hat image. Just look the difference in the icons "Tight" and "Edge".
-
I purchased Designer in the week before Publisher came out. I mention this because you say the Publishers crash is possibly related to Designer & and I had said before I never had a Save-As-Replace crash in any Publisher beta.
I can export PDFs in Publisher without crashes, in Designer I have tried only twice and that worked fine, too.
In the video you don't see panels because they usually fill this screen and I had to toggle them off to see the new document window.
– By the way, with 2 monitors and Separated Mode: It would be useful if new or just opened document windows would appear on the monitor which shows the tool bar. That could avoid the need to toggle the UI if using the 2nd screen for documents.
Crash on Save as... with same file name
in V1 Bugs found on macOS
Posted
Both from Affinity Store.