Jump to content

R C-R

Members
  • Content count

    8,230
  • Joined

  • Last visited

2 Followers

About R C-R

  • Rank
    Good news, everyone!

Profile Information

  • Gender
    Male
  • Location
    Texas, USA
  • Interests
    Animation; sci-fi & mystery books; UI design; physics; craft beers (consumption, not brewing); puns & dark, ironic humor; jazz & blues music; other stuff.

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There is no way to disable it. Apparently the warning about 'unsaved changes' applies to almost everything, including exporting, because that could be recorded as a history step, affect the last saved state of some per-document parameters, or some such.
  2. My confusion is over how you got from what I wrote to asking if I advocate the abolishing of multiple Pixel layers, & from there to thinking I am somehow grasping for reasons not to "support" live filter output caching. To be clear about it, I am not advocating abolishing anything, nor am I looking for reasons not to support anything that would improve the performance of the app. I am just wondering if simple cacheing of the output of live filter layers actually would do that, if it would do so any better than whatever cacheing is already used in the app, & if it would cause issues with existing features of the app that make it impractical to implement.
  3. Affinity Photo for iPad supports quite a few more keyboard shortcuts than are listed in the "Keyboard shortcuts" Help topic. That topic also incorrectly lists "U" as the shortcut for the Liquify Pinch Tool. @αℓƒяє∂ discovered that It actually is the letter I, as in Pinch. The topic says the shortcuts work with the "iPad's Smart keyboard" but fails to mention that they work with at least some 3rd party Bluetooth keyboards. Keyboard Shortcuts Photo ipad v2.rtf lists every shortcut that works with my iPad & a paired Anker Bluetooth keyboard. It is formatted similarly to the help topic, with every shortcut not listed in it highlighted on a grey background. I believe it to be accurate but I don't know if every BT keyboard supports them all. There is at least one omission from the Affinity Designer help topic of the same name, that being ⌘B for bold text. There are probably others but I have not yet checked all the possibilities.
  4. Affinity Designer is "real" vector software, & like with most other contemporary vector apps that includes support for quite a few raster image features. It even supports every raster image feature of its sister app Affinity Photo, although it cannot create or edit all of them. But that has nothing to do with the dpi/resize issue. It is just that if you change the document DPI you have to tell the app if you want to rescale its contents or anchor them in place, just as @walt.farrell said. It has many features, but reading users' minds is not among them!
  5. They already use mipmaps in a way somewhat like cacheing to reduce rendering overhead, but I am not sure how well that would work with live filters -- if nothing else, it could result in a lot more mipmaps that have to be stored somewhere, either in the file or in memory. This could also affect serialization, the file recovery feature, snapshots, or history, but I am not sure about that either.
  6. Assuming you are using Affinity Designer, in the File > Document Setup > Dimensions tab, try setting the "Documents will" option to "Rescale" & then change the DPI from 300 to 400.
  7. Or that it is a mistake that would leave some down-to-earth users in a fog about its function?
  8. Also for this, I do not understand how it could work when panning or zooming in & out of a document. Maybe I am oversimplifying this too much but it seems to me that a filter is either live or it is not. If it is live, then it needs to be re-rendered every time anything changes that affects it.
  9. If you have not already seen it, you might want to watch the Affinity Photo - Understanding DPI video tutorial for some background info on the relationship between image size & DPI. (I am assuming from your "vector program" comment that you are using Affinity Designer, but the video applies equally well to both Affinity apps.) Aside from that, placed images can & often do have different DPI (really PPI if you want to be pedantic about it) values than the document DPI, including different width & height DPI's.
  10. But how would that work when a user pans or zooms in & out on a document? Even if a full sized image of the filter's output & its effects on underlying layers was cached to memory (which could eat up a lot of RAM), it still would have to be re-rendered at the current document display size, right?
  11. Also note that an Affinity Store user account (if you have one) & your forum user account are two separate & unrelated things.
  12. As a Mac user, I have no idea if this is relevant but in the Mac version in Preferences > General there is an option to "Save thumbnails with documents." If the Windows version has the same option & it is not ticked, maybe try ticking it & see if that makes a difference? I have a few other apps on my Mac with a similar preference option. For all of them, as well as with any other document, I also have an OS level setting (in Finder, more or less equivalent to the Windows file explorer) to optionally show icon previews on a per folder basis. If this setting is not enabled, it overrides showing any thumbnails in Finder views, even if they are embedded in the document. I don't know if there is anything like that for the Windows file explorer, but if there is maybe that is something else to check?
  13. I assume what you mean by 'open in place' is the "Open From Cloud" option, right? If so, when I do that for example in Designer & choose a Photo file (either from an 'On my iPad' or cloud storage location) it does open that file. However, if I then save it from the Home screen, it does not overwrite the original file. That works for an .afdesign file opened in Designer or an .afphoto file opened in Photo, but not for an .afphoto file opened in Designer or visa versa. In fact, if I open an .afphoto file in Designer that initially has no vector layers & add a vector layer to it, selecting Save from the Home screen for that file displays this: Choosing either save option creates a new copy of the original with the .afdesign extension. Likewise, renaming any of the files in the Files app or either Affinity app does not affect the name(s) of the other(s) stored in an 'On my iPad' or cloud storage location. BTW, the Home screen "Open From Cloud" option is a bit misleading because it also allows opening a file from 'On my iPad' location.
  14. There are probably faster & better ways to do this but this is what I did: 1. Use the Ellipse Tool with the Shift key held down to place a circle over the part of the image you want to enlarge. 2. Set its stroke width & color as desired. If needed to make it easier to position it accurately, set its fill to none. 3. Once positioned, set the fill to a solid color & use the Selection Brush Tool with "Snap to Edges" & "All Layers" enabled to create a 'marching ants' selection of the fill. 4. Reset the fill to none & optionally lock the ellipse layer. 5. With the 'marching ants' selection still visible, select the background image layer & do a copy & paste. This will create a new layer containing just the selection. 6. Drag that layer to wherever you want it & use either the Transform panel or dragging on a corner handle of its selection box to enlarge it to the desired size. 7. With snapping enabled, use the Ellipse Tool with the Shift & Command keys held down to create a circle from the center of this layer, snapped to that layer's edges. 8. Set the ellipse to no fill & its stroke width & color as desired. 9. (Optional) For convenience, group this ellipse & the layer from step 5. 10. Use the Pen Tool in line mode to draw the lines connecting the two circles.
  15. Select "Customize Tools ..." (not "Customize Toolbar...") from the View menu & set it to use 2 or more columns.
×