Jump to content

Recommended Posts

Posted

Why is there a thin line between the fill and the stroke for an outer stroke setting?

I realise you can set the stroke to come from the middle and this fixes it, but that is not idea in all situations. 

 

Screen Shot 2023-01-28 at 7.00.59 am.png

Screen Shot 2023-01-28 at 7.09.48 am.png

Screen Shot 2023-01-28 at 7.12.02 am.png

  • 11 months later...
Posted
On 1/28/2023 at 1:05 AM, lacerto said:

Hello @Josh9856, and welcome to the forums.

This is a common issue in graphic design apps and related to antialiasing. Some apps can deal with the issue in context of export by automatically overlapping inner and outer parts of these kinds of objects so that the gap is covered. Affinity apps unfortunately cannot do this so to avoid this, some manual work is required. Most often these issues would not show on printed design.

It's a shame for web images. I don't usually use outer stroke over a color that would show through. It's interesting how one can use a program for so long but never notice some things...

Posted
1 hour ago, debraspicher said:

It's a shame for web images.

Why it is a shame, and for what or whom?
 

1 hour ago, debraspicher said:

It's interesting how one can use a program for so long but never notice some things...

Seems this is an issue rarely having an noticeable impact as lacerto said.

And there are easy workarounds. Why use an outer stroke in this specific case (same color, 100% opacity)? Center stroke of double width produces the intended visual result.

Affinity has limited resources so issues with higher impact needs to get prioritized for fixing.

On 1/28/2023 at 8:05 AM, lacerto said:

Some apps can deal with the issue in context of export by automatically overlapping inner and outer parts of these kinds of objects so that the gap is covered

Interesting, do you have more details? Does it work for raster and vector export formats?
Specifically in case of vector formats, how are these layers adjusted? Increasing stroke size? Combining stroke and curve into one curve? Applied to text layers?

No matter which approach is used, it will definitely modify the original curve / stroke of the file. So if you export e.g. to svg and re-import again the layers will differ. I dont say this is a bad thing, but at least users should have a choice.

For me it is a question of „Philosophy“: Affinity apps tend to export layers „literally“. In some cases users may prefer if Affinity would apply some adjustments to heal common issues, e.g. closing gaps like in this case.

Mac mini M1 A2348 | MBP M3 

Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.

 

Posted
15 minutes ago, NotMyFault said:

Why it is a shame, and for what or whom?
 

Seems this is an issue rarely having an noticeable impact as lacerto said.

And there are easy workarounds. Why use an outer stroke in this specific case (same color, 100% opacity)? Center stroke of double width produces the intended visual result.

Affinity has limited resources so issues with higher impact needs to get prioritized for fixing.

Interesting, do you have more details? Does it work for raster and vector export formats?
Specifically in case of vector formats, how are these layers adjusted? Increasing stroke size? Combining stroke and curve into one curve? Applied to text layers?

No matter which approach is used, it will definitely modify the original curve / stroke of the file. So if you export e.g. to svg and re-import again the layers will differ. I dont say this is a bad thing, but at least users should have a choice.

For me it is a question of „Philosophy“: Affinity apps tend to export layers „literally“. In some cases users may prefer if Affinity would apply some adjustments to heal common issues, e.g. closing gaps like in this case.

This is quite the defensive post from a simple comment and I have decided not to get into a rundown where I should have to run my observations by you in order to get into the specifics. That's not why I post here at all and it is a bad use of time over a relatively minor criticism.

Posted

@Josh9856 Try using the contour tool instead.

  1. To thicken a typeface select the text layer
  2. Select the contour tool and set the expansion of the typeface as you would with a stroke 
    If you are happy with it you can bake the contour bearing in mind baking will convert the text to curves, else do not bake and the text will remain editable.
  3. If you want to have a colour stroke effect, duplicate the text and contour the text layer below to have a simulated coloured stroke.

image.png.bb861d6a7b4e629c0bb45466a52cde1c.png

iMac 27" 2019 Sequoia 15.0 (24A335), iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Posted
16 minutes ago, lacerto said:
3 hours ago, NotMyFault said:

Interesting, do you have more details? Does it work for raster and vector export formats?

Illustrator, e.g., does it both when exporting to vectors (e.g. PDF, SVG), (…)
(…) expands the outline and then overlaps the "stroke" and "fill" parts.

Visually the .ai example appears like a trapping result … an option which Affinity generally lacks.  (= Über-/Unterfüllung, @NotMyFault)

 Ai versus AD:

aipdf.jpg.a9ea18d8af35d283e18a1b1559a66c5a.jpg

ADpdf.jpg.31c4895f81aa13d7f2e3a368bad18884.jpg

@lacerto, in your post the .ai.png appears twice (where the AD.png is expected as comparison). Can you delete one and reposition the AD.png from the post bottom to avoid confusion?

Bildschirmfoto2024-01-19um12_04_50.jpg.0eff58d0ace41ff5ee1e8ecea76ce251.jpg

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Posted
5 hours ago, NotMyFault said:

Why it is a shame, and for what or whom?

"shame" ≠ Schande (German) but also might simply express "it's a pity" (= schade):

"It's interesting how a pity that one can use a program for so long but never notice some things..."

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Posted
5 hours ago, thomaso said:

"shame" ≠ Schande (German) but also might simply express "it's a pity" (= schade):

"It's interesting how a pity that one can use a program for so long but never notice some things..."

Sorry I’m non native English. My usual dictionary says shame = Schande and gives multiple examples confirming this interpretation 

 

12 hours ago, debraspicher said:

It's a shame for web images. I don't usually use outer stroke over a color that would show through. It's interesting how one can use a program for so long but never notice some things...

Debra, i did not intend to offend you. Sorry for causing any inconvenience. I was asking out of curiosity because I could not interpret those 3 sentences in combination. It’s a shame, but you don’t use the function. Then why wondering that you never noticed- what exactly, using outer stroke, getting unwanted transparency between stroke an fill, … ?

I don’t need any explanation from your side. Sorry again. On the other side. Why assuming the worst in my post and giving such a strong reaction?
Again, these questions came to my mind, don’t feel obliged to waist any more time in this matter. 

IMG_1033.png

Mac mini M1 A2348 | MBP M3 

Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.

 

Posted
5 hours ago, NotMyFault said:

Sorry I’m non native English. My usual dictionary says shame = Schande and gives multiple examples confirming this interpretation 

Me too. I also was confused by the use of 'shame' in a recent response that made me doubt about my German understandig of "shame" as "Schande", the user seemed to combine it with a friendly reaction, which let me search for alternative translations.

A forum search appears surprising, too: It finds over 1300 uses, unlikely in the sense of "Schande" as "disgrace" or "infamy". To my ears, the above said something like, “Stupid, I didn’t notice that before.”

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Posted

FWIW, the macOS Dictionary app "American English" entry shows this:

Quote

 

shame | SHām | 

noun

• a painful feeling of humiliation or distress caused by the consciousness of wrong or foolish behavior: she was hot with shame | he felt a pang of shame at telling Alice a lie.

 a loss of respect or esteem; dishonor: the incident had brought shame on his family.

 used to reprove someone for something of which they should be ashamed: shame on you for dredging up such terrible memories | for shame, brother!

• [in singular] regrettable or unfortunate situation or action: it is a shame that they are not better known.

 a person, action, or situation that brings a loss of respect or honor: ignorance of Latin would be a disgrace and a shame to any public man.

 

 

All 3 1.10.8, & all 3 V2.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Posted
24 minutes ago, R C-R said:

• [in singular] regrettable or unfortunate situation or action: it is a shame that they are not better known.

But why does it add here "[in singular]" – isn't "shame" always singular, can there be "two shames"?

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Posted
1 hour ago, thomaso said:

But why does it add here "[in singular]" – isn't "shame" always singular, can there be "two shames"?

I can only assume fom the usage that it refers to usages like "a shame."

All 3 1.10.8, & all 3 V2.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.