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

thomaso

Members
 View Profile  See their activity

  • Posts

    11,201

  • Joined

  • Last visited

 Content Type 

Everything posted by thomaso

  1. thomaso
    In v.170174 the shortcut for "Preview Mode" is very easy already: "F10". But on Mac all F-Keys are prefered by the system. "Something easier" on Mac would mean no F-key at all. Why not just "w", which is known for "Preview Mode" in some designers area and not used by Publisher yet.
  2. thomaso
    bgeal, to me the top row column width after bottom row merge slides charming (see .mov). – Or did I misread your issue? 170174_table merged width.mov 170174_table merged width.afpub p.s. can I reduce the preview size of the .mov above ? how?
  3. thomaso
    @Chris_K, ok.: To upload the .afpub including font files: Is there a way to save the document & auto-collect its font files for sharing the complete package?
  4. thomaso
    When I drag an image (jpg) from an image catalog document (Expression Media) onto a page then it does not appear as image but as text with the keywords of the image. The frame of that text gets placed at the beginning of the APub document, the text runs out of it over serveral pages. In this screenshots I dragged an image file onto an empty frame on page 2. The resulting text frame gets placed on page 1, the text appears on page 2. When I select the text frame on page 1 the text appears there.
  5. thomaso
    On export as PDF/X- (-1a/3/4) I experience 2 issues: • Some text becomes curved on export, while others on same page don't. • Some text prevents export and results in a message "An error occurred while exporting to: <path/file.pdf>". Those text exports without error if it gets curved before export. The issues appear to be related to particular fonts. (f.i. Univers) The issues do not occure with normal PDF (v. 1.4 – 1.7). Is there kind of a preflight tool in Affinity Publisher to get further information?
  6. thomaso
    The applications seems to have issues with text/font in your document. A PDF/X-1a export is possible with the 4 text frames in the header/footer set to invisible. Weird: in the resulting PDF all remaining text become curves. As a workaround to get a PDF with all text you could convert these 4 frames from text to curves – with the little disadvantage that you can't alter the text in the PDF (- and in your document if you save it curved). Unfortunately in the PDF all text become curves. A faster but less quality workaround is to choose the export option "Rasterise: Everything".
  7. thomaso
    A.) If I select a CMYK swatch and create Chord Tints from the color pane, than the resulting tints are RGB. B.) If I select a CMYK swatch and create Chord Tints from the swatch directly (ctrl-click), than the results are in CMYK. ––> A) is a bug in my opinion. At least in a cmyk print document. Examples: Different Chord tint names from the swatch "100 k" (0c 0m y0 100k): C.) If I create tints via Chord menu (either from color or swatch pane) than the tints are named with values including their tint reduction. It is not possible to read the tint % value without additional calculation. D.) If I create tints not as Chord but as single swatch than the tint is named with the value of its origin + a tint value (%). ––> C) is a bug in my opinion. The tint value (%) is not recognizable without calculation. Example: Single created tints from the same swatch like above. ("100 k")
  8. thomaso
    I'd do it shorter – IF a simple undo would not work: I'd hit command-c before renaming it. And command-v as re-rename process. No typing at all
  9. thomaso
    But no, Yes, we can! However, even if a simple "undo" would not undo, I still could undo by re-rename it
  10. thomaso
    If in the color pane in tint slider view a tint color becomes added as swatch – than the sliders & values of that swatch don't show its real value but the value of the former 100% tint. Or shorter: sliders ignore tints, the tint slider excepted. In any slider type / color system. For instance: 50% tint of 100 C + 50 Y shows in the sliders 100 C + 50 Y, whereas its real values are 50 C + 25 Y. That means you can't know for shure the values of a swatch which got created as tint. Neither its name nor its slider values appear as realiable. Related issues: • if you hit the swatch name and, in the pop-up window, hit the pipette symbol or the tiny color circle besides the sliders pulldown menu – than the color changes to the sliders values and the created tint is lost and overwritten by the 100% of the former color. • if you define the origin color as global color the dependency gets lost as soon you create a tint: Changing the origin color does not affect its child, the tint. A tint of a color, even of a global, appears not to be related to its mother.
  11. thomaso
    May be you use "ideas" as names, not values? I can imagine that you might get irritated if your color for instance "sky blue" or "green 4" would get a different name by the application. What I meant are names with values only, as shown in my screenshots: I changed a blue into a yellow - but the name (values) remain as blue. This might become disturbing especially if you use global colors and use to alter them. I showed it with this two very different colors to make it more obvious. In reality the color change might be more subtil and a wrong name not such obvious. No, I am wondering, why this menu does tell me. It gives the impression I have to be careful. Usually you can undo every change you do in a file – and therefore a warning would make sense only when an undo would NOT be possible.
  12. thomaso
    In the list view of the swatches pane any new swatch gets an auto-name with its defined values. Unfortunately these names don't auto-change when the color definition got changed by the user. This results in wrong swatch names, both for global and non-global swatches. To avoid wrong names the user has to rename any swatch manually after changing its color. To fix the name it needs several clicks to the manual renaming option window. Suggestions: – auto-change a swatch name when its color definition got changed – enable renaming on double-click the swatch name p.s.: in the actual renaming option window a hint appears: "This is not an undoable operation." – Why does it warn me that I can undo this operation?
  13. thomaso
    Completely agree! Besides the missing ability to save individual option pane positions: imho the use of two monitors appears to force application crashes and makes the ability of saveable window positions more necessary. (see also window/pane positions )
  14. thomaso
    > " ... only happens when one of the documents is offset from the main screen" Not to me. – Might be a problem with two monitors? I just de-selected "Separated Mode" –> it arranged some but not all of the option-panes positions to a former setting + the two open doc-windows from the larger second monitor to the smaller laptop screen, behind the option pane windows. I moved them back on the larger/second monitor and selected "Separated Mode" –> that made the App crash and close. By the way: after restart the app it was the first time (of about 15) that my individual option pane positions were not placed anywhere and somehow chaotic after the application crash.
  15. thomaso
    A ctrl-click appears not to react mac-like & not as mentioned in the Affinity Publisher Beta Help: – For instance in the Swatches Pane: A ctrl-click on a color swatch opens a pulldown color-pane (with noise slider instead the opacity slider in the 'original' color-pane). The same result occurs with an option-click and with a double-click (no key pressed). Different to this behaviour the Help says: "ctrl-click the swatch you want to remove and choose Delete Fill from the pop-up menu." In MacOS usually a ctrl-click = a right-click. This appears not to work in Publisher, different to its Help-Info.
  16. thomaso
    In a new CMYK document a frame text appears as black by default. That's fine. Unfortunately this Black appears in the cmyk slider view of the color pane not to be = 100 K but mixed 87 C + 78 M + 65 Y + 93 K, which additionally is a rich Black with 323 % print color. This complys to the default Black definition of an RGB document. Any chance to fix the default Black for all CMYK documents to 100 K?
  17. thomaso
    Is it possible to save a custimized setting of window/pane positions? It appears to happen accasionally with 2 open documents that choosing "Window" > "Merge all Windows" results in a crash and closes the Application. After reopening the app all panes are spread somehow chaotic on my two monitors and neded to get reanged. And: how can I go back to the deafult window/pane setting? Meanwhile the tool and document and the long pane with the persona icons aren't locked anymore to the main monitors edges and partially covering the document window.
  18. thomaso
    I'd prefer to avoide to post already existing topics. Therefore it would be very useful, to make the search option/filter "Search in This Forum" working. At least as long the UI contains issues it would help a lot in any search for "windows" not to get results relating the Windows operating system within the Mac forum.
  19. thomaso
    > into the “Signature” section of my profile where is the “Signature” section in my profile? I can't find any "signature" wording within my Affinities forums profile. Can you deliver a screenshot of where you put it, please? Here is mine of no "signature" section:
  20. thomaso
    okay. "signature". now you'll guide us to "signature" - either, No, both in Affinity forums UI and in your profiles' result. very curious now: what to get is what to see what you'll show now? :•)
  21. thomaso
    https://forum.affinity.serif.com/index.php?/topic/561-gui-issue-effects-pane-open-many-v17832/?p=4574 : >> Ah, where is a useful place to write system information into a forum user profile? – Is it @ "Profile Feed" / "what's on your mind?" ? > We've not really thought about this. :( Would you tell/show us at least where/how users feed into "What's on your mind?" will occure?
  22. thomaso
    There is a Mac OS X feature, both system-wide and in most third-party applications, which pop-ups the file path on command-click on a documents window title . – Sounds complex but is easy to use. – Unfortunately it does not work in Affinity. ( Hm, because of its window 'tab' concept? ) – Instead in Affinity a command-click on the window title does select an object on the Affinity document page/canvas. The competitor Adobe meanwhile lost this feature in many of its programs (no, not every) – A niche/advantage for Affinity? Even more: in OS X the user may scroll through such pop-up windows content to jump to a level in finder. For instance 2 screenshots:
  23. thomaso
    just curios: what beta was "beta 5" which I found in some posts? I really would appreciate a look-up table with dates, names, numbers, features, fixes ... (and I wonder that you, Serif, seem not be interrested for your own use) this is a question only, an interest. It's neither a request nor about a bug. More a suggestion than a demand.
  24. thomaso
    I had posted questions about understanding beta, unfortunately within a different topic. So I ask here again: > forums structure: by beta? = by date ? Shure? The answer #3 makes me assume any post "knows" about users beta version simply by posting date. (Easy for new posts, no need to look up and type a version number) Otherwise it might be useful to know a particular beta version to a particular posting. Occasionally it happens that I search in the forum for tags (nice support!) and end up in reading about a "beta 5" within the search results – whereas my experienced version names sound like "1.0." and "17644", "17832", ..."18306". – Five digits versus digit "5". So I wonder if Serif would want to add a forums level about beta info: names, dates, changes ... Different to topic "Beta Update" it would list- or table-like 'easily' show facts, not comments. Read only.
  25. thomaso
    > forums structure: by beta? = by date ? Shure? Unfortunately I had added some questions about a totally different topic above. The quoted question meanwhile got sort of answered by TonyB: https://forum.affinity.serif.com/index.php?/topic/762-does-a-beta-update-overwrite-previous-beta-behavior/&p=2683
×
×
  • 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.

 Accept Cookies  Reject Cookies