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

Posts posted by thomaso

  1. 2 hours ago, walt.farrell said:

    transparency won't be apparent unless you set the document color handling options to "transparent background"

    A resources transparency 'usually' is visible in AfPub without "Document Setup..." > "Transparent background".

    1615023197_transparencyimagewithouttranspdocsetup.jpg.b7fd27fc6b32aa7857e26e3deae7fb0e.jpg
     

    Unfortunately image transparency is not visible in AfPub for grayscale images which got colored via fill color in AfPub – regardless whether doc setup transp background is on/off.
    Same missing transparency for images which have a clipping path included to create transparency. That appears to be basically ignored by AfPub.

    1923692000_transparencyimageclippingpath.jpg.c0dd030aa75d3d9c748bcaae0fbc957c.jpg

  2. This eyedropper tool in panels acts a bit different than the eyedropper of tool bar.

    If you simply click on it in a pop-up color panel, for instance of the fill color in the text frame panel, then it fills a selected object with the "active" color which is shown before in the tiny color preview circle right to it.

    If no object is selected then it does nothing there, or, if you have color sliders visible, then it sets them to the color of the tiny icon.

    To use the eyedropper of text frame panel as expected you need to click-HOLD and, still with the mouse button pressed, move around on your monitor. It picks any color underneath, even of UI (panels, bars) and objects of other applications which might be visible behind the Affinity app UI.
    If you release the mouse button then it sets this color to the "active" color and with a click again on the eyedropper or on this color in the tiny icon you fill a selected text frame.

     

  3. What you describe sounds more like use of RAM, not saved document file size. History might be a reason, but probably not the one we select in menu File > Save History...
    In my .afpub "Save History..." has not been active but it formerly contained 90 pages, which all got deleted unless 3 and then Saved As... I assume there is another kind of history in that .afpub which it can't get rid of. – Even another "Save As..." did not reduce it's file size, whereas for the 90 pages 'mother document' with Save As the size shrunk even below the 33 MB of the 3-pgs afpub.

    The massive increase of your file size within 1 day sounds (520 MB > 1.3 GB) as if you have worked, tried, altered a lot. Did you? Or did you just add content?
    How much ca. % did your file size reduce when you used "Save As..." with a new file name?

  4. On 6/28/2019 at 2:38 PM, Jon P said:

    I've exported some 200page documents with an image or two on each page and not had the export take longer than a minute.

    That sounds interesting.

    Does the color space matter for you on export time? Or whether they are embedded or not? – I wonder because I get very different times:

    10 jpgs, RGB, 60 MB, scaled 65%  |  10 pages, A4, 300 dpi  |  Export as 1.7 (default print PDF preset):
    Afpub + pdf in RGB:     40 sec - 13 MB
    Afpub + pdf in CMYK:  10 sec - 39 MB

    Do you have an idea where this difference comes from? I'd rather expect RGB to export faster. –  If you want I'd like to upload the .afpub + 10 images.

  5. In an .afpub with CMYK color space I use "Add chord to Swatch..." to create variations of a defined CMYK color.
    I can't get any useful swatch this way. For use in a CMYK workflow the result is somehow messy.

    The resulting swatches are ...

    1. each of them in RGB – regardless of "Lock colorspace" was on/off before starting the task.
    2. A few aren't in RGB, but a mixture of HSL and CMYK – (for instance: "Triadic").
    3. Each of them results with different values in Swatches panel versus Colour Panel.
    4. Some swatches start with its initial color which was set in color panel before use "add chord", some start with another color which was not set.

    Samples:

    A.) Tints of 100 K –> all RGB:
    598814620_colorchordtints100K.jpg.835faff559d59595fca1cc7bb83e91fd.jpg


    B.) Tints of 0c 100m 60y 0k –> all RGB.
    See also the different values of the selected swatch in Swatches Panel towards Colour Panel:

    1409804872_colorchordtintsCMYKorange.jpg.177eeb7da914cebeb5d093e7f355ed0c.jpg


    C.) Tints of 100c 50m 0y 0k –> all RGB
    Notice the massive change in the initial start color: Minus 26% cyan!

    977158675_colorchordtintsCMYKblue.thumb.jpg.896bef10297512678d1d76f3d439cad8.jpg


    D.) "Triade" of 100c 50m 0y 0k –> 1x CMYK, 2x HSL
    Note: this was the only result where the initial start color = resulting swatch.

    224425773_colorchordtriadeCMYKblue.jpg.0c95da6a5ee7f1864854075c50a94c9b.jpg


      

  6. 2 hours ago, walt.farrell said:

    Good questions.

    One more: for what purpose do all these nice "Add Chord to Swatch" options generate useless swatches if you are in a CMYK document color space + have a CMYK color definition selected? They seem to produce RBG swatches only, regardless of both document and color selector type. Some of these chords even result in swatches with mixed color spaces, for instance some in HSL, some in CMYK. – Does not appear as "by Design" nor to be a missing feature. ugly buggy.

    1477263834_colorchordtoswatchoptions.jpg.ab0d76ff7b1664794a6b24db8dfc4528.jpg

    Tints of 100 K in a CMYK document:

    208991718_colorchordtints100K.jpg.5a6a79c620546a72afa9c84bbab300af.jpg

  7. 16 minutes ago, VectorCat said:

    In Document setup, un-check ”facing pages.”

    This doesn't sound healthy to do it in Document Setup. To me it splits a facing 2-page master, terminates its margins to 0, but keeps margins on some document pages, on others the margins are gone, too.

    Instead you may set facing or single with for masters only with right-click on a master "Spread Properties..." or via tool bar > "Spread Setup..." and optionally adjust the margins. But even there, toggling for a specific master between facing to single might result in unexpected behavior.

    25063796_masterspreadproperties.jpg.956bad3ce0e0128ff558aa0a6223fb89.jpg

  8. Since the print options window appearance and content does vary, depending on a.) your OS and b.) your installed printer driver there is no simple step-by-step tutorial which works the same for everybody.

    What do you get if you use the option "Print to File" in your screenshot at the end of the list starting with "Layout" highlighted?
    Possibly it is not necessary to choose the PDF printer in the menu "Printer:" above? (as it does for me on mac: I don't have to switch my default Epson printer to be able to export a PDF via print.)
     

  9. 18 hours ago, wkoehn said:

    frames below it maintain their "margin" distance

    As far I understand you are not asking for auto-sizing a text frames height but for auto-moving a text frames distance towards others.

    Unfortunately there is no such feature yet to be able to work in background.
    Instead you need to use the option "align vertically" in 3 steps each time a frame height changes:

    1. unckeck the "Auto Distribute"
    2. set a specific distance
    3. click the most right button above

    1902646170_alignverticallyobjectsspecificdistance.jpg.ddcd67b3d08e7e7e447f2fb376881a3b.jpg

  10. 7 minutes ago, rah1861 said:

    I tried that, but there is no option in the Export PDF dialog to specify Booklet

    That's true. Possibly a mistyping by NilsFinken.

    Booklet output is only available yet via File > Print. But there you can use a Print to PDF option. On mac it is available by system in the pulldown menu at the lower left corner. On windows you might first need to install a driver for Print to PDF.

  11. On 6/28/2019 at 1:57 PM, Fredrik M said:

    if i change the color mode for one object and select the next on the color mode does not switch in the settings box

    Where did you change the color mode for single objects? If inside AfPublisher, in what panel?

    Do you mean with "color mode" the color space of an object?
    Or do you mean the color selector type, like sliders (hsl, rgb, 4c, lab), or wheel or greyscale?

    Do you mean with "settings box" the Color Panel and its various slider types?
    If yes, does it switch as expected if you click on the lock icon and then select an object where you expect a different color mode than the momentary sliders show.

    Or do you mean with "settings box" the pop-up color selector in Swatches Panel to edit a swatch color?
    If yes, this color selector type appears never to change by itself or automatically, it changes only, if I manually choose a different color selector slider type and remains there regardless of the documents color space.

    7 minutes ago, Fredrik M said:

    I have created my own preset, not sure how this would affect the control panels when in layout though.

    Did you really notice that an export preset affects the colors during layout?
    Hopefully it does not, that would be really weird.

    However, in my experience the most successful way to get K-only objects really reliable as K-only is to export as PDF 1.3 or 1.4. (PDF/X-1 – X-3).
    That unexpected and unwanted limitation, which is not according to PDF specifications, is, in my opinion, a bug in AfPublisher's color handling. The fact, that in a CMYK .afpub a linked grayscale image with a grayscale profile becomes treated as RGB in AfPublisher by default, though its Resource Manager recognizes the profile correctly, supports my thinking.

  12. jbartley, unfortunately i do not know the right answer to either of both questions. Possibly the problem is a mix of different things. The sandbox message may also be due to another problem starting somewhere else in the workflow but not issuing a message. However, I assume that enabling to switch personas (apps) may be tricky, for example, if those app sandboxes need to merge or intersect. Concerning fairness you might want to read what an appearently disappointed developer wrote in 2014: https://blog.helftone.com/mac-app-store-the-subtle-exodus/

    What I would try to limit the issue in your .afpub:
    – Use a workflow without switching personas: Edit and save a linked resource not in Publisher but in its initial app.
    – If a linked resource refuses an update or replace: delete it and place it as a new object.
    – Don't save Affinity files on your Desktop but rather in your Documents folder.

  13. @ Walt, "sandbox" is a security software in macOS, simpel spoken a kind of firewall for processes of system or apps and their files. In macs Activity Monitor.app you can see which process runs in a sandbox. Not all processes or apps use a sandbox. But sandbox is mandatory for apps sold in the App Store.

    about_sandboxing.png.e7b4dbdbfbeb9ec6c5adf7ec7477bbe4.png

    https://developer.apple.com/library/archive/documentation/Security/Conceptual/AppSandboxDesignGuide/AboutAppSandbox/AboutAppSandbox.html

     

  14. Sorry if it's slightly off-topic but possibly one here might know:

    I use an older Intuos 2 (XD–01912-U, in A4+ size) in macoS 10.12.6 (Sierra) – nowadays without using the wacom preference panel, because it's too old to open and various newer drivers don't recognize the old tablet.

    I tried this simple solution https://www.reddit.com/r/wacom/comments/80v05q/intuos_2_on_macos_sierra/
    to make the pref pane work – but for me it results in repeatedly restart of the system preferences.app with an according message window "To use the Wacom pref pane the Sys Pref must be closed and reopened"

    1207784877_wacomprefpanerestartsyspref.jpg.9a4e83fda3be4b00e2f55e8d7c9c4336.jpg


    I appreciate any idea or experience to avoid this issue and make the wacom pref pane get opened.

     

    • Change MacOS to not show file extensions 

    No. If I switch in MacOS to hide file extensions – but keep separated mode – then on SaveAs > Replace the crash still occurs in AfPub (haven't tried AfDes)

    • Don't run the app in separated mode

    Yes. If I switch to not separated mode – but have MacOS set to show file extensions – then it works with no crash, in both apps.

    Notes:
    – since v408 + Designer I use separated mode. During beta I was using not separated mode with no crash on save-as-replace. And AfDesigner was not installed.

    – studio link works but one time it moved the AfPub tool bar outside the screen area when I switched back from des to pub persona: placed below the lower edge of the lower monitor. Toggling "Show Toolbar" did not make it appear. It jumped back into visible area by "Customize Toolbar" only.

    – at any time since using v408 + AfDesigner the MacOS login window started to show mixed languages consequently (head + buttons: English / body: German). I fixed it via Terminal ("sudo languagesetup" > "3" back to German as default language)

     

    In case in separated mode the window arrangement is influencing, here my two monitor settings:

    565332249_monitorsystemmenubararrangement.jpg.9e4324f94cef76b472dbab75c60835d1.jpg

    1. MacBook Pro screen (with system menu bar):

    48001084_separatedmodemonitor1withsystemmenubar.thumb.jpg.dfd0b7266494c2bf7e8cf0ed3f539c24.jpg

    2. External monitor (with AfPub main window and tool bar below):

    680764382_separatedmodemonitor2withafpubtoolbar.thumb.jpg.6acccd6836ef27e7aa386d79457e6430.jpg

     

    EDIT: I would prefer to use not separated mode IF i would be able to use the same panel arrangement > tool bar below document main window + not overlapping with panels left or right.

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