Jump to content


  • Content Count

  • Joined

  • Last visited


About thomaso

  • Rank
    Dedicated User

Profile Information

  • Gender
  • Location
    Cologne, Germany

Recent Profile Visitors

3,201 profile views
  1. Though workbooks, tutorials or help texts don't replace reference manuals, – here some sorted link-lists to Serif's video tutorials for APh + APub: APhoto – posted by @v_kyr, 2020 dec: APublisher – posted by @acapstick, 2019 june + @EmilyGoater, 2021 march
  2. Ironically we can convert a Picture Frame, containing a bitmap fill + an image layer, to curves, without losing its picture frame features (UI) and without creating/converting any existing content to a bitmap fill. Instead the result appears buggy: Though the bitmap fill (before converting) still is reported at various UI spots to exists, it doesn't show in the layout, so now "Convert to Curves" seems someway to prevent a bitmap fill … and thus vice versa to a converted image, which forces a bitmap fill. (not in the video: Via Fill Tool I can load a new bitmap to this converted Picture Frame – again without getting it displayed in the layout though the UI reports it in the context toolbar and the various color wells) picture frame - fill & image - ConvertToCurves.m4v
  3. I don't see a reason why the way of "thinking" would prevent the app from displaying existing info. There doesn't seem to be any purpose in this behavior. It's not that I don't recognize how (~why) it happens but rather for what goal / use / advantage. (Besides the fact that I am not really missing this info, different to the OP, I am just curious to understand the concept of Serif / the developers) ps: You seem to mix the Affinity terms "image" vs. "picture frame". They are quite different – the image (frame) is more similar to a converted image layer (curve + fill) than to a picture frame, which can include both, a bitmap fill + an image (... besides additional content like further image(s) + vector object(s)).
  4. Just a note to «how the application "thinks"»: The app currently is willing & able to handle, report + give access to various kinds of content of a selected layer: An image layer does get its pixel resolution AND its vector stoke properties reported. From that perspective the thinking of the app appears oddly limited once the border of such a layer gets converted to an editable shape, as if the thinking would lack in multi-tasking. So it's hardly comprehensible that "Convert to Curves" interrupts access to the existing image information.
  5. This sounds even more disturbing. Walt, does it mean you can't replace just 1 of 2 instances? It is possible for me and I assume this behavior as being imperative. Imagine you start an .afpub with some identical images as placeholders to become individually replaced during the layout process. – Walt, isn't that possible for you?
  6. I have done it months ago with a small app. Since then macOS reminds me with a message window every few weeks to update the program, even though I have deselected all auto-update options in the macOS system panel (while the app itself has no update option or setting). Bit annoying macOS behavior.
  7. To me it is. – Mac only? Can you show your experience on Windows? In this clip you also see the problem of object selection within the manager: not the selected layout object is accordingly selected in the manager but its folder 'only'. resource manager - folders.m4v
  8. The question was related to the curve's content, the image, converted to a bitmap fill. The curve can be edited separately from its content, so curve & fill are two different things, the bitmap is hardly the curve itself.
  9. Hi dr.jamesmoore, Welcome to the Affinity Forums! Would you mind to change your user name? Your published email address might attract spam, to you or to the forum. (At least) if you purchased via Serif Store the older versions are there: https://store.serif.com/de/update/macos/publisher/1/ I don't know about the procedure for a Mac / Win App Store purchase, maybe someone else pops in with more info. In case you picked this thread accidentally: the mentioned v.1.8 isn't the current one. Your app, once installed, will guide you to the newest update via its "Check for Updates" option.
  10. That's a good question. It would be good to see what the original resolution of a bitmap fill was. Especially since there doesn't seem to be an option to reset to its original dimensions, only to original proportions. Though I would not mind to see the info I doubt it would be really useful (~ necessary) in practical use. As mentioned above, considering that a bitmap fill gets mainly used as pattern it is therefore downscaled, hardly increased. The various options like repeat (~stretch), mirror etc. do imply that the initial image doesn't appear in its original size and also there are options for interpolation to reduce possible jagging. Also note that there is no option for distance when wrap or mirror is used, that means you would prepare such a resource especially for this use (e.g. add a white margin) and would set its size accordingly, well knowing it will be used in smaller size. So, in case you want to achieve a specific result (different to just experimenting) I guess you would need to do some calculation anyway before using a bitmap fill.
  11. Does one know what "missing content" means? (appears at a .PDF and a .SVG) Also I want to add a suggestion to the topic's panel improvement list: The column "Status" appears to be redundant if the column "Placement" would be used instead. As far I understand an Embedded resource never can be missing + every Missing resource must be a Linked resource. So it could work to have in "Placement" 4 variables/entries: – Linked – Modified – Missing – Embedded EDIT: "– Modified" added to the variables
  12. It looks like a different rendering method in the Photo persona, and not influenced by the Pixel Alignment setting. As if the image gets blended with itself when moving. screen view APub & APhpers.m4v
  13. With OPT + SHIFT + UP/DOWN you can adjust the baseline of selected characters (– instead of the paragraph leading / line spacing).
  14. Instead of asking only "Why don't they make the interface like I expect it?" one could also question "WTF let me expect it different than it is?"
  15. In case you haven't noticed: meanwhile this topic has moved to the feedback forum, here any discussion fits. Though even here it's useful not to mix various subjects unless you don't mind. Subjects in separate topics are more obvious to the community because of their separate titles in the thread list view. I am sorry, I haven't been precise in this previous post. Actually by "convert to curves" an image gets converted to curves (with editable vector shape) but not rasterized. This way its resolution is maintained and can be fully used in a possible pattern or still increased without loss according to its original resolution. If you do an action which requires rasterization (e.g. applying a filter in APub's photo persona) then the app does warn you with a temporary assistant message in the upper right corner. (by the way: there is a feature request for a longer duration of this popup) The Layers panel indicates various types with its label texts in round brackets. Curve vs. Pixel: While converting to curve doesn't change/influence the image resolution, rasterizing "burns" (fixes) its resolution according to its current size in that moment, so for rasterizing the current object dimensions + document resolution are relevant. When up-scaled after applying the command they may appear in different resolution (depending on their dimension at the moment of the command).
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.