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

Old Bruce

Members
  • Posts

    15,221
  • Joined

  • Last visited

Posts posted by Old Bruce

  1. @Tamla and @NathanC,

    I would strongly suggest using Nathan's "Alternative" suggestion and stay away from using the Document Setup. The reason for this is because then the PDF will be single pages even though you start with double page spreads. There will be projects that have multiple Master Pages applied, as well as asymmetric margins and changing the Document Setup to Single pages can cause problems with editing later on.

    It is far easier to get a good looking document with Facing Pages for the layout even if you only want to export a Single pages PDF. Going the other way is going to may well cause a great deal of grief.

  2. 5 hours ago, Compositor K said:

    I brought in "No style" only as a means of demonstrating that baseline grid on does indeed seem to be the default. I never had any notion of using to control future styles. For that, as you say, dependent styles are the way to go.

    One of the first things I learned to do with Affinity Publisher is set up [No Style] the way I want it to be. I will choose to have Align to Baseline Grid off. Then with some of the text selected I go to the menu Edit > Defaults > Synchronize from Selection and then immediately go to Edit > Defaults > Save. Now the [No Style] will have my choices honoured.

  3. 18 hours ago, Pan Przemysław said:

    Oh wow, I just realized the backward (in)compatibility issue. I designed a menu for a friend's restaurant and recommended that they buy a license of Designer to make edits to the ever-changing menu. They bought the license and we have been co-editing the afdesign files for the last six months. And then I upgraded to Affinity 2 and my files are no longer compatible with my client's program. :/ They are willing to upgrade, but still..

    I am assuming you have both V1 and V2 applications up and running. If you work in V2 and wish to send a V1 copy to your client...

    First off, use Artboards. This will keep the Document paper sizes.

    Second, in your V2 application select all the artboards and copy them. 

    Third, in your V1 application choose File > New from Clipboard.

  4. 2 hours ago, Dimmo said:

    Now when I highlight the second word with move tool it doesn't show the font family, now it I put the text tool at the end of the second word and hit delete the font family is now showing.

    Odds are that you have a Return character at the end of the word "Designer" and that Return Character is a different font. This is the only way I can get the blank font family to appear as you showed in your screenshot.

  5. 27 minutes ago, R C-R said:

    That AD 2 dialog seems kind of buggy in several respects to me. For instance, set it to Type: Presets, & then open on the Page Preset: list. For me, that includes multiple duplicates & just about every preset in every category.

    I think that what is happening there is we are getting the Print and the Print (Press Ready) items duplicated. So it is the Colour Models RGB vs CMYK showing up as duplicated same sizes.

  6. My first thought from looking at the screenshots from @mykee is I wonder if there is maybe a "Keep Paragraph together" setting turned on in the Paragraph Style.  It certainly looks like it to me. Without a document that exhibits this problem we will all be speculating ad nauseam and the solution may get presented and missed.

    Other than that did you try a line break (not a new paragraph. Use Shift +Return) in the bottom of the text on the right hand page? If yes did you still get the indent?

    ScreenShot2023-08-03at10_03_35AM.png.5f8700f4b307875f4a898438e2b746ca.png

  7. 18 hours ago, CJIIIFS said:

    Rather than keeping the naming structure and layer structure I specified, Illustrator mashes everything together under one layer, with no names and no groups. The file I worked so hard on looks like such a sloppy mess. Even my text boxes have been divided into letters that have been converted to curves, rather than a defined box for text to reside in.

    You can get Layer layers in Designer to export as Layers in PDFs but everything else will be given generic names, rectangle, pixel layer etc. So if you need to have Everything named SVG may be the way to go. But if you just need the Layers for organizing bunches of layers then you can use PDF if you use Layer layers instead of Groups.

  8. 22 hours ago, garrettm30 said:

    I recently encountered an issue in one of our documents....

     

    5 hours ago, Dan C said:

    I can confirm that I've been able to replicate this issue here and I've logged it with our development team.

    It appears to be triggered by the Language. If I change it to None for the Hyphenation (and maybe the Spelling) then things work right. English (UK) seems to solve it as well.

     

     

  9. 15 hours ago, PanthenEye said:

    I just want this to be possible in Designer: https://github.com/EsotericSoftware/spine-scripts/tree/master/photoshop

    Creating new tools is all swell and good, but I just need a basic export pipeline for Spine 2D animation software, which is the industry standard for 2D animation in video games. The linked script saves literally hours of work and is the single biggest reason I'm still subbed to Adobe. Hopefully, the API will cover things like merging layers, parsing layer names then do operation X if the name contains some string, change exported layer name, add alpha padding to each exported image, trim alpha whitespace, set and read designer document ruler origin, read layer mode, scale layers before exporting and write relevant data to a JSON file, which Spine can then import and rebuild the exact layer order, layer position, layer mode and everything else that's relevant. This should be possible without manually defining export slices, ain't nobody got time for that. 

    There is a "Spine JSON" choice in the Export Persona. I don't know if this helps you.

    ScreenShot2023-08-02at7_31_42AM.png.67057ed0c7f654143b30d5ae18a56808.png

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