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

thomaso

Members
  • Posts

    11,394
  • Joined

  • Last visited

6 Followers

Profile Information

  • Location
    Cologne, Germany

Recent Profile Visitors

10,091 profile views
  1. A simple alternative would be the Node Tool + Transform Mode. Unfortunately it does not preserve the colour per line as in your sample. strokes lines blend.m4v
  2. Not only if you're typing. – For existing text choose the "Then Next Styles" option from the style's the burger menu. This menu option appears once a style has a "Next style" set in its style definition.
  3. @NotMyFault, very nice solution with the channel mixer. – But does it need the duplicated + merged layer? It seems to work non-destructive without this steps, too.
  4. If Walt's suggestion doesn't work for you: • The files you loaded from Corel seem to be placed in APub as "Image" layers. If this images are already stored on your disk you can send the according folder(s) to the freelance lady. • Alternatively open APub's Resource Manager window -> select all items -> press the "Collect…" button to get all placed resource files copied into a new folder on your disk. • If you want to send her all data (images + .afpub layout file) choose menu "File" -> "Save As Package…".
  5. In this case of straight edges + similarity between blue & green the Pen Tool appears to be a fast solution.
  6. A more safe workflow in Affinity is to keep both export options "as document" and adjust the document colour settings before export instead. If your document contains black text you may have assigned 100 K (with CMY = 0). To preserve colour values already set in the Swatches or Colours Panel choose the option "Assign" when selecting a different profile for your document. Simply spoken they adjust document colours according to the printing process (machine / paper). For instance a coated paper may require less ink compared to an uncoated paper, a yellowish paper requires less yellow ink. – Introduction to the ICC profile format: https://www.color.org/iccprofile.xalter – What is FOGRA39? https://www.color.org/fogra39.xalter – Fogra Characterization Data: https://www.color.org/chardata/FOGRA39.xalter
  7. In my understanding of the use of Column Guides a limit around 48 wouldn't harm, regardless of page size (assuming that larger page dimensions use larger object sizes). As you mentioned, for more the Grid option may be more useful than Column Guides. In my examples of 700 or 1500 the rendering speed was massively reduced even for just panning the page (while no object was created).
  8. Was there an "improvement" in V2? – In V1 the limit appears to depend on the page/spread size but is definitely higher than the resulting grid useful. For instance on a spread of 2x A3 landscape:
  9. @MEB, regarding "object is discarded" also the Designer Help is wrong or misleading at least: While its style attributes get discarded its layer type switches to Text whereas its original object type is still accessible with any Shape Tool:
  10. It depends… 😄 Essentially, a group style helps when you want that a bunch of related styles (all based on a common parent) can be grouped in the style panels when using hierarchical presentation of styles. Its main advantage is that any formatting applied to the group style is propagated in all the styles based on it, excepted for overridden formatting in each style. (To have an example, you can look how the paragraph style Body and the group style Base interact in Affinity's default style sheet.) A Group style is identical with a Paragraph style but just has a slightly different user interface: • Clicking on a Group style does nothing whereas • Clicking on a Paragraph style applies this style to a selected text or text frame. In this aspect a Group style is less effective but more or less efficient, depending on the user's habits. To apply a Group style you can use its burger menu: Group + Paragraph + Character styles can get displayed collapsed | unfolded as soon they have styles that are "Based on" them. They list them as hierarchical child entries, regardless of par- or char-styles. Also each style type may 'contain' other Group, Paragraph or Character styles. The ability to assign a paragraph style to characters only (~ as character style) + the ability to create a Group style based on a Character style increases the flexibility in potential effectiveness, efficiency, complexity and confusion. Thus it is just up to the user to achieve the "best" setup: • To reduce confusion it can be useful to avoid the "Based on" or "Next style" attributes but sort the style entries in the panel by their names only. • To increase efficiency it is required to use the "Based on" or "Next style" attributes. • While "Based on" is indicated in the panel interface as child entry, the "Next style" attribute doesn't have a visual indicator and thus it appears quite useful to mark a "Next" style by its style name (or number). • If a Group or Paragraph style has 'nested' styles defined, for instance as "Drop Caps", "Initial Words" or "Bullets and Numbering" it can be useful to define those as "Based on" to achieve hierarchical presentation in the panel – but this also creates dependency between the parent & the character style which may disturb if these character styles are meant to get used for multiple parent styles, for instance if the character style causes a different colour only that will be used for various highlights across the document. • Since a Group style is a paragraph style it doesn't have to get a further paragraph style nested and may contain character styles only or even no further style at all. You can switch a style between Char | Par | Group style type at any time with the according consequences to its possibly dependent style properties in other styles.
  11. While the Resource Manager tells the resolution for selected + unselected image resources, the Context Toolbar shows the resolution for a selected image and pixel layer.
  12. Oddly, arrow heads can handle brush opacity – they just ignore it for pressure. Here brush opacity of a marker brush:
  13. And maybe because… • arrow heads are (have to be) separate objects, not just the ends ('caps') of a singular stroke .(->"expand stroke")
  14. Maybe because… • size is an explicit arrow head attribute while opacity is not? • transparency is an issue for arrow heads anyway, independently of pressure or brush settings but with just colour opacity? Compare this question regarding an transparency issue of arrow heads: (interestingly this thread appears to have been moved by Serif to the Feature Request forum / and the OP's question got no Serif response but another question did.)
×
×
  • 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.